Architectural patterns for incident management include services for trouble ticketing and incident classification. Incident Management interacts with other areas of the architecture either directly (as with the service desk), indirectly (through manipulation of common data) or asynchronously (as part of a business process for incident management). Incidents begin their lives either as a phone in incident from a human, a detected error in the environment (usually as a result of event correlation from the Systems Management domain) or via incident messaging from another application.
Cloud Controls Matrix (CCM) Data
Physical | Network | Compute | App | Data |
---|---|---|---|---|
True | True | True | True | True |
Corp Gov Relevance |
---|
True |
SaaS | PaaS | IaaS |
---|---|---|
True | True | True |
Service Provider | Tenant / Consumer |
---|---|
True | True |
COBIT 4.1 | HIPAA / HITECH Act | ISO/IEC 27001-2005 |
---|---|---|
DS5.6 | 45 CFR 164.308 (a)(1)(i) | Clause 4.3.3 |
NIST SP800-53 R3 | FedRAMP (Final 2012) Low Impact | FedRAMP (Final 2012) Moderate Impact | PCI DSS v2.0 |
---|---|---|---|
IR-1 | NIST SP 800-53 R3 IR-1 | NIST SP 800-53 R3 IR-1 | 12.9 |
BITS Shared Assessments SIG v6.0 | BITS Shared Assessments SIG v5.0 | GAPP (Aug 2009) |
---|---|---|
J.1.1, J.1.2 | J.1 | 1.2.4 |
Jericho Forum | NERC CIP |
---|---|
Commandment #2 | CIP-007-3 - R6.1 |
Consensus Assessments Initiative Questionnaire (CAIQ) Data
COBIT | HIPAA | ISO27001 | SP800_53 |
---|---|---|---|
COBIT 4.1 DS5.6 | 45 CFR 164.308 (a)(1)(i) | Clause 4.3.3 | NIST SP800-53 R3 IR-1 |
FedRAMP | PCI_DSS | BITS | GAPP |
---|---|---|---|
NIST SP800-53 R3 IR-1 | PCI-DSS v2.0 12.9 | AUP v5.0 J.1 SIG v6.0: J.1.1, J.1.2 | GAPP Ref 1.2.4 |
SaaS | PaaS | IaaS |
---|---|---|
True | True | True |
SP | CUST |
---|---|
True | True |