Advanced asset tracking and correlation

• US 9,591,027 B2
• Filed: 02/17/2015
• Issued: 03/07/2017
• Est. Priority Date: 02/17/2015
• Status: Active Grant

• Current Assignee: Qualys Incorporated
• Original Assignee: Qualys Incorporated
• Inventors: Molloy, Sean M., Wirges, Matthew L., Sonawane, Amol S.
• Primary Examiner(s): Smithers, Matthew
• Assistant Examiner(s): MASSIE, DAVID H
• Application Number:
  US14/624,335
• Publication Number:
  US 20160241595A1
• Time in Patent Office: 749 Days
• Field of Search: 726/1
• US Class Current: 1/1
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/24578 using ranking
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G06F 40/205 Parsing
• CPC Class Codes: H04L 63/1408 by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1433 Vulnerability analysis
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

A security management system may be remotely deployed (e.g., using a cloud-based architecture) to add security to an enterprise network. For example, the security management system may scan assets within the enterprise network for vulnerabilities and may receive data chunks from these scans. The security management system may also receive data chunks from other sources, and, as a result, the system may handle data chunks having many different formats and attributes. When the security management system tries to associate data chunks to assets, there may not be a globally unique identifier that is applicable for all received data chunks. Provided in the present disclosure are exemplary techniques for tracking assets across a network using an asset correlation engine that can flexibly match data chunks to assets based on the attribute or attributes that are available within the data chunks.

Claims

1. A security management system for tracking a plurality of assets in a network using a plurality of attributes, the security management system comprising:

an asset database operable to store a plurality of asset entries, wherein one or more of the plurality of asset entries have asset entry values for at least one of the plurality of attributes; and

an asset correlation engine in communication with the asset database, the asset correlation engine operable to receive a data chunk associated with a target asset included in the plurality of assets;

wherein the asset correlation engine is further operable to parse the data chunk to determine data chunk values for at least one of the plurality of attributes;

wherein the asset correlation engine is further operable to scan the asset database using the data chunk values and a correlation metric to find a matching asset entry that corresponds with the target asset, thereby determining that the data chunk is associated with the target asset;

wherein the asset correlation engine is further operable to determine asset scores for at least some of the plurality of asset entries using the correlation metric, and

wherein the asset correlation engine finds the matching asset entry by comparing the asset scores;

wherein the correlation metric comprises a plurality of attribute weights corresponding to the plurality of attributes,

wherein at least some of the plurality of attributes weights are used to calculate the asset scores,

wherein the plurality of attributes comprises a strongly correlated attribute and a loosely correlated attribute, and

wherein the strongly correlated attribute has a larger attribute weight than the loosely correlated attribute; and

wherein the plurality of attributes further comprises a moderately correlated attribute having an attribute weight that is smaller than that of the strongly correlated attribute and larger than that of the loosely correlated attribute,

wherein the attribute weight of the highly correlated attribute is 1.5 to 40 times as large as the attribute weight of the moderately correlated attribute; and

wherein the attribute weight of the moderately correlated attribute is 1.5 to 25 times as large as the attribute weight of the loosely correlated attribute.

2. The security management system of claim 1, wherein a new asset entry is created in the asset database if none of the asset scores are above a threshold value.

3. The security management system of claim 1,

wherein the attribute weight of a first attribute from the plurality of attributes comprises a positive attribute weight for a match of a data chunk value and an asset entry value corresponding to the first attribute and a negative attribute weight for a mismatch of the data chunk value and the asset entry value corresponding to the first attribute;

and

wherein the positive and negative attribute weights are different in magnitude.

4. The security management system of claim 1, wherein the asset correlation engine is further operable to update the matching asset entry to include at least one of the data chunk values if the matching asset entry does not have the at least one data chunk value before being found by the asset correlation engine.

5. The security management system of claim 1,

wherein the asset correlation engine is further operable to select a data chunk value from the data chunk values and test the selected data chunk value using an exclusion rule;

and

wherein the asset correlation engine is further operable to disregard an attribute corresponding to the selected data chunk value when finding the matching asset entry if the selected data chunk value satisfies the exclusion rule.

6. The security management system of claim 5, wherein the exclusion rule comprises comparing the selected data chunk value to one of a single value, a range of values, and a regular expression.

7. The security management system of claim 1,

wherein the asset correlation engine is further operable to receive the data chunk from an agent that is installed on the target asset;

wherein the plurality of attributes comprises agent identification; and

wherein the data chunk values comprise an agent identification value corresponding to the agent identification, the agent identification value being established by the agent that is installed on the target asset.

8. The security management system of claim 7, wherein the agent is operable to write the agent identification value to a local memory device associated with the target asset.

9. The security management system of claim 1, wherein the asset correlation engine is further operable to receive the data chunk from a scanner that is operable to scan the target asset.

10. The security management system of claim 1, wherein the target asset comprises one of a desktop workstation, a server, a laptop, a tablet, a mobile phone, and a virtual machine.

11. The security management system of claim 1, wherein the plurality of attributes comprises at least one of an IP address attribute, a DNS name attribute, a network attribute, an operating system attribute, a NetBIOS name attribute, and instance identification.

12. A method for tracking a plurality of assets in a network using a plurality of attributes, the method comprising:

storing, by an asset database, a plurality of asset entries, wherein one or more of the plurality of asset entries have asset entry values for at least one of the plurality of attributes;

receiving, by an asset correlation engine in communication with the asset database, a data chunk associated with a target asset included in the plurality of assets;

parsing, by the asset correlation engine, the data chunk to determine data chunk values for at least one of the plurality of attributes; and

scanning, by the asset correlation engine, the asset database using the data chunk values and a correlation metric to find a matching asset entry that corresponds with the target asset, thereby determining that the data chunk is associated with the target asset,

determining, by the asset correlation engine, asset scores for at least some of the plurality of asset entries using the correlation metric; and

finding, by the asset correlation engine, the matching asset entry by comparing the asset scores;

wherein the correlation metric comprises a plurality of attribute weights corresponding to the plurality of attributes,

wherein at least some of the plurality of attributes weights are used to calculate the asset scores,

wherein the plurality of attributes comprises a strongly correlated attribute and a loosely correlated attribute,

and wherein the strongly correlated attribute has a larger attribute weight than the loosely correlated attribute; and

wherein the plurality of attributes further comprises a moderately correlated attribute having an attribute weight that is smaller than that of the strongly correlated attribute and larger than that of the loosely correlated attribute,

wherein the attribute weight of the highly correlated attribute is 1.5 to 40 times as large as the attribute weight of the moderately correlated attribute; and

wherein the attribute weight of the moderately correlated attribute is 1.5 to 25 times as large as the attribute weight of the loosely correlated attribute.

13. The method of claim 12, further comprising:

adding to the asset database a new asset entry if none of the asset scores are above a threshold value.

14. The method of claim 12, wherein the plurality of attributes comprises at least one of an IP address attribute, a DNS name attribute, a network attribute, an operating system attribute, a NetBIOS name attribute, agent identification, and instance identification.