# US 2021/0334359 A1 · Mobile device policy enforcement

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0334359 A1
- Document ID: US20210334359A1
- Status: Published application
- Kind: A1
- Application number: 17/371,948
- Filed: 2021-07-09
- Published: 2021-10-28
- Earliest claimed: 2016-06-30
- Assignees: Sophos Limited
- Applicants: Sophos Limited
- Inventors: Michael Shannon
- Web page: https://patentgrep.com/patent/US20210334359A1

## CPC

- G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
- G06F 21/554: {involving event detection and direct action}
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04W 12/082: using revocation of authorisation
- H04W 12/10: Integrity
- H04W 12/128: Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware
- G06F 8/61: Installation
- G06F 2221/033: Test or assess software
- H04L 9/08: Key distribution {or management, e.g. generation, sharing or updating, of cryptographic keys or passwords (network architectures or network communication protocols for supporting key management in a packet data network H04L63/06)}
- H04L 63/06: {for supporting key management in a packet data network (cryptographic mechanisms or cryptographic arrangements for key management H04L9/08)}
- H04L 63/1433: {Vulnerability analysis}
- H04L 2209/80: Wireless
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## 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

### Claim 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 of an enterprise network, 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 successfully executes the software code with the invalid signature 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.

### Claim 2 (depends on 1)

The computer-readable medium of claim 1, wherein the action to remediate the device includes requiring one or more changes to the operating system to check that the software code has the valid signature before permitting execution of the software code.

### Claim 3 (depends on 2)

The computer-readable medium of claim 2, wherein the action to remediate the device includes applying the one or more changes to the operating system on the device.

### Claim 4 (depends on 1)

The computer-readable medium of claim 1, wherein the action to remediate the device includes reinstalling software on the device.

### Claim 5 (depends on 1)

The computer-readable medium of claim 1, wherein the action to remediate the device includes applying changes to software on the device.

### Claim 6 (depends on 1)

The computer-readable medium of claim 1, wherein the action to remediate the device further includes notifying a threat management facility of the enterprise network of a potential security breach of the device.

### Claim 7

A method, comprising:
executing a local security agent on a compute instance of an enterprise network, the local security agent enforcing a security policy requiring an operating system of the compute instance 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 compute instance until one of the repeated attempts to execute the software code on the compute is successful, wherein repeatedly attempting to execute the software code includes waiting a predetermined time interval between each attempt, the compute instance having the security policy, 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, causing a remedial action to be taken by the compute instance.

### Claim 8 (depends on 7)

The method of claim 7, wherein the remedial action includes requiring one or more changes to the operating system to check that the software code has the valid signature before permitting execution of the software code.

### Claim 9 (depends on 8)

The method of claim 8, wherein the remedial action includes applying the one or more changes to the operating system on the compute instance.

### Claim 10 (depends on 7)

The method of claim 7, wherein the remedial action includes reinstalling software on the compute instance.

### Claim 11 (depends on 7)

The method of claim 7, wherein the remedial action includes applying changes to software on the compute instance.

### Claim 12 (depends on 7)

The method of claim 7, wherein the remedial action includes notifying a threat management facility of the enterprise network of a potential security breach of the compute instance.

### Claim 13 (depends on 7)

The method of claim 7, wherein the remedial action includes one or more of notify a user and notify an administrator.

### Claim 14

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 compute instance of an enterprise network, the local security agent enforcing a security policy requiring an operating system of the compute instance 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 compute instance 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 compute instance to prevent 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 an action to remediate the compute instance.

### Claim 15 (depends on 14)

The system of claim 14, wherein the action to remediate the compute instance includes requiring changes to the operating system to check that the software code has the valid signature before permitting execution of the software code.

### Claim 16 (depends on 15)

The system of claim 15, wherein the action to remediate the compute instance includes applying the required changes to the operating system on the compute instance.

### Claim 17 (depends on 14)

The system of claim 14, wherein the action to remediate the compute instance includes reinstalling software on the compute instance.

### Claim 18 (depends on 14)

The system of claim 14, wherein the action to remediate the compute instance includes applying changes to software on the compute instance.

### Claim 19 (depends on 14)

The system of claim 14, wherein the action to remediate the compute instance includes notifying one or more of a user and an administrator.

### Claim 20 (depends on 14)

The system of claim 14, wherein the action to remediate the compute instance includes notifying a threat management facility of the enterprise network of a potential security breach of the compute instance.
