IP Library Granted Patent US 10,284,587
Granted Patent B1
US 10,284,587 · App. 15/265,346 · Granted May 7, 2019

Systems and methods for responding to electronic security incidents

Inventors: Brian Schlatter (Playa Vista, CA); Adam Glick (Culver City, CA); Akshata Krishnamoorthy Rao (Mountain View, CA); Feng Li (Ontario, CA)
Assignee: Symantec Corporation
H04L63/1433G06F3/0482H04L63/1441
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,284,587
App. No.
15/265,346
Granted
May 7, 2019
Kind
B1
Abstract

The disclosed computer-implemented method for responding to electronic security incidents may include (i) identifying a plurality of security incidents that each occurred within a computing environment and call for a security response, (ii) establishing relationships among the plurality of security incidents by, for each security incident, (a) calculating a feature vector indicating at least one feature of the security incident, (b) using the feature vector to calculate a degree of similarity between the security incident and an additional security and (c) creating an association between the security incident and the additional security incident that reflects the degree of similarity between the security incident and the additional security incident, and (iii) triggering, based on the relationships among the plurality of security incidents, a security action that responds to at least the security incident and the additional security incident. Various other methods, systems, and computer-readable media are also disclosed.

Claims (62)

1. A computer-implemented method for responding to electronic security incidents, at least a portion of the method being performed by a computing device comprising at least one processor, the method comprising:

causing an identification module executed by the at least one processor to identify, by a software security system that is configured to detect abnormal activity within a computing system, a plurality of security incidents, wherein each security incident in the plurality of security incidents represents an instance of abnormal activity that occurred within the computing system and calls for a security response;

establishing relationships among the plurality of security incidents by, for each security incident in the plurality of security incidents:

causing a vector module executed by the at least one processor to calculate a feature vector of the security incident that indicates at least one feature of the security incident;

causing a similarity module executed by the at least one processor to calculate a degree of similarity between the security incident and an additional security incident in the plurality of security incidents based at least in part on comparing the feature vector of the security incident to a feature vector of the additional security incident; and

causing a creation module executed by the at least one processor to create an association between the security incident and the additional security incident that reflects the degree of similarity between the security incident and the additional security incident; and

causing a security module executed by the at least one processor to trigger, by the software security system and based on associations among the plurality of security incidents, a security action that responds to at least both the security response called for by the security incident and the security response called for by the additional security incident.

2. The method of claim 1 , wherein triggering the security action comprises generating a report comprising a plurality of related security incidents that are associated with the security incident and the additional security incident.

3. The method of claim 2 , wherein generating the report comprises sorting the plurality of related security incidents based on the degree of similarity of each incident to the security incident.

4. The method of claim 2 , further comprising providing the report to an administrator of at least one computing system involved in the security incident.

5. The method of claim 4 , wherein providing the report to the administrator comprises displaying the contents of the report through a graphical user interface that enables the administrator to respond simultaneously to at least the security incident and the additional security incident.

6. The method of claim 1 , wherein creating the association between the security incident and the additional security incident is based on the degree of similarity satisfying a similarity threshold.

7. The method of claim 6 , wherein triggering the security action comprises automatically adjusting the similarity threshold based on the number of additional security incidents that are associated with the security incident to generate an actionable list of security incidents that are associated with the security incident.

8. The method of claim 1 , wherein the security action comprises generating a new security incident based on the relationship between at least the security incident and the additional security incident.

9. The method of claim 1 , wherein the feature vector that comprises at least one feature of the security incident comprises at least one of:

a hostname of a computing device affected by the security incident;

a classification of the computing device affected by the security incident;

an Internet Protocol (IP) address that, when accessed, triggered the security incident;

a domain name that, when accessed, triggered the security incident;

a Uniform Resource Locator (URL) that, when accessed, triggered the security incident;

a user of a computing system affected by the security incident;

a group of users affected by the security incident;

a physical location of computing systems affected by the security incident;

an e-mail address that facilitated the security incident;

a file that, when present on a victim computing system, triggered the security incident;

a software application that, when present on the victim computing system, triggered the security incident; and

a digital signature that represents a signing authority that signed files involved in the security incident and the additional security incident.

10. A system for responding to electronic security incidents, the system comprising:

an identification module, stored in memory, that identifies, by a software security system that is configured to detect abnormal activity within a computing system, a plurality of security incidents, wherein each security incident in the plurality of security incidents represents an instance of abnormal activity that occurred within the computing system and calls for a security response;

a vector module, stored in memory, that calculates, for each security incident in the plurality of security incidents, a feature vector that indicates at least one feature of the security incident;

