# US 2004/0025015 A1 · System and method for the managed security control of processes on a computer system

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

- Number: US 2004/0025015 A1
- Document ID: US20040025015A1
- Status: Published application
- Kind: A1
- Application number: 10/336,299
- Filed: 2003-01-03
- Published: 2004-02-05
- Earliest claimed: 2002-01-04
- Assignees: Internet Security Systems, Inc.
- Inventors: Thomas James Satterlee; William Frank Hackenberger
- Web page: https://patentgrep.com/patent/US20040025015A1

## CPC

- G06F 21/552: {involving long-term monitoring or reporting}
- G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/554: {involving event detection and direct action}
- G06F 21/565: {by checking file integrity}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/629: {to features or functions of an application}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- G06F 2221/2149: Restricted operating environment
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Managing and controlling the execution of software programs with a computing device to protect the computing device from malicious activities. A protector system implements a two-step process to ensure that software programs do not perform malicious activities which may damage the computing device or other computing resources to which the device is coupled. In the first phase, the protector system determines whether a software program has been previously approved and validates that the software program has not been altered. If the software program is validated during the first phase, this will minimize or eliminate security monitoring operations while the software program is executing during the second phase. If the software program cannot be validated, the protector system enters the second phase and detects and observes executing activities at the kernel level of the operating system so that suspicious actions can be anticipated and addressed before they are able to do harm to the computing device.

## Claims

### Claim 1

A computer-implemented method for implementing security for a computing device, comprising the steps of:
identifying an allowed program that is permitted to execute on the computing device;
receiving a signal that a new program is going to be executed on the computing device;
suspending the execution of the new program on the computing device;
determining whether the new program is the same as the allowed program;
if the new program is the same as the allowed program, permitting the new program to execute on the computing device; and
if the new program is not the same as the allowed program, monitoring the new program while allowing it to execute on the computing device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the step of receiving a signal that a new program is going to be executed is performed at the operating system kernel of the computing device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the step of monitoring the new program while allowing it to execute is performed at the operating system kernel of the computing device.

### Claim 4 (depends on 1)

The method of claim 1, wherein the step of determining whether the new program is the same as the allowed program comprises:
computing a checksum for the new program, and
comparing the new program's checksum to a checksum for the allowed program.

### Claim 5 (depends on 1)

The method of claim 1, wherein the step of determining whether the new program is the same as the allowed program comprises determining whether the new program has been modified.

### Claim 6 (depends on 1)

The method of claim 1, wherein the step of monitoring the new program while allowing it to execute comprises controlling the files the program attempts to access during execution of the new program on the computing device.

### Claim 7 (depends on 1)

The method of claim 1, wherein the step of monitoring the new program while allowing it to execute comprises controlling the registry settings the new program attempts to access during execution of the new program on the computing device.

### Claim 8 (depends on 1)

The method of claim 1, wherein the step of monitoring the new program while allowing it to execute comprises controlling the network activity of the new program.

### Claim 9 (depends on 1)

The method of claim 1, wherein the step of monitoring the new program while allowing it to execute comprises determining whether a user has previously approved operation of the new program.

### Claim 10 (depends on 1)

The method of claim 1, further comprising the step of terminating the execution of the new program if the program performs suspicious activities.

### Claim 11 (depends on 1)

The method of claim 1, further comprising the step of taking remedial measures to protect the security of other computing device components if the new program is not the same as the allowed program.

### Claim 12 (depends on 1)

A computer-readable medium having computer-executable instructions for performing the steps recited in claim 1.

### Claim 13

A computer-implemented method for implementing security for a computing device comprising the steps of:
interrupting the loading of a new program for operation with the computing device;
validating the new program;
if the new program is validated, permitting the new program to continue loading and to execute in connection with the computing device;
if the new program is not validated, monitoring the new program while it loads and executes in connection with the computing device.

### Claim 14 (depends on 13)

The method of claim 13, wherein the step of interrupting the loading of a new program comprises:
intercepting a signal from the computing device's operating system that the new program is loading, and
suspending the loading of the new program.

### Claim 15 (depends on 13)

