# US 2019/0173921 A1 · Automated Mitigation of Electronic Message Based Security Threats

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0173921 A1
- Document ID: US20190173921A1
- Status: Published application
- Kind: A1
- Application number: 16/192,206
- Filed: 2018-11-15
- Published: 2019-06-06
- Earliest claimed: 2017-10-02
- Assignees: ServiceNow, Inc.
- Applicants: ServiceNow, Inc.
- Inventors: Phillip DiCorpo; Jose Bernal; Eun-Sook Watson
- Web page: https://patentgrep.com/patent/US20190173921A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 16/951: Indexing; Web crawling techniques
- G06F 16/953: Querying, e.g. by the use of web search engines
- G06F 21/56: Computer malware detection or handling, e.g. anti-virus arrangements
- H04L 51/212: using filtering or selective blocking
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0281: {Proxies}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L 63/1483: {service impersonation, e.g. phishing, pharming or web spoofing (detection of rogue wireless access points H04W12/12)}
- H04L 51/08: Annexed information, e.g. attachments
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

An example embodiment may include a security enforcement point device disposed within a managed network and a security decision point device disposed within a computational instance of a remote network management platform. The security decision point device may be configured to: receive a message by way of the managed network; parse the message to identify observable indicators of one or more of the security threats, where the observable indicators include at least one of a network addresses, a hyperlink, or a representation of an attached file; remotely query a security threat database for the observable indicators; receive, from the security threat database, an indication that the observable indicators are associated with a particular security threat, and transmit, to the security enforcement point device, a command to update its associated security policy such that the particular security threat is mitigated.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A system configured to detect and mitigate phishing attacks for a network, the system comprising:
an email server having a spam filter configured to apply one or more filtering rules to a message sent to one or more client devices associated with the network; and
a security decision point application configured to:
receive the message from the email server, wherein the message was not classified as spam by the spam filter but suspected to be a phishing attack;
parse the message for an observable indicator of the phishing attack;
query a security threat database for the observable indicator, wherein the security threat database is configured to determine whether the observable indicator is associated with known phishing attacks;
receive a result of the determination from the security threat database; and
in response to the result indicating that the observable indicator is not associated with the known phishing attacks, transmit an update to the spam filter to classify a future message having the observable indicator as spam.

### Claim 22 (depends on 21)

The system of claim 21, wherein the security decision point application is configured to transmit an additional update to the email server to block the future message having the observable indicator in response to the result indicating that the observable indicator is associated with the known phishing attacks.

### Claim 23 (depends on 21)

The system of claim 21, wherein the observable indicator comprises a network address, a hyperlink, a representation of an attached file, a sender name, or a recipient name.

### Claim 24 (depends on 23)

The system of claim 23, wherein the representation of the attached file is a hash computed by applying a one-way function to the attached file.

### Claim 25 (depends on 21)

The system of claim 21, wherein the security threat database comprises one or more feature vectors representing an array of known observable indicators associated with the known phishing attacks, and wherein the security threat database is configured to determine whether the observable indicator is associated with the known phishing attacks by comparing the observable indicator to the one or more feature vectors.

### Claim 26 (depends on 21)

The system of claim 21, wherein the security decision point application is configured to:
receive, from a computing device, a query for a particular observable indicator;
determine whether the particular observable indicator is maintained in the security threat database; and
based upon a determination that the particular observable indicator is maintained in the security threat database, transmit, to the computing device for display, information representing one or more configuration items that received at least one message having the particular observable indicator.

### Claim 27 (depends on 21)

The system of claim 21, wherein the message comprises an email message, a short message service (SMS) message, an instant messaging (IM) message, or a group chat message.

### Claim 28 (depends on 21)

The system of claim 21, wherein the message comprises an email message having an attached file, and wherein the security decision point application is configured to:
query the email server to determine a number of times that the attached file has been received by the email server, a number of email accounts to which the attached file was delivered, the email accounts to which the attached file was delivered, or any combination thereof.