a similarity module, stored in memory, that calculates a degree of similarity between the security incident and an additional security incident in the plurality of security incidents based at least in part on comparing the feature vector of the security incident to a feature vector of the additional security incident;

a creation module, stored in memory, that creates an association between the security incident and the additional security incident that reflects the degree of similarity between the security incident and the additional security incident;

a security module, stored in memory, that triggers, by the software security system and based on associations among the plurality of security incidents, a security action that responds to at least both the security response called for by the security incident and the security response called for by the additional security incident; and

at least one physical processor configured to execute the identification module, the vector module, the similarity module, the creation module, and the security module.

11. The system of claim 10 , wherein the security module triggers the security action by generating a report comprising a plurality of related security incidents that are associated with the security incident and the additional security incident.

12. The system of claim 11 , wherein the security module generates the report by sorting the plurality of related security incidents based on the degree of similarity of each incident to the security incident.

13. The system of claim 11 , wherein the security module provides the report to an administrator of at least one computing system involved in the security incident.

14. The system of claim 13 , wherein the security module provides the report to the administrator by displaying the contents of the report through a graphical user interface that enables the administrator to respond simultaneously to at least the security incident and the additional security incident.

15. The system of claim 10 , wherein the creation module creates the association between the security incident and the additional security incident is based on the degree of similarity satisfying a similarity threshold.

16. The system of claim 15 , wherein the security module triggers the security action comprises automatically adjusting the similarity threshold based on the number of additional security incidents that are associated with the security incident to generate an actionable list of security incidents that are associated with the security incident.

17. The system of claim 10 , wherein the security module generates a new security incident based on the relationship between at least the security incident and the additional security incident.

18. The system of claim 10 , wherein the feature vector that comprises at least one feature of the security incident comprises at least one of:

a hostname of a computing device affected by the security incident;

a classification of the computing device affected by the security incident;

an Internet Protocol (IP) address that, when accessed, triggered the security incident;

a domain name that, when accessed, triggered the security incident;

a Uniform Resource Locator (URL) that, when accessed, triggered the security incident;

a user of a computing system affected by the security incident;

a group of users affected by the security incident;

a physical location of computing systems affected by the security incident;

an e-mail address that facilitated the security incident;

a file that, when present on a victim computing system, triggered the security incident;

a software application that, when present on the victim computing system, triggered the security incident; and

a digital signature that represents a signing authority that signed files involved in the security incident and the additional security incident.

19. A non-transitory computer-readable medium comprising one or more computer-readable instructions that, when executed by at least one processor of a computing device, cause the computing device to:

cause an identification module executed by the at least one processor to identify, by a software security system that is configured to detect abnormal activity within a computing system, a plurality of security incidents, wherein each security incident in the plurality of security incidents represents an instance of abnormal activity that occurred within the computing system and calls for a security response;

establish relationships among the plurality of security incidents by, for each security incident in the plurality of security incidents:

causing a vector module executed by the at least one processor to calculate a feature vector that indicates at least one feature of the security incident;

causing a similarity module executed by the at least one processor to calculate a degree of similarity between the security incident and an additional security incident in the plurality of security incidents based at least in part on comparing the feature vector of the security incident to a feature vector of the additional security incident; and

causing a creation module executed by the at least one processor to create an association between the security incident and the additional security incident that reflects the degree of similarity between the security incident and the additional security incident; and

causing a security module executed by the at least one processor to trigger, by the software security system and based on associations among the plurality of security incidents, a security action that responds to at least both the security response called for by the security incident and the security response called for by the additional security incident.

20. The non-transitory computer-readable medium of claim 19 , wherein the one or more computer-readable instructions cause the security module to generate a report comprising a plurality of related security incidents that are associated with the security incident and the additional security incident.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 21, 2019
From: SYMANTEC CORPORATION
To: CA, INC.
Reel/Frame 051144/0918 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 14, 2016
From: SCHLATTER, BRIAN; GLICK, ADAM; RAO, AKSHATA KRISHNAMOORTHY; LI, FENG
To: SYMANTEC CORPORATION
Reel/Frame 039741/0408 →
Cited By (18)
US 12,204,652 US 12,204,870 US 12,229,276 US 12,265,526 US 12,299,116 US 12,346,451 US 12,354,043 US 12,361,358 US 12,373,557 US 12,373,566 US 12,406,068 US 12,488,124 US 12,511,381 US 12,526,289 US 12,621,331 US 12,670,455 US 12,717,931 US 12,725,106