Policy-based selection of remediation

• US 9,392,024 B2
• Filed: 08/18/2015
• Issued: 07/12/2016
• Est. Priority Date: 09/03/2004
• Status: Active Grant

• Current Assignee: Fortinet Inc.
• Original Assignee: Fortinet Inc.
• Inventors: Ogura, James Le, Bezilla, Daniel B., Immordino, John L.
• Primary Examiner(s): Revak, Christopher
• Application Number:
  US14/829,397
• Publication Number:
  US 20150358360A1
• Time in Patent Office: 329 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 21/552 involving long-term monitoring or reporting
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: H04L 43/0876 Network utilisation, e.g. volume of load or congestion level
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

Methods and systems for remediating a security policy violation on a computer system are provided. According to one embodiment, information regarding a program-code-based operational state of a host asset is collected by a light weight sensor (LWS) running on the host asset via a survey tool. The information is transmitted by the LWS to a remote server via an external network. Multiple security policies are enforced by the remote server with respect to the host asset based on the received information including determining whether the program-code-based operational state of the host asset represents a violation of one or more security policies, by evaluating, the received information with respect to the security policies, each of which define at least one parameter condition violation of which is potentially indicative of unauthorized activity on the host asset or manipulation of the host asset making the host asset vulnerable to attack.

Claims

1. A method comprising:

collecting, by a light weigh sensor (LWS) running on a host asset of a plurality of monitored host assets within an enterprise network, information regarding a program-code-based operational state of the host asset via a survey tool installed on the host asset;

transmitting, by the LWS, the information to a remote server that is in a client-server relationship with the LWS via an external network coupling the enterprise network and the remote server in communication; and

enforcing, by the remote server, a plurality of security policies with respect to the host asset based on the received information including determining whether the program-code-based operational state of the host asset represents a violation of one or more security policies of the plurality of security policies, by evaluating, the received information with respect to the plurality of security policies, wherein each security policy of the plurality of security policies define at least one parameter condition violation of which is potentially indicative of unauthorized activity on the host asset or manipulation of the host asset making the host asset vulnerable to attack.

2. The method of claim 1, wherein the host asset comprises a network-attached storage (NAS) device, a router, a switch, a personal computer or a printer.

3. The method of claim 2, further comprising when a result of the determining is affirmative, then causing, by the remote server, the host asset to perform one or more remediation actions.

4. The method of claim 2, further comprising when a result of the determining is affirmative, then causing, by the remote server, one or more selected remediations to be deployed to the host asset based on the violation.

5. The method of claim 2, further comprising when a result of the determining is affirmative, then causing, by the remote server, one or more actions or operations to be carried out on the host asset.

6. The method of claim 5, wherein the one or more actions or operations at least in part implement a precautionary measure to improve reliability, availability or survivability of the host asset.

7. The method of claim 5, wherein the one or more actions or operations are suited to remediating circumstances of the violation.

8. The method of claim 3, further comprising maintaining, by the remote server, a policy database having stored therein the plurality of security policies.

9. The method of claim 8, further comprising maintaining, by the remote server, a remediation database having stored therein information regarding a plurality of remediation actions including the one or more remediation actions.

10. The method of claim 2, wherein the violation relates to existence or non-existence of a particular application on the host asset.

11. The method of claim 2, wherein the violation is based at least in part on a version of a particular application on the host asset.

12. The method of claim 2, wherein the violation is based at least in part on whether a patch associated with a particular application has been installed on the host asset.

13. The method of claim 2, wherein the violation is based at least in part on a version of an operating system or a type of the operating system running on the host asset.

14. The method of claim 2, wherein the violation relates to whether a particular process is running on the host asset.

15. The method of claim 4, further comprising prior to said causing, by the remote server, the remediation to be deployed to the host asset, determining whether the remediation has been configured for automatic deployment.

16. The method of claim 2, wherein the violation relates to one or more of:

presence of an unknown application or a rogue application on the host asset;

an operating system test relating to an operating system being run by the host asset;

whether a removable storage device is connected to the host asset;

a particular process is running on the host asset; and

a state associated with one or more ports of the host asset.

17. The method of claim 2, wherein the violation relates to one or more of:

existence or non-existence of a particular file on the host asset;

a location of a particular file on the host asset; and

one or more permissions associated with the particular file.

18. The method of claim 2, wherein the information regarding the program-code-based operational state comprises information indicative of one or more drivers installed on the host asset.

19. The method of claim 18, wherein the violation relates to existence or non-existence of a particular type of driver on the host asset.

20. The method of claim 19, wherein the particular type of driver comprises a universal serial bus (USB) driver.