IP Library Granted Patent US 8,832,828
Granted Patent B2
US 8,832,828 · App. 12/411,504 · Granted Sep 9, 2014

Dynamic scanning based on compliance metadata

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 8,832,828
App. No.
12/411,504
Granted
Sep 9, 2014
Kind
B2
Abstract

In embodiments of the present invention improved capabilities are described for systems, methods, and devices that assess a metadata factor associated with metadata of code to determine a compliance state of said code; assign or adjust a security sensitivity factor based at least in part on said compliance state of said code; and provide a security facility with an indicator of how aggressively to monitor the code for malicious code infection.

Claims (22)

1. A computer program product embodied in a non-transitory computer readable medium that, when executing on one or more computers, performs the steps of:

a. assessing a metadata factor associated with metadata of code using an endpoint security facility to determine a compliance state of said code representing a state of compliance with an enterprise policy related to a risk posed by the code;

b. at least one of assigning and adjusting a security sensitivity factor based at least in part on said compliance state of said code;

c. repeating step (a) and step (b) at least once before executing the code, and least once while executing the code, and at least once after executing the code; and

d. providing a remote security facility with an indicator of how to treat said code, wherein said indicator is based on said security sensitivity factor, wherein the indicator includes an indication of at least one of how aggressively to monitor said code and how aggressively to enforce a policy related to said code, and wherein the indicator includes a level of monitoring for the code including a frequency for further scans of the code.

2. The computer program product of claim 1 , wherein said metadata factor is a patch level of said code.

3. The computer program product of claim 1 , wherein said metadata factor is a software version of said code.

4. The computer program product of claim 1 , wherein said metadata factor is a certification of said code.

5. The computer program product of claim 1 , wherein said metadata factor is at least one of a probability that said code is infected with malicious code and a probability that said code is vulnerable to manipulation.

6. The computer program product of claim 1 , wherein said metadata factor is an identity of the vendor of said code.

7. The computer program product of claim 1 , wherein said metadata factor is an impact of the code being infected by malicious code.

8. The computer program product of claim 1 , wherein said indicator relates to a frequency with which said code should be monitored.

9. The computer program product of claim 1 , wherein said code is an executable file.

10. The computer program product of claim 1 , wherein said code is a software application.

11. The computer program product of claim 1 , wherein said code is interpretable content.

12. The computer program product of claim 11 , wherein said interpretable content is at least one of scripts and non-compiled languages.

13. The computer program product of claim 1 further comprising: performing a remedial action based on said security sensitivity factor.

14. The computer program product of claim 13 , wherein said remedial action is updating the patch level of the code.

15. The computer program product of claim 1 , wherein said remedial action is adding a remedial software component to the code, wherein the remedial software component is adapted to prevent a malicious function.

16. The computer program product of claim 1 , wherein the step of at least one of assigning and adjusting a security sensitivity factor based at least in part on said compliance state of said code adjusting the sensitivity factor further comprises adjusting the sensitivity factor based on a policy setting.

17. The computer program product of claim 16 , wherein said policy is resident on an endpoint computer.

18. The computer program product of claim 16 , wherein said policy is updated by a central policy management system.

Assignments (9)
RELEASE OF SECURITY INTEREST IN PATENTS AT R/F 053476/0681 Recorded Mar 9, 2021
From: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT
To: SOPHOS LIMITED
Reel/Frame 056469/0815 →
RELEASE OF SECURITY INTEREST Recorded Jul 28, 2020
From: DEUTSCHE BANK AG NEW YORK BRANCH
To: SOPHOS LIMITED
Reel/Frame 053334/0220 →
PATENT SECURITY AGREEMENT FIRST LIEN Recorded Jul 6, 2020
From: SOPHOS LIMITED
To: GOLDMAN SACHS BANK USA, AS COLLATERAL AGENT
Reel/Frame 053124/0350 →
PATENT SECURITY AGREEMENT SECOND LIEN Recorded Jul 6, 2020
From: SOPHOS LIMITED
To: OWL ROCK CAPITAL CORPORATION, AS COLLATERAL AGENT
Reel/Frame 053476/0681 →
ASSIGNMENT OF SECURITY INTEREST Recorded Feb 3, 2014
From: JPMORGAN CHASE BANK, N.A.
To: DEUTSCHE BANK AG NEW YORK BRANCH, AS COLLATERAL AGENT
Reel/Frame 032152/0883 →
CHANGE OF NAME Recorded Apr 11, 2013
From: SOPHOS PLC
To: SOPHOS LIMITED
Reel/Frame 030194/0299 →
SECURITY INTEREST Recorded May 11, 2012
From: RBC EUROPE LIMITED, AS EXISTING ADMINISTRATION AGENT AND COLLATERAL AGENT
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 028198/0285 →
SECURITY AGREEMENT Recorded Aug 8, 2011
From: SOPHOS LIMITED F/K/A SOPHOS PLC
To: ROYAL BANK OF CANADA EUROPE LIMITED, AS COLLATERAL AGENT
Reel/Frame 026717/0424 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2009
From: LYNE, JAMES I.G.; THOMAS, ANDREW J.
To: SOPHOS PLC
Reel/Frame 022453/0951 →