# US 2019/0245879 A1 · Vulnerability consequence triggering system for application freeze and removal

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

- Number: US 2019/0245879 A1
- Document ID: US20190245879A1
- Status: Published application
- Kind: A1
- Application number: 15/889,797
- 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; Jessica Kay Aleshire; MacKenzie Smith Durnovich
- Web page: https://patentgrep.com/patent/US20190245879A1

## CPC

- H04L 63/1433: {Vulnerability analysis}
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/1441: {Countermeasures against malicious traffic (countermeasures against attacks on cryptographic mechanisms H04L9/002)}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- 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 the network components, implementing remediation plans for the vulnerabilities, instituting remediation exceptions for the vulnerabilities, and taking consequence actions for the vulnerabilities. When implementing the remediation plan, at least a portion of the network component may be frozen such that a user cannot operate at least a portion of the network component until the vulnerability is remediated. After implementing the remediation plan, monitoring of the network components and the remediation plan continues in order to identify triggers. If a trigger is identified, the consequence action may be implemented, which may prevent operation of the network components by disconnecting or blocking them from the network, uninstalling the network component, deactivating or powering down the network component.

## Claims

### Claim 1

A system for triggering consequence actions for network component vulnerabilities, 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:
monitor network components for vulnerabilities;
identify a vulnerability, wherein the vulnerability is related to at least one network component of the network components;
identify a remediation plan for the vulnerability for the at least one network component;
implement the remediation plan for the at least network component;
monitor the at least one network component for compliance with the remediation plan;
identify a trigger for implementing a consequence action for the at least one network component; and
implement the consequence action for the at least one network component when the trigger is identified.

### Claim 2 (depends on 1)

The system of claim 1, wherein the consequence action for the at least one network component comprises preventing operation of at least a portion of the at least one network component until the remediation plan is implemented, wherein preventing the operation of at least the portion of the at least one network component comprises remotely accessing and controlling the at least one network component.

### Claim 3 (depends on 1)

The system of claim 1, wherein the consequence action for the at least one network component comprises removal of the at least one network component from a network.

### Claim 4 (depends on 3)

The system of claim 3, wherein the removal of the at least one network component comprises remotely disconnecting the at least one network component from the network.

### Claim 5 (depends on 3)

The system of claim 3, wherein the removal of the at least one network component comprises blocking a connection of the at least one network component to the network.

### Claim 6 (depends on 3)

The system of claim 3, wherein the removal of the at least one network component comprises uninstalling the at least one network component.

### Claim 7 (depends on 3)

The system of claim 3, wherein the removal of the at least one network component comprises deactivating operation of the at least one network component.

### Claim 8 (depends on 3)

The system of claim 3, wherein the removal of the at least one network component comprises remotely powering down the at least one network component.

### Claim 9 (depends on 1)

The system of claim 1, wherein the trigger comprises a primary user of the network component failing to respond to an alert regarding the remediation plan.

### Claim 10 (depends on 1)

The system of claim 1, wherein the trigger comprises a failure to implement the remediation plan.

### Claim 11 (depends on 1)

The system of claim 1, wherein the trigger comprises a failure to complete the remediation plan by a remediation deadline.

### Claim 12 (depends on 1)

The system of claim 1, wherein the remediation plan comprises alerting at least a primary user of a remediation process, providing network component updates to remediate the vulnerability, and preventing operation of at least a portion of the at least one network component until the remediation plan is implemented.

### Claim 13 (depends on 1)

The system of claim 1, wherein the one or more processors are configured to execute the computer readable code to:
classify the vulnerabilities for the network components based on priority of the vulnerabilities, the network components exposed to the vulnerabilities, and primary users associated with the vulnerabilities;
generate remediation plans for the vulnerabilities;
generate the consequence actions for the vulnerabilities; and
generate triggers for implementing the consequence actions.

### Claim 14 (depends on 13)

The system of claim 13, wherein the vulnerabilities are classified based on priority of remediation for the vulnerabilities.

### Claim 15 (depends on 14)

The system of claim 14, wherein the priority of remediation for the vulnerabilities are determined based on a scope of the vulnerability, the network components affected by the vulnerability, connection of the network components to other network components, or the primary users of the network components.

### Claim 16 (depends on 1)

The system of claim 1, wherein the network component comprises a network device or a network application.

### Claim 17

A computer implemented method for triggering consequence actions for network component vulnerabilities, the method comprising:
monitoring, by one or more processors, network components for vulnerabilities;
identifying, by the one or more processors, a vulnerability, wherein the vulnerability is related to at least one network component of the network components;
identifying, by the one or more processors, a remediation plan for the vulnerability for the at least one network component;
implementing, by the one or more processors, the remediation plan for the at least network component;
monitoring, by the one or more processors, the at least one network component for compliance with the remediation plan;
identifying, by the one or more processors, a trigger for implementing a consequence action for the at least one network component; and
implementing, by the one or more processors, the consequence action for the at least one network component when the trigger is identified.

### Claim 18 (depends on 17)

The method of claim 17, wherein the consequence action for the at least one network component comprises removal of the at least one network component from a network, wherein the removal comprises remotely disconnecting the at least one network component from the network, blocking a connection of the at least one network component to the network, uninstalling the at least one network component, deactivating operation of the at least one network component, or remotely powering down the at least one network component.

### Claim 19 (depends on 17)

The method of claim 17, wherein the trigger comprises a primary user of the network component failing to respond to an alert regarding the remediation plan, a failure of implementation of the remediation plan, or a failure to complete the remediation plan by a remediation deadline.

### Claim 20

A computer program product for triggering consequence actions for network component vulnerabilities, 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 monitor network components for vulnerabilities;
an executable portion configured to identify a vulnerability, wherein the vulnerability is related to at least one network component of the network components;
an executable portion configured to identify a remediation plan for the vulnerability for the at least one network component;
an executable portion configured to implement the remediation plan for the at least network component;
an executable portion configured to monitor the at least one network component for compliance with the remediation plan;
an executable portion configured to identify a trigger for implementing a consequence action for the at least one network component; and
an executable portion configured to implement the consequence action for the at least one network component when the trigger is identified.
