IP Library › Granted Patent US 12,034,743
Granted Patent B2
US 12,034,743 · App. 17/525,773 · Granted Jul 9, 2024

Quantification of adversary tactics, techniques, and procedures using threat attribute groupings and correlation

Inventors: Ankur Sunil Tyagi (Foster City, CA); Mayuresh Vishwas Dani (Fremont, CA)
Assignee: Qualys, Inc.
H04L63/1416H04L63/1425H04L63/1433H04L63/1466H04L63/20
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 12,034,743
App. No.
17/525,773
Granted
Jul 9, 2024
Kind
B2
Abstract

The present disclosure provides a method and a system for generating a decision tree that tests security event files. The method comprises receiving attack data comprising a plurality of attack execution operations and determining threat attribute data based on the attack data. The method also comprises generating a decision tree using the threat attribute data. The decision tree includes at least one first node and a plurality of second nodes connected to the at least one first node. A first nodal data may be generated and assigned to each second node based on one or more threat attributes associated with the threat attribute data. In response to receiving a security event file, the method executes one or more security tests, using the decision tree, for the security event file.

Claims (77)

1. A method comprising:

receiving, using one or more computing device processors, attack data comprising a plurality of attack execution operations;

determining, using the one or more computing device processors, threat attribute data based on the attack data, the threat attribute data comprising:

a first threat attribute associated with the plurality of attack execution operations, the first threat attribute comprising threat-actor data indicative of an attacker associated with at least one attack execution operation comprised in the plurality of attack execution operations,

a second threat attribute associated with the plurality of attack execution operations, the second threat attribute indicative of malware data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a third threat attribute associated with the plurality of attack execution operations, the third threat attribute indicative of security tool data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a fourth threat attribute associated with the plurality of attack execution operations, the fourth threat attribute comprising user data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a fifth threat attribute associated with the plurality of attack execution operations, the fifth threat attribute comprising location data associated with an attack execution operation comprised in the plurality of attack execution operations, and

a sixth threat attribute associated with the plurality of attack execution operations, the sixth threat attribute comprising operating system data associated with executing the at least one attack execution operation comprised in the plurality of attack execution operations; and

generating, using the one or more computing device processors, a decision tree using the threat attribute data, the decision tree including at least one first node and a plurality of second nodes connected to the at least one first node, wherein:

first nodal data is generated and assigned to each second node based on at least one of the first threat attribute, the second threat attribute, the third threat attribute, the fourth threat attribute, the fifth threat attribute, or the sixth threat attribute, and

in response to receiving a security event file, executing one or more security tests, using the decision tree, for the security event file.

2. The method of claim 1 , wherein the security event file comprises at least one attack type, and wherein the executing the one or more security tests for the security event file using the decision tree comprises:

determining a risk value to assign the security event file;

assigning the risk value to the security event file; and

prioritizing one or more remediation operations against the at least one attack type.

3. The method of claim 1 , wherein the first nodal data comprises a first score assigned to a first leaf node comprised in the plurality of second nodes of the decision tree, the first score including a combination of:

a second score associated with a second leaf node comprised in the plurality of second nodes of the decision tree; and

a third score associated with a third leaf node comprised in the plurality of second nodes of the decision tree.

4. The method of claim 1 , wherein the threat attribute data further comprises one or more of:

a seventh threat attribute associated with the plurality of attack execution operations, the seventh threat attribute comprising application package data indicative of package-access information associated with executing the at least one attack execution operation comprised in the plurality of attack execution operations;

an eighth threat attribute associated with the plurality of attack execution operations, the eighth threat attribute comprising sub-operation data associated with executing at least one sub-attack execution operation associated with the at least one attack execution operation comprised in the plurality of attack execution operations; and

a ninth threat attribute associated with the plurality of attack execution operations, the ninth threat attribute comprising remediation data associated with mitigating against the at least one attack execution operation comprised in the plurality of attack execution operations.

5. The method of claim 1 , wherein the threat attribute data is used to automatically structure one or more parent nodes and child nodes of the decision tree.

6. The method of claim 1 , wherein the attack data comprises one or more of:

a framework based on an attack repository, the attack repository comprising one or more of the attacker or one or more attackers associated with the plurality of attack execution operations;

second attack data captured from multiple computing devices associated with multiple entities; and

one or more resources associated with the multiple computing devices.

7. The method of claim 6 , wherein:

the malware data comprises a group of malware samples that have a common code base;

the user data comprises user credential data or administrator credential data; and

the location data comprises data that indicates whether the at least one attack execution operation was locally executed or remotely executed relative to a location of the multiple computing devices.

8. The method of claim 6 , wherein the first nodal data is based on a grouping of a plurality of threat attributes correlated to threat tactics, threat techniques, or threat procedures associated with the framework.

9. The method of claim 6 , wherein:

