# US 2020/0351307 A1 · Systems and methods for sharing, distributing, or accessing security data and/or security applications, models, or analytics

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

- Number: US 2020/0351307 A1
- Document ID: US20200351307A1
- Status: Published application
- Kind: A1
- Application number: 16/929,404
- Filed: 2020-07-15
- Published: 2020-11-05
- Earliest claimed: 2017-11-06
- Assignees: Secureworks Corp.
- Applicants: Secureworks Corp.
- Inventors: Timothy Vidas; Jon Ramsey; Aaron Hackworth; Robert Danford; William Urbanski
- Web page: https://patentgrep.com/patent/US20200351307A1

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06F 21/52: during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06N 7/01: Probabilistic graphical models, e.g. probabilistic networks
- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- G06N 3/02: Neural networks
- G06N 20/00: Machine learning
- 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)
- G06N: COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS

## Abstract

Methods and systems for building security applications can be provided. Data policies for accessing security data can be set, and a module pipeline including one or more modules selected from a plurality of modules can be generated. The modules can include at least one module operable to apply a predictive security application or model for detection or identification of security threats. Module execution policies governing execution of the one or more modules in the module pipeline also can be set. Upon receipt of a request to initiate execution of the module pipeline, it can be determined if the execution thereof would violate the data policies or the module execution policies. If so, execution of the module pipeline can be blocked, otherwise the module pipeline can be executed to process the portion of the security data.

## Claims

### Claim 1

A method for building security applications, comprising:
setting data policies for accessing security data based on one or more selected parameters;
generating a module pipeline including selecting one or more modules from a plurality of modules configured to be executed according to a prescribed sequence for accessing and processing of the security data, the plurality of modules including at least one module operable to apply a predictive security application or model to the security data for detection or identification of security threats;
setting module execution policies governing execution of the one or more modules in the module pipeline;
receiving a request to initiate execution of the module pipeline to access and process at least a portion of the security data;
determining if the execution of the module pipeline would violate at least one of the data policies or at least one of the module execution policies, and if so, prohibiting execution of the module pipeline; and
if execution of the module pipeline does not violate at least one of the data polies or module execution policies, initiating execution of the module pipeline to process the accessed portion of the security data.

### Claim 2 (depends on 1)

The method of claim 1, wherein the at least one predictive security application or model includes artificial intelligence, a neural network, machine learning, statistical analysis, probabilistic modeling, named entity recognition, or combinations thereof.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
setting infrastructure policies that determine a time, a location, or resources to be used for execution of the one or more modules in the module pipeline, and
if execution of the module pipeline violates at least one of the infrastructure policies, blocking execution of the module pipeline.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
generating historical metrics that capture previously developed data policies, module policies, and infrastructure policies; and
if execution of the module pipeline conflicts with one or more of the historical metrics, blocking execution of the module pipeline.

### Claim 5 (depends on 1)

The method of claim 1, wherein the plurality of modules further includes one or more modules operable to normalize the portion of the accessed security data, one or more modules operable to take one or more preventative or remedial actions based on detected or identified security threats, and one or more modules for sharing or providing access to at least a portion of the accessed the security data with like actors or sharing partners.

### Claim 6 (depends on 1)

The method of claim 1, further comprising identifying one or more security threats or malicious action based on application of the predictive security application or model.

### Claim 7 (depends on 6)

The method of claim 6, further comprising taking one or more remedial actions upon identification of the one or more security threats or malicious actions.

### Claim 8

A system for building security applications, comprising:
A series of information handling devices or systems, each including:
a memory; and
at least one processor configured to access and execute instructions stored in the one or more memories such that the system is configured to:
set data policies for accessing security data based on one or more selected parameters;
generate a module pipeline including one or more modules selected from a plurality of modules to be executed according to a prescribed sequence for processing of the security data, the plurality of modules including at least one module operable to apply a predictive security application or model for detection or identification of security threats;
set module execution policies governing execution of the one or more modules in the module pipeline;
receive a request to initiate execution of the module pipeline to access and process at least a portion of the security data; and
determine if the execution of the module pipeline would violate at least one of the data policies or at least one of the module execution policies, and if so, prohibit execution of the module pipeline, otherwise execute the module pipeline to process the portion of the security data.

### Claim 9 (depends on 8)

The system of claim 8, wherein the at least one predictive security application or model includes artificial intelligence, a neural network, machine learning, statistical analysis, probabilistic modeling, named entity recognition, or combinations thereof.

### Claim 10 (depends on 8)

The system of claim 8, wherein the system is further configured to set infrastructure policies that determine a time, a location, or resources to be used for execution of the one or more modules in the module pipeline, and if execution of the module pipeline violates at least one of the infrastructure policies, block execution of the module pipeline.

### Claim 11 (depends on 8)

The system of claim 8, wherein the system is further configured to generate historical metrics that capture previously developed data policies, module policies, and infrastructure policies; and if execution of the module pipeline conflicts with one or more of the historical metrics, block execution of the module pipeline.

### Claim 12 (depends on 8)

The system of claim 8, wherein the plurality of modules further includes one or more modules operable to normalize the portion of the security data, one or more modules operable to take one or more preventative or remedial actions based on detected or identified security threats, and one or more modules for providing access to the security data with like actors or sharing partners.

### Claim 13 (depends on 8)

The system of claim 8, wherein the system is further configured to identify one or more security threats or malicious action based on application of the predictive security application or model.

### Claim 14 (depends on 13)

The system of claim 13, wherein the system is further configured to take one or more remedial actions upon identification of the one or more security threats or malicious actions.

### Claim 15

A method, comprising:
collecting security data obtained from monitoring of one or more networks or systems;
setting one or more data access parameters for providing access to, publishing, or sharing of the security data;
providing access to, publishing, or sharing portions of the security data with one or more actors, partners, communities, or managed security service providers based on the one or more data access parameters;
selecting a series of modules for identifying security threats or malicious actions based at least in part on the security data, including at least one module configured to apply one or more predictive security models or applications to the portion of the security data accessed, published or shared for detection or identification of one or more security threats; and at least one module operable to determine a remedial action to be taken to mitigate or eliminate one or more identified or detected security threats;
setting module execution parameters for executing the one or more modules, including one or more parameters for creating, updating and/or modifying the one or more predictive security models or applications; and one or more parameters for determine remedial actions taken for detected or identified security threats; and
executing the one or more modules based on the module execution parameters for identifying of security threats or malicious actions.

### Claim 16 (depends on 15)

The method of claim 15, further comprising generating an alarm or taking an action upon identification of a security threat or malicious action.

### Claim 17 (depends on 15)

The method of claim 15, further comprising generating new or updated security data based on execution of the one or modules or module pipelines.

### Claim 18 (depends on 15)

The method of claim 15, wherein the one or more modules or module pipelines includes at least one probabilistic model.
