# US 2021/0281597 A1 · Tailored security configuration of least-privilege applications

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

- Number: US 2021/0281597 A1
- Document ID: US20210281597A1
- Status: Published application
- Kind: A1
- Application number: 16/809,928
- Filed: 2020-03-05
- Published: 2021-09-09
- Earliest claimed: 2020-03-05
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: Hugo Guiroux; Christopher Ferreira; Matthias Neugschwandtner; Roxana Bradescu
- Web page: https://patentgrep.com/patent/US20210281597A1

## CPC

- H04L 63/105: {Multiple levels of security}
- H04L 63/1433: {Vulnerability analysis}
- G06F 21/54: by adding security routines or objects to programs
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 21/629: {to features or functions of an application}
- H04L 63/166: {at the transport layer}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 69/16: Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
- G06F 2221/2113: Multi-level security, e.g. mandatory access control
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques for tailoring security configurations for least-privilege applications are provided. In one technique, multiple software artifacts associated with a software application are identified. For each software artifact, a call graph is generated, the call graph is added to a set of call graphs, and a set of dependencies for the software artifact is detected. The set of call graphs are combined to generate a merged call graph. One or more portions of the merged call graph are pruned to generate a pruned call graph. Annotation data is stored that associates elements in the pruned call graph with the set of dependencies for each software artifact. Based on the annotation data, reachable dependencies are identified. Based on the reachable dependencies, a set of security policies is generated for the software application.

## Claims

### Claim 1

A method comprising:
identifying a plurality of software artifacts associated with a software application;
for each software artifact of the plurality of software artifacts:
generating a call graph for said each software artifact;
adding the call graph to a set of call graphs;
detecting a set of one or more dependencies for said each software artifact;
combining the set of call graphs to generate a merged call graph;
pruning one or more portions of the merged call graph to generate a pruned call graph;
storing annotation data that associates elements in the pruned call graph with the set of one or more dependencies for each software artifact of the plurality of software artifacts;
based on the annotation data, identifying a set of reachable dependencies;
based on the set of reachable dependencies, generating a set of one or more security policies for the software application;
wherein the method is performed by one or more computing devices.

### Claim 2 (depends on 1)

The method of claim 1, wherein the plurality of software artifacts include the software application and one or more libraries that the software application calls.

### Claim 3 (depends on 1)

The method of claim 1, wherein the plurality of software artifacts comprise two or more of bytecode, assembly code, or source code.

### Claim 4 (depends on 1)

The method of claim 1, wherein a plurality of types of dependencies reflected in the set of one or more dependencies for each software artifact of the plurality of software artifacts includes a system call, a TCP stack, a UDP stack, and a library call.

### Claim 5 (depends on 1)

The method of claim 1, wherein a particular software artifact in the plurality of software artifacts comprises one or more entry points to the particular software artifact, one or more internal functions, and one or more function references to one or more other software artifacts.

### Claim 6 (depends on 1)

The method of claim 1, wherein combining the set of call graphs comprises:
for each software artifact in a subset of the plurality of software artifacts:
identifying one or more function references of said each software artifact;
for each function reference of the one or more function references:
identifying an entry point, in another software artifact of the plurality of software artifacts, to which said each function reference points;
creating an association, in the merged call graph, between the said each function reference and the entry point.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
identifying one or more entry points for the software application;
for each entry point of the one or more entry points:
determining whether said each entry point is reachable;
storing first data that indicates that said entry point is reachable if it is determined that said each entry point is reachable;
if it is determined that said each entry point is reachable, then:
identifying a set of one or more nodes that are downstream of said each entry point;
storing second data that indicates that said node in the set of one or more nodes is reachable;
wherein pruning one or more portions of the merged call graph comprises identifying one or more paths through the merged call graph, wherein, for each path in the one or more paths, no node in said each path is associated with data that indicates that the node is reachable.

### Claim 8 (depends on 1)

