# US 2020/0396244 A1 · Complex Application Attack Quantification, Testing, Detection and Prevention

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

- Number: US 2020/0396244 A1
- Document ID: US20200396244A1
- Status: Published application
- Kind: A1
- Application number: 16/963,105
- Filed: 2019-01-18
- Published: 2020-12-17
- Earliest claimed: 2018-01-18
- Assignees: RiskSense, Inc.
- Applicants: RiskSense, Inc.
- Inventors: Anand Paturi; Srinivas Mukkamala
- Web page: https://patentgrep.com/patent/US20200396244A1

## CPC

- G06Q 10/06: Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06F 16/986: {Document structures and storage, e.g. HTML extensions}
- G06F 21/54: by adding security routines or objects to programs
- G06N 5/022: Knowledge engineering; Knowledge acquisition
- G06N 5/04: Inference or reasoning models
- G06Q 30/018: Certifying business or products
- H04L 63/1416: {Event detection, e.g. attack signature detection}
- H04L 63/1433: {Vulnerability analysis}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/535: {Tracking the activity of the user (network monitoring arrangements H04L43/00; recording of computer activity G06F11/34)}
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06F 18/214: Generating training patterns; Bootstrap methods, e.g. bagging or boosting
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F 2221/033: Test or assess software
- G06F 2221/2101: Auditing as a secondary aspect
- G06N 7/01: Probabilistic graphical models, e.g. probabilistic networks
- G06N 20/00: Machine learning
- G06Q 10/10: Office automation; Time management
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

An apparatus and method for cyber risk quantification calculated from the likelihood of a cyber-attack on the target enterprise and/or cyber ecosystem based on its security posture. The cyber-attack likelihood can be derived as a probability-based time-to-event (TTE) measure using survivor function analysis. The likelihood probability measure can also be passed to cyber risk frameworks to determine financial impacts of the cyber-attacks. Embodiments of the present invention also relate to an apparatus and method (1) to identify and validate application attack surfaces and protect web applications against business logic-based attacks, sensitive data leakage and privilege escalation attacks; and/or (2) that protects web applications against business logic-based attacks, sensitive data leakage and privilege escalation attacks. This can include implementing an intelligent learning loop using artificial intelligence that creates an ontology-based knowledge base from application request and response sequences. Stochastic probabilistic measures are preferably applied to a knowledge base for predicting malicious user actions in real time.

## Claims

### Claim at position 1

1-61. (canceled)

### Claim 62

A method for testing and protecting organizational software web applications against complex web application attacks comprising:
an event capture module communicating with a knowledge base to create comprehensive predicate logic representation for events generated by one or more end users in real time;
the event capture module communicating with a deduction module to allow passing user and application logic identifiers as constants to a process for creating a grounded Markov Logic Network (“MLN”);
a deduction module aiding in the creation of the grounded MLN via its communication with the knowledge base and the event capture module;
passing the grounded MLN to an MLN management module;
the MLN management module receiving input from the deduction model;
the MLN management module creating a master MLN derived from legitimate user actions on a target web application that implements a custom business logic;
the MLN management module dynamically inferring user behavior leading to complex web application attacks; and
an alert module receiving inputs from the MLN management module.

### Claim 63 (depends on 62)

The method of claim 62 wherein the MLN management module performs static and dynamic inference to predict and prevent complex web application attacks.

### Claim 64 (depends on 62)

The method of claim 62 wherein the MLN management module forms a feedback loop to the event capture module to reevaluate a primitive event to enhance learning.

### Claim 65 (depends on 62)

The method of claim 62 wherein the alert module is activated based on attack detection and/or prevention triggers from the MLN management module.

### Claim 66 (depends on 62)

The method of claim 62 wherein the deduction module further comprises an inductive logic programming-based inference engine that creates grounded MLN for the target web application from user actions.

### Claim 67 (depends on 66)

The method of claim 66 wherein the inference engine assigns weights to the predicate statements that represent user actions on the target web application.

### Claim 68 (depends on 67)

The method of claim 67 wherein an analysis engine calculates weights as a maximum likelihood estimator for a probability function.

### Claim 69 (depends on 68)

The method of claim 68 wherein the probability function is based on all state transitions for underlying events applicable to each of a privilege access level.

### Claim 70 (depends on 66)

The method of claim 66 wherein the inference engine accepts weight inputs that originate from subject matter experts.

### Claim 71 (depends on 66)

