# US 2013/0276108 A1 · Flow data for security data loss prevention

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

- Number: US 2013/0276108 A1
- Document ID: US20130276108A1
- Status: Published application
- Kind: A1
- Application number: 13/444,774
- Filed: 2012-04-11
- Published: 2013-10-17
- Earliest claimed: 2012-04-11
- Assignees: CA, Inc.
- Inventors: Aaron Kenneth Blackwell
- Web page: https://patentgrep.com/patent/US20130276108A1

## CPC

- G06F 21/554: {involving event detection and direct action}
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

There are techniques for detecting and preventing possible security violations in a computer network. The security violation detection may be based on data attached to transactions as they flow through one or more software applications. A transaction that is processed by a sequence of software components that execute on one or more electronic devices may be traced. Data that is associated with the transaction as the transaction flows through the sequence of software components may be accessed. The accessed data may be analyzed to detect a possible security violation. The accessed data may be compared to one or more pre-defined patterns. The transaction may be intercepted upon detection of a possible security violation.

## Claims

### Claim 1

A method comprising:
tracing a transaction that is processed by a sequence of software components that execute on an electronic device, the tracing is performed by a circuit on the electronic device;
accessing data that is associated with the transaction as the transaction flows through the sequence of software components, the accessing is performed by a circuit on the electronic device; and
analyzing the data associated with the transaction to detect a possible security violation.

### Claim 2 (depends on 1)

The method of claim 1, wherein the accessing data that is associated with the transaction comprises:
accessing data at multiple points along the flow of the transaction.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
combining the data from the multiple points along the flow, wherein the analyzing of the data to detect a possible security violation comprises analyzing the data from the multiple points along the flow.

### Claim 4 (depends on 1)

The method of claim 1, wherein the accessing data that is associated with the transaction comprises:
accessing data that is passed from one of the software components to another of the software components.

### Claim 5 (depends on 1)

The method of claim 1, wherein the accessing data that is associated with the transaction comprises:
accessing data that is processed internally by one of the software components.

### Claim 6 (depends on 1)

The method of claim 1, wherein the analyzing the accessed data to detect a possible security violation comprises comparing the accessed data to a pre-defined pattern to detect a possible security violation.

### Claim 7 (depends on 1)

The method of claim 1, wherein the transaction is a particular type of transaction, the analyzing the accessed data to detect a possible security violation comprises comparing the data to pre-defined data patterns for that type of transaction.

### Claim 8 (depends on 1)

The method of claim 1, further comprising:
halting the transaction in response to determining that there is a possible security violation.

### Claim 9 (depends on 1)

The method of claim 1, wherein the accessing data that is associated with the transaction as the transaction flows through the sequence of software components is performed by monitoring software residing on the electronic device, the monitoring software monitors performance of the software components.

### Claim 10

A system comprising:
a processor programmed to:
access data attached to transactions as the transactions flow through a software application; and
compare the data attached to each of the transactions to pre-defined patterns to detect possible security violations.

### Claim 11 (depends on 10)

The system of claim 10, wherein the processor programmed to access data that is attached to the transactions as the transactions flow comprises the processor programmed to:
access data at multiple points along the flow of a first of the transactions.

### Claim 12 (depends on 11)

The system of claim 11, wherein the processor is further programmed to:
combine the data from the multiple points along the flow of the first transaction, wherein the processor compares the combined data with one or more pre-defined patterns to detect a possible security violation.

### Claim 13 (depends on 10)

The system of claim 10, wherein the software application comprises a plurality of software components, the processor programmed to access data attached to the transactions as the transactions flow comprises the processor programmed to:
access data that is passed from a first of the software components to a second of the software components.

### Claim 14 (depends on 10)

The system of claim 10, wherein the software application comprises a plurality of software components, the processor programmed to access data attached to the transactions as the transactions flow comprises the processor programmed to:
access data that is processed internally by the plurality of software components.

### Claim 15 (depends on 10)

The system of claim 10, wherein the transaction is a particular type of transaction, the processor programmed to compare the data to pre-defined patterns to detect a possible security violation comprises the processor programmed to compare the data to pre-defined data patterns for that type of transaction.

### Claim 16 (depends on 10)

The system of claim 10, wherein the processor is further programmed to:
halt a first of the transactions in response to determining that there is a possible security violation.

### Claim 17

A method comprising:
determining a sequence of software components that process a transaction being processed by the software components that execute on an electronic device, the determining is performed by a circuit on the electronic device;
accessing data that is attached to the transaction as the transaction flows through the sequence of software components, the accessing is performed by a circuit on the electronic device; and
comparing the data that is attached to the transaction with a pre-defined pattern to determine whether a security violation may have occurred.

### Claim 18 (depends on 17)

The method of claim 17, wherein the accessing data that is attached to the transaction as the transaction flows comprises:
accessing data at multiple points along the flow of the transaction.

### Claim 19 (depends on 18)

The method of claim 18, further comprising:
combining the data from the multiple points along the flow, wherein the comparing the data to the pre-defined pattern compares the combined data with the pre-defined pattern.

### Claim 20 (depends on 17)

The method of claim 17, wherein the accessing data that is attached to the transaction as the transaction flows comprises:
accessing data that is passed from or received by a first of the software components.

### Claim 21 (depends on 17)

The method of claim 17, wherein the accessing data that is attached to the transaction as the transaction flows comprises:
accessing data that is processed internally by a first of the software components.

### Claim 22 (depends on 17)

The method of claim 17, wherein the transaction is a particular type of transaction, the comparing the data with the pre-defined pattern comprises comparing the data to a pre-defined data pattern for that type of transaction.

### Claim 23 (depends on 17)

The method of claim 17, further comprising:
halting the transaction in response to determining that a security violation may have occurred.

### Claim 24

A computer program product comprising:
a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to trace a transaction that is processed by a sequence of software components that execute on an electronic device;
computer readable program code configured to access data that is associated with the transaction as the transaction flows through the sequence of software components; and
computer readable program code configured to analyze the data associated with the transaction to detect a possible security violation.
