IP Library Granted Patent US 7,861,299
Granted Patent B1
US 7,861,299 · App. 11/836,251 · Granted Dec 28, 2010

Threat detection in a network security system

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 7,861,299
App. No.
11/836,251
Granted
Dec 28, 2010
Kind
B1
Abstract

A network security system is provided that receives information from various sensors and can analyze the received information. In one embodiment of the present invention, such a system receives a security event from a software agent. The received security event includes a target address and an event signature, as generated by the software agent. The event signature can be used to determine a set of vulnerabilities exploited by the received security event, and the target address can be used to identify a target asset within the network. By accessing a model of the target asset, a set of vulnerabilities exposed by the target asset can be retrieved. Then, a threat can be detected by comparing the set of vulnerabilities exploited by the security event to the set of vulnerabilities exposed by the target asset.

Claims (46)

1. A computer-implemented method performed by a manager module for determining whether a security event represents a threat to a network, the method comprising:

receiving the security event from an agent, the security event including an indication of a target asset;

determining a first set of one or more vulnerabilities exploited by the received security event;

determining a second set of one or more vulnerabilities exposed by the target asset; and

detecting a threat by determining a vulnerability common to the first set of vulnerabilities and the second set of vulnerabilities.

2. The method of claim 1 , further comprising:

if no common vulnerability is shared by both the first set of vulnerabilities and the second set of vulnerabilities, determining that the security event does not represent the threat to the network.

3. The method of claim 1 , further comprising prioritizing the security event.

4. The method of claim 3 , wherein prioritizing the security event comprises determining a priority based on the security event.

5. The method of claim 4 , wherein determining the priority based on the security event comprises determining the priority based on an importance of the target asset.

6. The method of claim 4 , wherein determining the priority based on the security event comprises determining the priority based on a danger inherent in the security event.

7. The method of claim 4 , wherein determining the priority based on the security event comprises determining the priority based on a relevance of the security event.

8. The method of claim 4 , wherein determining the priority based on the security event comprises determining the priority based on a configuration of the target asset.

9. The method of claim 1 , wherein the indication of the target asset comprises an address associated with the target asset.

10. The method of claim 9 , wherein the address associated with the target asset comprises an Internet Protocol (IP) address.

11. The method of claim 1 , wherein the target asset comprises a network device.

12. The method of claim 1 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on an event signature of the security event.

13. The method of claim 1 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on a type of the security event.

14. The method of claim 1 , wherein determining the second set of vulnerabilities comprises determining the second set of vulnerabilities based on a model of the target asset.

15. The method of claim 14 , further comprising determining a priority based on a reliability of the model of the target asset.

16. A machine-readable medium having stored thereon data representing instructions that, when executed by a processor in a manager module, cause the processor to perform a method for determining whether a security event represents a threat to a network, the method comprising:

receiving the security event from an agent, the security event including an indication of a target asset;

determining a first set of one or more vulnerabilities exploited by the received security event;

determining a second set of one or more vulnerabilities exposed by the target asset; and

detecting a threat by determining a vulnerability common to the first set of vulnerabilities and the second set of vulnerabilities.

17. A system for determining whether a security event represents a threat to a network, the system comprising:

a machine-readable medium storing machine-readable instructions for performing a method, the method comprising:

receiving the security event from an agent, the security event including an indication of a target asset;

determining a first set of one or more vulnerabilities exploited by the received security event;

determining a second set of one or more vulnerabilities exposed by the target asset; and

detecting a threat by determining a vulnerability common to the first set of vulnerabilities and the second set of vulnerabilities; and

a processor configured to execute the machine-readable instructions stored by the machine-readable medium.

18. The machine-readable medium of claim 16 , wherein the method further comprises:

if no common vulnerability is shared by both the first set of vulnerabilities and the second set of vulnerabilities, determining that the security event does not represent the threat to the network.

19. The machine-readable medium of claim 16 , wherein the method further comprises determining a priority based on the security event.

20. The machine-readable medium of claim 16 , wherein the indication of the target asset comprises an address associated with the target asset.

21. The machine-readable medium of claim 16 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on an event signature of the security event.

22. The machine-readable medium of claim 16 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on a type of the security event.

23. The machine-readable medium of claim 16 , wherein determining the second set of vulnerabilities comprises determining the second set of vulnerabilities based on a model of the target asset.

24. The system of claim 17 , wherein the method further comprises:

if no common vulnerability is shared by both the first set of vulnerabilities and the second set of vulnerabilities, determining that the security event does not represent the threat to the network.

25. The system of claim 17 , wherein the method further comprises determining a priority based on the security event.

26. The system of claim 17 , wherein the indication of the target asset comprises an address associated with the target asset.

27. The system of claim 17 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on an event signature of the security event.

28. The system of claim 17 , wherein determining the first set of vulnerabilities comprises determining the first set of vulnerabilities based on a type of the security event.

29. The system of claim 17 , wherein determining the second set of vulnerabilities comprises determining the second set of vulnerabilities based on a model of the target asset.

Assignments (10)
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0577 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC)
Reel/Frame 063560/0001 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
CHANGE OF NAME Recorded Aug 8, 2019
From: ENTIT SOFTWARE LLC
To: MICRO FOCUS LLC
Reel/Frame 050004/0001 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ENTIT SOFTWARE LLC; ARCSIGHT, LLC
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0577 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 9, 2017
From: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
To: ENTIT SOFTWARE LLC
Reel/Frame 042746/0130 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 9, 2015
From: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
To: HEWLETT PACKARD ENTERPRISE DEVELOPMENT LP
Reel/Frame 037079/0001 →
CERTIFICATE OF CONVERSION Recorded Nov 16, 2012
From: ARCSIGHT, INC.
To: ARCSIGHT, LLC.
Reel/Frame 029308/0908 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 16, 2012
From: ARCSIGHT, LLC.
To: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P.
Reel/Frame 029308/0929 →
MERGER Recorded Dec 23, 2010
From: PRIAM ACQUISITION CORPORATION
To: ARCSIGHT, INC.
Reel/Frame 025525/0172 →