The method of claim 1, wherein:
the set of one or more security policies includes a plurality of security policies that includes a first security policy for a first security mechanism and a second security policy for a second security mechanism that is different than the first security mechanism,
generating the set of one or more security policies for the software application comprises:
for each reachable dependency in the list of reachable dependencies:
determining a type of said each reachable dependency;
adding said each reachable dependency to a security policy, in the plurality of security policies, that is associated with the type.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
storing the set of one or more security policies in a software container that comprises a plurality of software applications.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
identifying one or more software artifacts, of the plurality of software artifacts, that are not invokable during execution of the software application;
storing, in the container, the plurality of software artifacts except for the one or more software artifacts.

### Claim 11

One or more non-transitory storage media storing instructions which, when executed by one or more computing devices, cause:
identifying a plurality of software artifacts associated with a software application;
for each software artifact of the plurality of software artifacts:
generating a call graph for said each software artifact;
adding the call graph to a set of call graphs;
detecting a set of one or more dependencies for said each software artifact;
combining the set of call graphs to generate a merged call graph;
pruning one or more portions of the merged call graph to generate a pruned call graph;
storing annotation data that associates elements in the pruned call graph with the set of one or more dependencies for each software artifact of the plurality of software artifacts;
based on the annotation data, identifying a set of reachable dependencies;
based on the set of reachable dependencies, generating a set of one or more security policies for the software application.

### Claim 12 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein the plurality of software artifacts include the software application and one or more libraries that the software application calls.

### Claim 13 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein the plurality of software artifacts comprise two or more of bytecode, assembly code, or source code.

### Claim 14 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein a plurality of types of dependencies reflected in the set of one or more dependencies for each software artifact of the plurality of software artifacts includes a system call, a TCP stack, a UDP stack, and a library call.

### Claim 15 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein a particular software artifact in the plurality of software artifacts comprises one or more entry points to the particular software artifact, one or more internal functions, and one or more function references to one or more other software artifacts.

### Claim 16 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein combining the set of call graphs comprises:
for each software artifact in a subset of the plurality of software artifacts:
identifying one or more function references of said each software artifact;
for each function reference of the one or more function references:
identifying an entry point, in another software artifact of the plurality of software artifacts, to which said each function reference points;
creating an association, in the merged call graph, between the said each function reference and the entry point.

### Claim 17 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein the instructions, when executed by the one or more processors, further cause:
identifying one or more entry points for the software application;
for each entry point of the one or more entry points:
determining whether said each entry point is reachable;
storing first data that indicates that said entry point is reachable if it is determined that said each entry point is reachable;
if it is determined that said each entry point is reachable, then:
identifying a set of one or more nodes that are downstream of said each entry point;
storing second data that indicates that said node in the set of one or more nodes is reachable;
wherein pruning one or more portions of the merged call graph comprises identifying one or more paths through the merged call graph, wherein, for each path in the one or more paths, no node in said each path is associated with data that indicates that the node is reachable.

### Claim 18 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein:
the set of one or more security policies includes a plurality of security policies that includes a first security policy for a first security mechanism and a second security policy for a second security mechanism that is different than the first security mechanism,
generating the set of one or more security policies for the software application comprises:
for each reachable dependency in the list of reachable dependencies:
determining a type of said each reachable dependency;
adding said each reachable dependency to a security policy, in the plurality of security policies, that is associated with the type.

### Claim 19 (depends on 11)

The one or more non-transitory storage media of claim 11, wherein the instructions, when executed by the one or more processors, further cause:
storing the set of one or more security policies in a software container that comprises a plurality of software applications.

### Claim 20 (depends on 19)

The one or more non-transitory storage media of claim 19, wherein the instructions, when executed by the one or more processors, further cause:
identifying one or more software artifacts, of the plurality of software artifacts, that are not invokable during execution of the software application;
storing, in the container, the plurality of software artifacts except for the one or more software artifacts.
