# US 2017/0286688 A1 · Precision-tuned runtime monitoring

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

- Number: US 2017/0286688 A1
- Document ID: US20170286688A1
- Status: Published application
- Kind: A1
- Application number: 15/083,330
- Filed: 2016-03-29
- Published: 2017-10-05
- Earliest claimed: 2016-03-29
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Paul Ionescu; Iosif V. Onut; Omer Tripp
- Web page: https://patentgrep.com/patent/US20170286688A1

## CPC

- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- 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 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Preliminary program analysis of an executable may be performed. A security vulnerability level of a portion of the executable may be determined based on the preliminary program analysis. The security vulnerability level of the portion may be compared to a security vulnerability threshold. The precision of runtime monitoring of the portion may be tuned based on the comparison.

## Claims

### Claim 1

A method comprising:
performing, by a processor, preliminary program analysis of an executable;
determining, by the processor and based on the preliminary program analysis, a security vulnerability level of a portion of the executable;
comparing, by the processor, the security vulnerability level of the portion to a security vulnerability threshold; and
tuning, by the processor, the precision of runtime monitoring of the portion based the comparing.

### Claim 2 (depends on 1)

The method of claim 1, wherein the comparing comprises determining that the security vulnerability level of the portion is higher than the security vulnerability threshold, and the tuning comprises configuring the runtime system to monitor the portion with a high level of precision based on the comparing.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
determining, by the processor and based on the preliminary program analysis, a second security vulnerability level of a second portion of the executable;
comparing, by the processor, the second security vulnerability level of the second portion to the security vulnerability threshold;
determining that the second security vulnerability level of the second portion is lower than the security vulnerability threshold; and
tuning, by the processor and based on determining that the second security vulnerability level of the second portion is lower than the security vulnerability threshold, the precision of runtime-monitoring of the second portion with a low level of precision.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining, by the processor and based on the comparing, that the security vulnerability level of the portion is lower than the security vulnerability threshold;
comparing, by the processor, the security vulnerability level of the portion to a second vulnerability threshold, wherein the second vulnerability threshold is lower than the first vulnerability threshold;
determining, by the processor, based on the comparing the security vulnerability level of the portion to the second vulnerability threshold, that the security vulnerability level of the portion is above the second vulnerability threshold; and
configuring, by the processor and the tuning, the runtime system to monitor the portion with an intermediate level of precision based on the determining that the security vulnerability of the portion is higher than the second security vulnerability threshold.

### Claim 5 (depends on 1)

The method of claim 1, wherein the preliminary program analysis is a form of static analysis.

### Claim 6 (depends on 5)

The method of claim 5, wherein the static analysis is shape analysis.

### Claim 7 (depends on 6)

The method of claim 6, wherein the shape analysis is restricted to execution prefixes of the executable.

### Claim 8 (depends on 1)

The method of claim 1, wherein the preliminary program analysis is a form of offline testing.

### Claim 9 (depends on 1)

The method of claim 1, wherein the preliminary program analysis is a form of runtime monitoring.

### Claim 10 (depends on 9)

The method of claim 9, wherein the runtime monitoring has been tuned in a previous runtime monitoring tuning process.

### Claim 11 (depends on 1)

The method of claim 1, wherein the preliminary program analysis is taint analysis.

### Claim 12 (depends on 11)

The method of claim 11, wherein taint analysis is restricted to non-immutable variables.

### Claim 13 (depends on 1)

The method of claim 1, wherein the portion is an execution prefix and wherein the comparing comprises determining an execution prefix length limit beyond which the security vulnerability level of the portion falls below the security vulnerability threshold.

### Claim 14 (depends on 1)

The method of claim 1, wherein the tuning occurs when the executable is executed.

### Claim 15 (depends on 1)

The method of claim 1, wherein the tuning is performed when the executable is integrated into a computer system.

### Claim 16 (depends on 1)

The method of claim 1, wherein the tuning is performed on a periodic basis.

### Claim 17

A system comprising a processor configured to perform a method comprising:
performing, by the processor, shape analysis of an executable, wherein the shape analysis is restricted to analyzing execution prefixes of the executable;
determining, by the processor and based on the preliminary program analysis, an execution-prefix length limit, wherein any execution prefixes with a length higher than the execution-prefix length limit are likely to exhibit a security vulnerability level below a security vulnerability threshold;
storing, by the processor, the execution-prefix length limit in an oracle;
accessing, by the processor, the oracle; and
tuning, by the processor, runtime-monitoring of the executable to monitor prefixes with a prefix length lower than the prefix length limit with high precision and to monitor prefixes with a prefix length lower than the prefix length limit with low precision.

### Claim 18

A computer program product, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a computer to cause the computer to:
compute, in a first phase and in response to receiving an input comprising a code portion representing a program P having execution prefixes and further comprising an identification of a prefix length bound by n, a control flow graph G of the program P;
apply a breadth first search traversal over the control flow graph G up to the limit of n to create a set S of finite execution prefixes of length less or equal to n;
apply a shape analysis selected from a set of predefined analyses, over each of one or more path prefixes in the set S to determine a respective security status, wherein the selected shape analysis is applied over only the execution prefixes of the program P;
record each mapping from an execution prefix to a respective security status as an Oracle O;
in a second phase at runtime, apply the Oracle O, in an online enforcement algorithm utilizing information computed by the selected shape analysis to precisely monitor for security concerns along a given execution prefix in the set S of finite execution prefixes as the finite execution prefixes unfold, wherein all execution prefixes are enumerated and accounted for, and full coverage up to the limit of n is obtained; and
perform conservative monitoring of the program P at runtime beyond a prefix of length n, by the oracle.
