# US 2019/0319980 A1 · Threat response using event vectors

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

- Number: US 2019/0319980 A1
- Document ID: US20190319980A1
- Status: Published application
- Kind: A1
- Application number: 16/383,315
- Filed: 2019-04-12
- Published: 2019-10-17
- Earliest claimed: 2018-04-13
- Assignees: Sophos Limited
- Applicants: Sophos Limited
- Inventors: Joseph H. Levy; Andrew J. Thomas; Daniel Salvatore Schiappa; Kenneth D. Ray
- Web page: https://patentgrep.com/patent/US20190319980A1

## CPC

- G06F 21/45: Structures or tools for the administration of authentication
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/122: {using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185)}
- G06F 16/137: {Hash-based (content-based indexing of textual data G06F16/31)}
- G06F 16/285: {Clustering or classification}
- G06F 16/93: Document management systems
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- G06N 3/0675: {using electro-optical, acousto-optical or opto-electronic means}
- G06N 5/046: Forward inferencing; Production systems
- G06N 5/048: Fuzzy inferencing
- G06N 20/00: Machine learning
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/16: the keys or algorithms being changed during operation
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3265: {using certificate chains, trees or paths; Hierarchical trust model}
- H04L 9/3271: {using challenge-response}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 41/20: {Network management software packages}
- H04L 41/22: comprising specially adapted graphical user interfaces [GUI]
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0838: {using one-time-passwords}
- H04L 63/0861: {using biometrical features, e.g. fingerprint, retina-scan (cryptographic mechanisms or cryptographic arrangements for entity authentication using biological data H04L9/3231)}
- H04L 63/101: {Access control lists [ACL]}
- H04L 63/102: {Entity profiles}
- H04L 63/1408: {by monitoring network traffic (monitoring network traffic per se H04L43/00)}
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/1433: {Vulnerability analysis}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)}
- G06F 2221/034: Test or assess a computer or a system
- H04L 9/3228: {One-time or temporary data, i.e. information which is sent for every authentication or authorization, e.g. one-time-password, one-time-token or one-time-key}
- H04L 9/3231: {Biological data, e.g. fingerprint, voice or retina (network architectures or network communication protocols for supporting authentication of entities using biometrical features in a packet data network H04L63/0861)}
- H04L 2463/082: applying multi-factor authentication
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A security platform uses a sensor-event-analysis-response methodology to iteratively adapt to a changing security environment by continuously creating and updating entity models based on observed activities and detecting patterns of events that deviate from these entity models.

## Claims

### Claim 1

A computer program product for assessing and responding to risk in an enterprise network, the computer program product comprising computer executable code embodied in a non-transitory computer-readable medium that, when executing on one or more computing devices, performs the steps of:
instrumenting a compute instance in the enterprise network with a number of sensors to detect events from a number of computing objects associated with the compute instance;
storing a first entity model for an entity associated with the compute instance at a local security agent for the compute instance, the entity including at least one of a domain controller, a physical device, a user, an operating system, or an application associated with the compute instance, and the first entity model characterizing a pattern of events expected from the number of sensors in a vector space;
receiving events from the number of computing objects at the local security agent on the compute instance;
collecting a plurality of the events into an event vector in the vector space;
calculating a first risk score with the local security agent based on a first distance between the event vector and the first entity model in the vector space;
when the first risk score exceeds a first threshold, deploying a first remedial action for the compute instance from the local security agent;
storing a second entity model for the entity at a threat management facility for the enterprise network, the second entity model characterizing a second pattern of events expected from the number of sensors in the vector space;
transmitting the event vector to the threat management facility;
calculating a second risk score with the threat management facility based on a second distance between the event vector and the second entity model; and
when the second risk score exceeds a second threshold, deploying a second remedial action for the compute instance from the threat management facility.

### Claim 2 (depends on 1)

The computer program product of claim 1 wherein at least one of the first threshold and the second threshold is algorithmically determined.

### Claim 3 (depends on 1)

The computer program product of claim 1 wherein calculating the second risk score includes evaluating the second risk score based on an event stream from two or more compute instances within the enterprise network.

### Claim 4

