IP Library Granted Patent US 11,086,984
Granted Patent B2
US 11,086,984 · App. 15/636,965 · Granted Aug 10, 2021

Mobile device policy enforcement

Inventor: Michael Shannon (Vancouver, CA)
Assignee: Sophos Limited
G06F21/51G06F21/554H04L9/088H04L9/0891H04L9/0894H04L63/20H04W12/082H04W12/10H04W12/128G06F8/61G06F2221/033H04L9/08H04L63/06H04L63/1433H04L2209/80
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 11,086,984
App. No.
15/636,965
Granted
Aug 10, 2021
Kind
B2
Abstract

In general, in one aspect, a method includes receiving software code with an invalid characteristic, repeatedly attempting to execute the software code with the invalid characteristic on a device, and in response to successful execution of the software code with the invalid characteristic, taking an action. The action may include an action to remediate the device.

Claims (26)

1. A non-transitory computer-readable medium comprising instructions, the instructions when executed causing one or more processors to:

execute a local security agent on a device, the local security agent enforcing a security policy requiring an operating system of the device to check that software code has a valid signature before permitting execution of the software code;

attempt to execute the software code with an invalid signature on the device, the invalid signature preventing execution of the software code on the device if the operating system meets the security policy;

upon unsuccessful execution of the software code with the invalid signature on the device, repeat the attempt to execute the software code with the invalid signature on the device until a given attempt executes the software code on the device, wherein repeating the attempt to execute the software code includes waiting a predetermined time interval between each attempt; and

in response to successful execution of the software code with the invalid signature, take an action to remediate the device, the action including isolating the device from a network and requiring changes to the operating system to check that the software code has the valid signature before permitting execution of the software code.

2. The computer-readable medium of claim 1 , wherein the instructions further cause the one or more processors to receive the software code with the invalid signature.

3. The computer-readable medium of claim 1 , wherein the action to remediate the device includes one or more of: reinstall software on the device, apply changes to software on the device, run remediating software on the device, report a health status of the device that is an unhealthy status, report a health status of the device that indicates that the device is in violation of policy, notify a user, or notify an administrator.

4. A method comprising:

executing a local security agent on a device, the local security agent enforcing a security policy requiring an operating system of the device to check that software code has a valid signature before permitting execution of the software code;

repeatedly attempting to execute the software code with an invalid signature on the device until one of the repeated attempts to execute the software code on the device is successful, wherein repeatedly attempting to execute the software code includes waiting a predetermined time interval between each attempt, the device having a security policy specifying that only software code with a valid signature is permitted to execute on the device, the invalid signature preventing execution of the software code with the invalid signature if the operating system meets the security policy; and

in response to successfully executing the software code with the invalid signature, taking a consequential action by the device, the consequential action including requiring changes to the operating system to check that the software code has the valid signature before permitting execution of the software code.

5. The method of claim 4 , further comprising, receiving the software code with the invalid signature.

6. The method of claim 4 , wherein the method further comprises installing the software code with the invalid signature on the device.

7. The method of claim 4 , wherein the consequential action comprises an action to remediate the device, the action comprising one or more of: reinstalling software on the device, applying changes to software on the device, reporting a health status of the device that is in violation of policy.

8. The method of claim 4 , wherein the consequential action comprises one or more of: notifying a user, and notifying an administrator.

9. A system, comprising:

one or more processors;

a non-transitory computer-readable medium comprising instructions, the instructions when executed causing the one or more processors to perform operations, comprising:

execute a local security agent on a device, the local security agent enforcing a security policy requiring an operating system of the device to check that software code has a valid signature before permitting execution of the software code;

receive the software code with an invalid signature;

repeatedly attempt to execute the software code with the invalid signature on the device until one of the repeated attempts to execute the software code with the invalid signature is successful, wherein repeatedly attempting to execute the software code includes waiting a predetermined time interval between each attempt, wherein the invalid signature causes the device to prevent execution of the software code with the invalid signature if the operating system meets a security policy specifying that only software code with a valid signature is permitted to execute on the device; and

in response to successfully executing the software code with the invalid signature, remediate the device and confirm that the operating system checks that the software code has the valid signature before permitting execution of the software code.

10. The system of claim 9 , wherein the operations further comprise, store the software code with the invalid signature on the device.

11. The system of claim 9 , wherein remediating the device further includes applying changes to an operating system, software, or configuration of the device.

12. The system of claim 9 , wherein remediating the device further includes reporting a health status of the device.

13. The system of claim 12 , wherein reporting the health status of the device is that the device includes reporting that the device is in violation of the security policy.

Assignments (4)
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 →
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 ASSIGNOR'S INTEREST Recorded Oct 20, 2017
From: SHANNON, MICHAEL
To: SOPHOS LIMITED
Reel/Frame 043911/0811 →
Cited By (7)
US 12,282,541 US 12,292,964 US 12,292,965 US 12,380,204 US 12,475,213 US 12,518,030 US 12,682,040