Michael William Nix

US Patent:

20170244559, Aug 24, 2017

Filed:

Feb 28, 2017

Appl. No.:

15/445087

Inventors:

- Armonk NY, US
Jai Singh Arun - Morrisville NC, US
MIchael Delaine Nix - Lake Kiowa TX, US
Krishna Kishore Yellepeddy - Austin TX, US

International Classification:

H04L 9/08

Abstract:

A security management system comprises a key management sub-system, an asset/workload management sub-system, and an event management sub-system. The event management sub-system detects events. The asset/workload management sub-system correlates events (irrespective of type) with the assets that generate them, and the key management sub-system uses the event-asset associations determined by the asset/workload management sub-system to automatically orchestrate the necessary key management activities (e.g., key creation, revocation, refresh, etc.) across the impacted components in the information technology and operational realms to ensure data security. In one use case, a security event detected by the event management sub-system triggers one or more actions within the asset/workload management sub-system. Service configuration records are identified from this scan, and assets defined in those records are identified. An event-asset association is then supplied to the key management sub-system, which uses this information to determine a key management operation.

US Patent:

20150055780, Feb 26, 2015

Filed:

Aug 21, 2013

Appl. No.:

13/972682

Inventors:

- Armonk NY, US
Jai Singh Arun - Morrisville NC, US
MIchael Delaine Nix - Lake Kiowa TX, US
Krishna Kishore Yellepeddy - Austin TX, US

Assignee:

International Business Machines Corporation - Armonk NY

International Classification:

H04L 9/08

US Classification:

380277

Abstract:

A security management system comprises a key management sub-system, an asset/workload management sub-system, and an event management sub-system. The event management sub-system detects events. The asset/workload management sub-system correlates events (irrespective of type) with the assets that generate them, and the key management sub-system uses the event-asset associations determined by the asset/workload management sub-system to automatically orchestrate the necessary key management activities (e.g., key creation, revocation, refresh, etc.) across the impacted components in the information technology and operational realms to ensure data security. In one use case, a security event detected by the event management sub-system triggers one or more actions within the asset/workload management sub-system. Service configuration records are identified from this scan, and assets defined in those records are identified. An event-asset association is then supplied to the key management sub-system, which uses this information to determine a key management operation.