A method for assessing and responding to risk in an enterprise network, the method comprising:
instrumenting a compute instance in the enterprise network with a number of sensors to detect events from a number of computing objects associated with the compute instance;
providing a first entity model and a second entity model for an entity associated with the compute instance, the first entity model and the second entity model characterizing a pattern of events expected from the number of sensors in a vector space;
receiving events from the number of computing objects at a local security agent on the compute instance;
collecting a plurality of the events into an event vector in the vector space;
calculating a first risk score with the local security agent based on a first distance between the event vector and the first entity model in the vector space;
when the first risk score exceeds a first threshold, deploying a first remedial action for the compute instance from the local security agent;
transmitting the event vector to a threat management facility;
calculating a second risk score with the threat management facility based on a second distance between the event vector and the second entity model; and
when the second risk score exceeds a second threshold, deploying a second remedial action for the compute instance from the threat management facility.

### Claim 5 (depends on 4)

The method of claim 4 wherein the second entity model includes one or more events from a second compute instance in the enterprise network.

### Claim 6 (depends on 4)

The method of claim 4 wherein the second entity model includes one or more events from a second entity in the enterprise network.

### Claim 7

A system comprising:
a local security agent on a compute instance in an enterprise network, the local security agent configured to receive events from sensors on the compute instance and to generate one or more event vectors each including a collection of events for an entity associated with the compute instance, the local security agent further configured to locally determine a first risk score based on a first deviation of one of the event vectors to an entity model for the entity associated with the compute instance, and the local security agent further configured to report each of the event vectors to a remote resource; and
a threat management facility for the enterprise network, the threat management facility configured to operate on an event stream including event vectors reported from each of a plurality of compute instances including the compute instance, and to calculate a second risk score based on a second deviation of one or more of the event vectors in the event stream from one or more corresponding entity models associated with the plurality of compute instances.

### Claim 8 (depends on 7)

The system of claim 7 wherein the threat management facility is configured to deploy a remedial measure for the compute instance when at least one of the first risk score and the second risk score exceeds a threshold.

### Claim 9 (depends on 8)

The system of claim 8 wherein the threshold is algorithmically determined.

### Claim 10 (depends on 7)

The system of claim 7 wherein the first risk score is indicative of deviations from an activity baseline for the event vectors for the compute instance.

### Claim 11 (depends on 10)

The system of claim 10 wherein the activity baseline is determined based on a historical window of event vectors for the compute instance.

### Claim 12 (depends on 11)

The system of claim 11 wherein the activity baseline is periodically recalculated for a new historical window.

### Claim 13 (depends on 7)

The system of claim 7 wherein the second risk score is indicative of deviations from an activity baseline for the event stream received at the threat management facility.

### Claim 14 (depends on 13)

The system of claim 13 wherein the activity baseline is determined based on a historical window for the event stream.

### Claim 15 (depends on 7)

The system of claim 7 wherein the first risk score is calculated based on a distance between at least one of the event vectors and the entity model in a vector space.

### Claim 16 (depends on 7)

The system of claim 7 wherein the first risk score is evaluated using a k-nearest neighbor algorithm.

### Claim 17 (depends on 7)

The system of claim 7 wherein the second risk score is calculated based on a distance between the event stream and the one or more corresponding entity models in a vector space.

### Claim 18 (depends on 7)

The system of claim 7 wherein the second risk score is evaluated using a k-nearest neighbor algorithm.

### Claim 19 (depends on 7)

The system of claim 7 wherein the entity of the entity model is at least one of a domain controller, a physical device, a user, an operating system, and an application associated with the compute instance.

### Claim 20 (depends on 7)

The system of claim 7 wherein the one or more corresponding entity models include models for a number of entities within the enterprise network selected from the group consisting of a domain controller, an identity and access management system, a physical device, a user, an operating system, and an application associated with the compute instance.

### Claim 21 (depends on 7)

The system of claim 7 wherein the event stream includes a plurality of anonymized event vectors.

### Claim 22 (depends on 7)

The system of claim 7 wherein event vectors in the event stream are at least one of tokenized, encrypted, compressed, and prioritized.
