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.

Abstract: Embodiments of the present invention provide a system for exception remediation logic routing and suppression. In particular, the system may identify a vulnerability of a network component as well as additional information like an associated vulnerability category. Next, an original remediation procedure associated with the vulnerability of the network component is identified, including an expected timeframe for completing the original remediation procedure. A determination is then made regarding an expected timeframe for completing the original remediation and how that expected timeframe will not be met in time. A remediation exception procedure is then generated based on the vulnerability, the vulnerability category, the primary user, or a line of business associated with the primary user. This remediation exception procedure comprises an approval to implement the original remediation procedure outside of the expected timeframe, and may include additional restrictions to the network component.

Abstract: Embodiments of the present invention provide a system for network device owner identification and communication triggering. In particular, the system may monitor a plurality of systems of record associated with network of devices and/or individual network components. A primary user for each of these network components is identified, either through a known association in the systems of record or from analysis of records of network traffic associated with each network component. The primary user is recorded for each network component. In the event a vulnerability of a network component is identified, information about the network vulnerability is identified, aggregated with other information about the network component and potential remediation procedures, and compiled as a vulnerability notification. In response to the vulnerability, the system is automatically triggered to transmit the vulnerability notification to the primary user.

Abstract: Embodiments of the present invention provide a system for exception remediation logic routing and suppression. In particular, the system may identify a vulnerability of a network component as well as additional information like an associated vulnerability category. Next, an original remediation procedure associated with the vulnerability of the network component is identified, including an expected timeframe for completing the original remediation procedure. A determination is then made regarding an expected timeframe for completing the original remediation and how that expected timeframe will not be met in time. A remediation exception procedure is then generated based on the vulnerability, the vulnerability category, the primary user, or a line of business associated with the primary user. This remediation exception procedure comprises an approval to implement the original remediation procedure outside of the expected timeframe, and may include additional restrictions to the network component.

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.

Abstract: Embodiments of the present invention provide a system for network device owner identification and communication triggering. In particular, the system may monitor a plurality of systems of record associated with network of devices and/or individual network components. A primary user for each of these network components is identified, either through a known association in the systems of record or from analysis of records of network traffic associated with each network component. The primary user is recorded for each network component. In the event a vulnerability of a network component is identified, information about the network vulnerability is identified, aggregated with other information about the network component and potential remediation procedures, and compiled as a vulnerability notification. In response to the vulnerability, the system is automatically triggered to transmit the vulnerability notification to the primary user.