### Claim 29

A method comprising:
receiving, by a security decision point application, a message from an email server having a spam filter, wherein the message was not classified as spam by the spam filter but suspected to be a phishing attack;
parsing, by the security decision point application, the message for an observable indicator of a phishing attack;
querying, by the security decision point application, a security threat database for the observable indicator, wherein the security threat database is configured to determine whether the observable indicator is associated with known phishing attacks;
receiving, by the security decision point application, a result of the determination from the security threat database; and
in response to the result indicating that the observable indicator is not associated with the known phishing attacks, transmitting, by the security point application, an update to the spam filter to classify a future message having the observable indicator as spam.

### Claim 30 (depends on 29)

The method of claim 29, comprising transmitting, by the security point application, an additional update to the email server to block the future message having the observable indicator in response to the result indicating that the observable indicator is associated with the known phishing attacks.

### Claim 31 (depends on 29)

The method of claim 29, wherein the observable indicator comprises a network address, a hyperlink, a representation of an attached file, a sender name, or a recipient name.

### Claim 32 (depends on 31)

The method of claim 31, wherein the representation of the attached file is a hash computed by applying a one-way function to the attached file.

### Claim 33 (depends on 29)

The method of claim 29, wherein the security threat database comprises one or more feature vectors representing an array of known observable indicators associated with the known phishing attacks, and wherein the security threat database is configured to determine whether the observable indicator is associated with the known phishing attacks by comparing the observable indicator to the one or more feature vectors.

### Claim 34 (depends on 29)

The method of claim 29, further comprising:
receiving, by the security decision point application from a computing device, a query for a particular observable indicator;
determining, by the security decision point application, whether the particular observable indicator is maintained in the security threat database; and
based upon a determination that the particular observable indicator is maintained in the security threat database, transmitting, by the security decision point application to the computing device for display, information representing one or more configuration items that received at least one message having the particular observable indicator.

### Claim 35 (depends on 29)

The method of claim 29, wherein the message comprises an email message, a short message service (SMS) message, an instant messaging (IM) message, or a group chat message.

### Claim 36 (depends on 29)

The method of claim 29, wherein the message comprises an email message having an attached file, and the method comprising:
querying, by the security decision point application, the email server to determine a number of times that the attached file has been received by the email server, a number of email accounts to which the attached file was delivered, the email accounts to which the attached file was delivered, or any combination thereof.

### Claim 37

A tangible, non-transitory computer-readable medium, comprising instructions that, when executed by one or more processors, cause the one or more processors to:
receive a message from an email server having a spam filter, wherein the message was not classified as spam by the spam filter but suspected to be a phishing attack;
parse the message for an observable indicator of a phishing attack;
query a security threat database for the observable indicator, wherein the security threat database is configured to determine whether the observable indicator is associated with known phishing attacks;
receive a result of the determination from the security threat database; and
in response to the result indicating that the observable indicator is not associated with the known phishing attacks, transmit an update to the spam filter to classify a future message having the observable indicator as spam.

### Claim 38 (depends on 37)

The tangible, non-transitory computer-readable medium of claim 37, comprising instructions that cause the one or more processors to transmit an additional update to the email server to block the future message having the observable indicator in response to the result indicating that the observable indicator is associated with the known phishing attacks.

### Claim 39 (depends on 37)

The tangible, non-transitory computer-readable medium of claim 37, wherein the observable indicator comprises a network address, a hyperlink, a representation of an attached file, a sender name, or a recipient name.

### Claim 40 (depends on 37)

The tangible, non-transitory computer-readable medium of claim 37, wherein the security threat database comprises one or more feature vectors representing an array of known observable indicators associated with the known phishing attacks, and wherein the security threat database is configured to determine whether the observable indicator is associated with the known phishing attacks by comparing the observable indicator to the one or more feature vectors.