The method of claim 13, wherein the step of monitoring the new program comprises intercepting a signal from the computing device's operating system.

### Claim 16 (depends on 13)

The method of claim 13, wherein the step of validating the new program comprises determining whether the new program corresponds with an approved program.

### Claim 17 (depends on 13)

The method of claim 13, wherein the step of validating the new program comprises comparing a checksum for the new program with a previously determined checksum.

### Claim 18 (depends on 13)

The method of claim 13, wherein the step of validating the new program comprises analyzing characteristics of the new program.

### Claim 19 (depends on 13)

The method of claim 13, wherein the step of monitoring the new program comprises controlling the files the new program attempts to access during execution of the new program.

### Claim 20 (depends on 13)

A computer-readable medium having computer-executable instructions for performing the steps recited in claim 13.

### Claim 21

A computer-implemented method for performing security for a computing device during a pre-execution phase comprising the steps of:
identifying an allowed program that is permitted to execute with the computing device;
receiving a signal that a new program is being loaded for execution with the computing device;
suspending the loading of the new program;
comparing the new program to the allowed program; and
determining whether the new program is valid.

### Claim 22 (depends on 21)

The method of claim 21, wherein the step of receiving a signal comprises receiving a signal from the computing device's operating system kernel.

### Claim 23 (depends on 21)

The method of claim 21, wherein the step of comparing the new program to the allowed program comprises comparing a checksum of the new program to a checksum of the allowed program.

### Claim 24 (depends on 21)

The method of claim 21, wherein the step of determining whether the new program is valid comprises determining whether a checksum of the new program corresponds to a checksum of the allowed program.

### Claim 25 (depends on 21)

A computer-readable medium having computer-executable instructions for performing the steps recited in claim 21.

### Claim 26

A computer-implemented method for performing security for a computing device during an execution phase comprising the steps of:
intercepting a call to open a file from the computing device's operating system;
determining whether the file is restricted;
if the file is restricted, taking remedial action to protect the computing device; and
if the file is not restricted, permitting the call to open the file.

### Claim 27 (depends on 26)

The method of claim 26, further comprising the step of receiving an instruction to monitor a call from an executing program.

### Claim 28 (depends on 26)

The method of claim 26, further comprising the step of defining files that are restricted from access.

### Claim 29 (depends on 28)

The method of claim 28, wherein the step of defining files that are restricted comprises designating a file that cannot be accessed in response to the call.

### Claim 30 (depends on 28)

The method of claim 28, wherein the step of defining files that are restricted comprises designating a file that cannot be modified in response to the call.

### Claim 31 (depends on 26)

The method of claim 26, further comprising the step of alerting a security management module of the presence of a malicious program.

### Claim 32 (depends on 26)

The method of claim 26, wherein the step of taking remedial action comprises terminating the call.

### Claim 33 (depends on 26)

The method of claim 26, wherein the step of taking remedial action comprises alerting another security module of the existence of the call.

### Claim 34 (depends on 26)

The method of claim 26, wherein the step of taking remedial action comprises notifying the user of the existence of the call.

### Claim 35 (depends on 26)

A computer-readable medium having computer-executable instructions for performing the steps recited in claim 26.

### Claim 36

A system for managing security of a computing device comprising:
a pre-execution module operable for receiving notice from the computing device's operating system that a program is being loaded onto the computing device;
a validation module coupled to the pre-execution monitor operable for determining whether the program is valid;
a detection module coupled to the pre-execution monitor operable for intercepting a trigger from the computing device's operating system; and
an execution module coupled to the detection module and operable for monitoring the program in response to the trigger intercepted by the detection module.

### Claim 37 (depends on 36)

The system of claim 36, wherein the pre-execution module is further operable for suspending loading of the program onto the computing device.

### Claim 38 (depends on 36)

The system of claim 36, wherein the pre-execution module is further operable for retrieving validation data.

### Claim 39 (depends on 36)

The system of claim 36, wherein the execution module is further operable for deciding whether to terminate the trigger intercepted by the detection module.

### Claim 40 (depends on 36)

The system of claim 36, wherein the execution module is further operable for retrieving authorization data and deciding how to respond to the trigger intercepted by the detection module.