the decision tree automatically balances threat attributes across different tactics associated with the framework to generate an attack kill-chain associated with the security event file;

the attack kill-chain indicates one or more attack execution operations for executing an attack campaign; and

the one or more security tests using the decision tree generates remediation data comprising one or more security operations that mitigate against the attack kill-chain.

10. The method of claim 6 , wherein the decision tree maps threat tactics, threat techniques, and threat practices associated with the framework to one or more scores assigned to one or more nodes of the decision tree.

11. A system comprising:

one or more computing system processors; and

memory storing instructions that, when executed by the one or more computing system processors, causes the system to:

receive attack data comprising a plurality of attack execution operations,

determine threat attribute data based on the attack data, the threat attribute data comprising:

a first threat attribute associated with the plurality of attack execution operations, the first threat attribute comprising threat-actor data indicative of an attacker associated with at least one attack execution operation comprised in the plurality of attack execution operations,

a second threat attribute associated with the plurality of attack execution operations, the second threat attribute indicative of malware data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a third threat attribute associated with the plurality of attack execution operations, the third threat attribute indicative of security tool data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a fourth threat attribute associated with the plurality of attack execution operations, the fourth threat attribute comprising user data associated with the at least one attack execution operation comprised in the plurality of attack execution operations,

a fifth threat attribute associated with the plurality of attack execution operations, the fifth threat attribute comprising location data associated with an attack execution operation comprised in the plurality of attack execution operations, and

a sixth threat attribute associated with the plurality of attack execution operations, the sixth threat attribute comprising operating system data associated with executing the at least one attack execution operation comprised in the plurality of attack execution operations; and

generate a decision tree using the threat attribute data, the decision tree including at least one first node and a plurality of second nodes connected to the at least one first node, wherein:

first nodal data is generated and assigned to each second node based on at least one of the first threat attribute, the second threat attribute, the third threat attribute, the fourth threat attribute, the fifth threat attribute, or the sixth threat attribute, and

in response to receiving a security event file, executing one or more security tests, using the decision tree, for the security event file.

12. The system of claim 11 , wherein the security event file comprises at least one attack type, and wherein the executing the one or more security tests for the security event file using the decision tree comprises:

determining a risk value to assign the security event file;

assigning the risk value to the security event file; and

prioritizing one or more remediation operations against the at least one attack type.

13. The system of claim 11 , wherein the first nodal data comprises a first score assigned to a first leaf node comprised in the plurality of second nodes of the decision tree, the first score including a combination of:

a second score associated with a second leaf node comprised in the plurality of second nodes of the decision tree; and

a third score associated with a third leaf node comprised in the plurality of second nodes of the decision tree.

14. The system of claim 11 , wherein the threat attribute data further comprises one or more of:

a seventh threat attribute associated with the plurality of attack execution operations, the seventh threat attribute comprising application package data indicative of package-access information associated with executing the at least one attack execution operation comprised in the plurality of attack execution operations;

an eighth threat attribute associated with the plurality of attack execution operations, the eighth threat attribute comprising sub-operation data associated with executing at least one sub-attack execution operation associated with the at least one attack execution operation comprised in the plurality of attack execution operations; and

a ninth threat attribute associated with the plurality of attack execution operations, the ninth threat attribute comprising remediation data associated with mitigating against the at least one attack execution operation comprised in the plurality of attack execution operations.

15. The system of claim 11 , wherein the threat attribute data is used to automatically structure one or more parent nodes and child nodes of the decision tree.

16. The system of claim 11 , wherein the attack data comprises one or more of:

a framework based on an attack repository, the attack repository comprising one or more of the attacker or one or more attackers associated with the plurality of attack execution operations;

second attack data captured from multiple computing devices associated with multiple entities; and

one or more resources associated with the multiple computing devices.

17. The system of claim 16 , wherein:

the malware data comprises a group of malware samples that have a common code base;

the user data comprises user credential data or administrator credential data; and

the location data comprises data that indicates whether the at least one attack execution operation was locally executed or remotely executed relative to a location of the multiple computing devices.

18. The system of claim 16 , wherein the first nodal data is based on a grouping of a plurality of threat attributes correlated to threat tactics, threat techniques, or threat procedures associated with the framework.

19. The system of claim 16 , wherein:

the decision tree automatically balances threat attributes across different tactics associated with the framework to generate an attack kill-chain associated with the security event file;

the attack kill-chain indicates one or more attack execution operations for executing an attack campaign; and

the one or more security tests using the decision tree generates remediation data comprising one or more security operations that mitigate against the attack kill-chain.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 14, 2022
From: TYAGI, ANKUR S.; DANI, MAYURESH VISHWAS
To: QUALYS, INC.
Reel/Frame 061420/0122 →
Continuity (1)
Related Publication 20230156017A1 · May 18, 2023
Cited By (1)
US 12,348,570