The method of claim 66 wherein the inference engine creates a grounded MLN for the target web application from end user actions.

### Claim 72 (depends on 66)

The method of claim 66 wherein the inference engine receives unique user identifiers from the knowledge base and event capture module.

### Claim 73 (depends on 72)

The method of claim 72 wherein the unique user identifiers comprise one or more elements selected from a list consisting of session variables, user id, nonce, privilege access level and a combination thereof.

### Claim 74 (depends on 72)

The method of claim 72 wherein the inference engine uses application logic identifiers and user-specific identifiers as constants in the grounded MLN.

### Claim 75 (depends on 74)

The method of claim 74 wherein the grounded MLN is created as a time slice network capturing all user actions on web applications on a temporal scale.

### Claim 76 (depends on 75)

The method of claim 75 wherein the created grounded MLN is a master MLN for a learning mode and wherein the created grounded MLN is a dynamic MLN in a live mode the master MLN generated from all legitimate events performed based on business logic of the target application.

### Claim 77 (depends on 75)

The method of claim 75 further comprising computing summary factors as a transition joint probability function between each of a plurality of temporal level in the temporal scale.

### Claim 78 (depends on 77)

The method of claim 77 wherein the joint probability function within a summary factor at a temporal level represents a consolidated function including all end user attributes and events executed until an immediately prior temporal level.

### Claim 79 (depends on 62)

The method of claim 62 further comprising an inference engine performing static and dynamic inference.

### Claim 80 (depends on 79)

The method of claim 79 wherein the inference engine performs static analysis by accepting security analyst queries and determines if the target web application is susceptible to complex application attacks.

### Claim 81 (depends on 80)

The method of claim 80 wherein the inference engine can determine if the target web application is susceptible to privilege escalation attacks and business-logic attacks.

### Claim 82 (depends on 80)

The method of claim 80 further comprising converting end user queries to respective predicate logic statements and subjecting them to inference in the grounded MLN by using offensive ontology constructs.

### Claim 83 (depends on 62)

The method of claim 62 wherein the MLN management module accepts business logic rules as inputs and further predicts and prevents attacks targeting such rules.

### Claim 84 (depends on 83)

The method of claim 83 wherein predicting and preventing attacks targeting such rules happens in real time or near-real time.

### Claim 85 (depends on 83)

The method of claim 83 wherein the dynamic inference for detecting insecure direct object reference and horizontal privilege access escalation attacks are performed by comparing summary factors between a current and a preceding temporal level.

### Claim 86 (depends on 85)

The method of claim 85 wherein comparing summary factors between a current and a preceding temporal level happens in real time or near-real time.

### Claim 87 (depends on 62)

The method of claim 62 wherein the inference engine performs dynamic inference to detect vertical privilege escalation, insecure direct object reference, horizontal privilege escalation, and other anomalous user behavior by comparing summary factors between a master MLN and a dynamic MLN.

### Claim 88 (depends on 87)

The method of claim 87 wherein comparing summary factors between a master MLN and a dynamic MLN is performed by computing a relative entropy between joint probability distribution functions of the summary factors.

### Claim 89 (depends on 88)

The method of claim 88 wherein an anomalous user behavior alert is generated based on an entropy value generated from summary factor comparison.

### Claim 90 (depends on 89)

The method of claim 89 wherein the anomalous user behavior alert is generated in real time or near-real time.

### Claim 91 (depends on 62)

The method of claim 62 further comprising a command and control center that allows users to activate an attack prevention mode to enable detection of anomalous application user behavior.

### Claim at position 32

92-93. (canceled)

### Claim 94

A non-transitory computer-readable medium comprising computer software for testing and protecting organizational software web applications against complex web application attacks comprising:
code creating an event capture module that communicates with a knowledge base to create comprehensive predicate logic representation for events generated by one or more end users in real time;
code permitting the event capture module to communicate with a deduction module to allow passing user and application logic identifiers as constants to a process for creating a grounded Markov Logic Network (“MLN”);
code creating a deduction module that aids in the creation of the grounded MLN via its communication with the knowledge base and the event capture module;
code passing the grounded MLN to an MLN management module and which causes the MLN management module to receive input from the deduction model;
code causing the MLN management module to create a master MLN derived from legitimate user actions on a target web application that implements a custom business logic;
code causing the MLN management module to dynamically inferring user behavior leading to complex application attacks; and
code causing an alert module to receive inputs from the MLN management module.
