# US 2025/0156526 A1 · Security policies for software call stacks

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

- Number: US 2025/0156526 A1
- Document ID: US20250156526A1
- Status: Published application
- Kind: A1
- Application number: 19/024,341
- Filed: 2025-01-16
- Published: 2025-05-15
- Earliest claimed: 2020-09-16
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Ashutosh Kulshreshtha; Andy Sloane; Hiral Shashikant Patel; Uday Krishnaswamy Chettiar; Oliver Kempe; Bharathwaj Sankara Viswanathan; Navindra Yadav
- Web page: https://patentgrep.com/patent/US20250156526A1

## CPC

- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/54: by adding security routines or objects to programs
- G06F 18/214: Generating training patterns; Bootstrap methods, e.g. bagging or boosting
- G06F 21/51: at application loading time, e.g. accepting, rejecting, starting or inhibiting executable software based on integrity or source reliability
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06N 3/0464: Convolutional networks [CNN, ConvNet]
- G06N 3/084: Backpropagation, e.g. using gradient descent
- G06N 3/09: Supervised learning
- G06N 5/01: Dynamic search techniques; Heuristics; Dynamic trees; Branch-and-bound
- G06N 20/00: Machine learning
- G06N 20/10: using kernel methods, e.g. support vector machines [SVM]
- G06N 20/20: Ensemble learning
- G06N 3/044: Recurrent networks, e.g. Hopfield networks
- G06N 3/045: Combinations of networks
- G06N 3/08: Learning methods
- G06N 7/01: Probabilistic graphical models, e.g. probabilistic networks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

The present disclosure provides systems, methods, and computer-readable media for implementing security polices at software call stack level. In one example, a method includes generating a call stack classification scheme for an application, detecting a call stack during deployment of the application; using the call stack classification scheme during runtime of the application, classifying the detected call stack as one of an authorized call stack or an unauthorized call stack to yield a classification; and applying a security policy based on the classification.

## Claims

### Claim 1

A method comprising:
classifying a call stack as an unauthorized call stack based on a score of the call stack using a classification scheme, wherein the score is assigned during runtime of deployment of an application based in part on a determination that an operating environment of the application is unsecure; and
modifying a security policy based on the classification of the application as unauthorized during the deployment of the application, wherein access to the application is denied during the deployment of the application,
wherein an execution order of the call stack detected during the deployment of the application is a condition for the classification scheme to authorize or unauthorize the application.

### Claim 2 (depends on 1)

The method of claim 1, wherein the classification scheme including a classifier trained using at least one machine learning technique using a list of previously known authorized call stacks and/or a list of previously known unauthorized call stacks to train the classifier.

### Claim 3 (depends on 2)

The method of claim 2, wherein the classifier is configured to identify call stacks as one of an authorized or unauthorized call stacks.

### Claim 4 (depends on 2)

The method of claim 2, wherein the classifier is configured to output the classification of the call stack as one of an authorized call stack or unauthorized call stack.

### Claim 5 (depends on 1)

The method of claim 1, wherein classifying the call stack further comprises:
comparing the score to a threshold; and
classifying the call stack as the unauthorized call stack if the score is less than the threshold.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
tracing call stacks during execution of the application;
determining an execution order of each call stack; and
labelling the application as authorized at least based in part on the execution order of each call stack.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
tracing call stacks during execution of the application;
generating a graph of a percentage of each call stack encountered during the execution of the application; and
labelling the application as unauthorized or authorized based at least in part on the percentage of each call stack encountered during the execution of the application.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
determining a score for the call stack based on execution order;
comparing the score to a threshold score to classify the call stack as authorized or unauthorized; and
based on the call stack being classified as unauthorized, labelling the call stack and the execution order as blacklisted in the classification scheme.

### Claim 9 (depends on 1)

The method of claim 1, wherein the call stack is detected during runtime of the application by Runtime Application Self-Protection (RASP) agents that trace call stack functionality.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
detecting the call stack during the deployment of the application in the operating environment.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
classifying the call stack as an authorized call stack based on a second score of the call stack using the classification scheme being greater than a threshold, wherein the second score is assigned during runtime of a second deployment of the application based in part on a determination that a second operating environment is secure.

### Claim 12 (depends on 11)

The method of claim 11, further comprising:
detecting the call stack during the second deployment of the application in the second operating environment.

### Claim 13

A system comprising:
one or more memories having instruction stored therein; and
one or more processors configured to execute the instructions to:
classify a call stack as an unauthorized call stack based on a score of the call stack using a classification scheme, wherein the score is assigned during runtime of deployment of an application based in part on a determination that an operating environment of the application is unsecure; and
modify a security policy based on the classification of the application as unauthorized during the deployment of the application, wherein access to the application is denied during the deployment of the application,
wherein an execution order of the call stack detected during the deployment of the application is a condition for the classification scheme to authorize or unauthorize the application.

### Claim 14 (depends on 13)

The system of claim 13, wherein the classification scheme including a classifier trained using at least one machine learning technique using a list of previously known authorized call stacks and/or a list of previously known unauthorized call stacks to train the classifier.

### Claim 15 (depends on 14)

The system of claim 14, wherein the classifier is configured to identify call stacks as one of an authorized or unauthorized call stacks.

### Claim 16 (depends on 14)

The system of claim 14, wherein the classifier is configured to output the classification of the call stack as one of an authorized call stack or unauthorized call stack.

### Claim 17 (depends on 13)

The system of claim 13, wherein the one or more processors are configured to execute the instructions to:
compare the score to a threshold; and
classify the call stack as the unauthorized call stack if the score is less than the threshold.

### Claim 18 (depends on 13)

The system of claim 13, wherein the one or more processors are configured to execute the instructions to:
trace call stacks during execution of the application;
determine an execution order of each call stack; and
label the application as authorized within the call stack application scheme based at least in part on the execution order of each call stack.

### Claim 19 (depends on 13)

The system of claim 13, wherein the one or more processors are configured to execute the instructions to:
trace call stacks during execution of the application;
generate a graph of a percentage of each call stack encountered during the execution of the application; and
label the application as unauthorized or authorized based at least in part on the percentage of each call stack encountered during the execution of the application.

### Claim 20 (depends on 13)

The system of claim 13, wherein the one or more processors are configured to execute the instructions to:
determining a score for the call stack based on execution order;
comparing the score to a threshold score to classify the call stack as authorized or unauthorized; and
based on the call stack being classified as unauthorized, labelling the call stack and the execution order as blacklisted in the classification scheme.
