# US 2019/0245880 A1 · Exception remediation logic rolling platform

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

- Number: US 2019/0245880 A1
- Document ID: US20190245880A1
- Status: Published application
- Kind: A1
- Application number: 15/889,799
- Filed: 2018-02-06
- Published: 2019-08-08
- Earliest claimed: 2018-02-06
- Assignees: Bank of America Corporation
- Applicants: Bank of America Corporation
- Inventors: Julia A. Ward; Jonathan Michael Nauss; Peter Jordan Langsam
- Web page: https://patentgrep.com/patent/US20190245880A1

## CPC

- H04L 63/1433: {Vulnerability analysis}
- H04L 41/0661: {by reconfiguring faulty entities}
- H04L 43/0817: by checking functioning
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The invention relates generally to monitoring and managing network components, such as monitoring the network components to determine the vulnerabilities of network components, implementing remediation plans for the vulnerabilities, instituting remediation suppression for acceptable uses, instituting network component exceptions and rolling exceptions to other network components automatically, and taking consequence actions for the vulnerabilities. A network component exception may be implemented for a network component when the network component data meets custom criteria. When the custom criteria is met, the network component is automatically rolled into the network component exception process to automatically associate network component exceptions with network components that have data that meets the custom criteria. The network component exceptions prevent vulnerability actions from being taken with respect to the associated network components.

## Claims

### Claim 1

A system for rolling network component exceptions to network components, the system comprising:
one or more memories having computer readable code stored thereon; and
one or more processors operatively coupled to the one or more memories, wherein the one or more processors are configured to execute the computer readable code to:
access custom criteria for identifying the network component exceptions;
monitor the network components for network component data;
compare the network component data to the custom criteria in order to determine when the network component data for a network component meets the custom criteria;
automatically operatively coupling network component exception data with the network component when the network component data meets the custom criteria;
prevent a vulnerability action for the network component when the network component is determined have a network component exception; and
monitor the network components or the custom criteria for changes that affect the network components that are operatively coupled to the network component exceptions.

### Claim 2 (depends on 1)

The system of claim 1, wherein the one or more processors are configured to execute the computer readable code to:
receive the custom criteria, wherein the custom criteria is automatically determined based on a logic determination.

### Claim 3 (depends on 1)

The system of claim 1, wherein the one or more processors are configured to execute the computer readable code to:
receive the custom criteria from a user, wherein the custom criteria is defined by the user.

### Claim 4 (depends on 1)

The system of claim 1, wherein monitoring the network components comprises determining changes in the network component that results in a change in the network component exception.

### Claim 5 (depends on 1)

The system of claim 1, wherein monitoring the custom criteria comprises determining changes in the custom criteria that result in a change in the network component exception.

### Claim 6 (depends on 1)

The system of claim 1, wherein automatically operatively coupling the network component exception to the network component comprises storing an indication of the network component exception to a list of the network component exceptions.

### Claim 7 (depends on 1)

The system of claim 1, wherein automatically operatively coupling the network component exception to the network component comprises attaching exception data to the network component indicating that the network component includes the network component exception.

### Claim 8 (depends on 1)

The system of claim 1, wherein preventing the vulnerability action comprises preventing an indication that a vulnerability exists for the network component.

### Claim 9 (depends on 1)

The system of claim 1, wherein preventing the vulnerability action comprises preventing implementation of remediation of a vulnerability for the network component.

### Claim 10 (depends on 1)

The system of claim 1, wherein preventing the vulnerability action comprises preventing reporting of the potential vulnerability.

### Claim 11 (depends on 1)

The system of claim 1, wherein the one or more processors are configured to execute the computer readable code to:
tag an association between the custom criteria with the network components that have the network component exceptions based on the custom criteria; and
compare the custom criteria with the network components when a change in the custom criteria or the network component occurs in order to determine changes in the network component exceptions.

### Claim 12

A computer implemented method for rolling network component exceptions to network components, the method comprising:
accessing, by one or more processors, custom criteria for identifying the network component exceptions;
monitoring, by the one or more processors, the network components for network component data;
comparing, by the one or more processors, the network component data to the custom criteria in order to determine when the network component data for a network component meets the custom criteria;
automatically operatively coupling, by the one or more processors, network component exception data with the network component when the network component data meets the custom criteria;
preventing, by the one or more processors, a vulnerability action for the network component when the network component is determined have a network component exception; and
monitoring, by the one or more processors, the network components or the custom criteria for changes that affect the network components that are operatively coupled to the network component exceptions.

### Claim 13 (depends on 12)

The method of claim 12, wherein the method further comprises:
receiving, by the one or more processors, the custom criteria, wherein the custom criteria is automatically determined based on a logic determination.

### Claim 14 (depends on 12)

The method of claim 12, wherein the method further comprises:
receiving, by the one or more processors, the custom criteria from a user, wherein the custom criteria is defined by the user.

### Claim 15 (depends on 12)

The method of claim 12, wherein monitoring the network components comprises determining changes in the network component that results in a change in the network component exception.

### Claim 16 (depends on 12)

The method of claim 12, wherein monitoring the custom criteria comprises determining changes in the custom criteria that result in a change in the network component exception.

### Claim 17 (depends on 12)

The method of claim 12, wherein automatically operatively coupling the network component exception to the network component comprises storing an indication of the network component exception to a list of the network component exceptions.

### Claim 18 (depends on 12)

The method of claim 12, wherein automatically operatively coupling the network component exception to the network component comprises attaching exception data to the network component indicating that the network component includes the network component exception.

### Claim 19 (depends on 12)

The method of claim 12, wherein the method further comprises:
tagging, by the one or more processors, an association between the custom criteria with the network components that have the network component exceptions based on the custom criteria; and
comparing, by the one or more processors, the custom criteria with the network components when a change in the custom criteria or the network component occurs in order to determine changes in the network component exceptions.

### Claim 20

A computer program product for rolling network component exceptions to network components, the computer program product comprising at least one non-transitory computer-readable medium having computer-readable program code portions embodied therein, the computer-readable program code portions comprising:
an executable portion configured to access custom criteria for identifying the network component exceptions;
an executable portion configured to monitor the network components for network component data;
an executable portion configured to compare the network component data to the custom criteria in order to determine when the network component data for a network component meets the custom criteria;
an executable portion configured to automatically operatively coupling network component exception data with the network component when the network component data meets the custom criteria;
an executable portion configured to prevent a vulnerability action for the network component when the network component is determined have a network component exception; and
an executable portion configured to monitor the network components or the custom criteria for changes that affect the network components that are operatively coupled to the network component exceptions.
