SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
LOG-01: Logging and Monitoring Policy and Procedures
Logging and Monitoring Policy and Procedures
LOG-01: Are logging and monitoring policies and procedures established, documented, approved, communicated, applied, evaluated, and maintained?
The policies and procedures should include considerations regarding:
a. The purpose, scope, roles, responsibilities, and coordination among organizational entities and training.
b. How are incidents handled during a security incident?
c. What information should be logged and monitored, and for how long?
d. Who is notified in the event of an incident?

Logging and monitoring policies and procedures should capture the following events:
c. Individual user accesses to systems.
d. Actions taken by any individual with root or administrative privileges.
e. Access to all audit logs should be restricted based on need-to-know and least privilege principles.
f. Invalid access attempts.
g. Changes, additions, or deletions to accounts with root or administrative privileges.
h. Use of and changes to identification and authentication mechanisms, including elevation of privilege.
i. Initializing, stopping, or pausing of the audit logs.
j. Creation and deletion of system-level objects.
Control implemented
Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
Control ownership
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for logging and monitoring. Review and update the policies and procedures at least annually.

Logging and Monitoring Policy and Procedures
LOG-01: Are policies and procedures reviewed and updated at least annually?
The policies and procedures should include considerations regarding:
a. The purpose, scope, roles, responsibilities, and coordination among organizational entities and training.
b. How are incidents handled during a security incident?
c. What information should be logged and monitored, and for how long?
d. Who is notified in the event of an incident?

Logging and monitoring policies and procedures should capture the following events:
c. Individual user accesses to systems.
d. Actions taken by any individual with root or administrative privileges.
e. Access to all audit logs should be restricted based on need-to-know and least privilege principles.
f. Invalid access attempts.
g. Changes, additions, or deletions to accounts with root or administrative privileges.
h. Use of and changes to identification and authentication mechanisms, including elevation of privilege.
i. Initializing, stopping, or pausing of the audit logs.
j. Creation and deletion of system-level objects.
Control implemented
Not applicable - A “N/A” answer indicates that the portion of the control in question is out of scope of the assessment. The “SSRM control ownership” column is to be left blank (e.g., greyed out), and optionally the CSP may explain why it is the case (“CSP Implementation Description”).
No - A “No” answer indicates that the portion of the control in question is not implemented, while in scope of the assessment. The CSP has to assign the implementation responsibility of the control to the relevant party under column “SSRM control ownership”, and optionally elaborate on the “why” (has not been implemented), and “what” has to be done for its implementation by that party.
Yes - A “Yes” answer indicates that the portion of the control in question is implemented. The CSP indicates the responsible and accountable parties (SSRM control ownership), and optionally elaborates on the implementation “how-to” per relevant party CSP and/or CSC.
Control ownership
CSP-owned - The CSP is entirely responsible and accountable for the CCM control implementation.
CSC-owned - The Cloud Service Customer (CSC) is entirely responsible and accountable for the CCM control implementation.
Third-party - The third-party CSP in the supply chain (e.g., an IaaS provider) is responsible for CCM control implementation, while the CSP is fully accountable.
Shared CSP and CSC - Both the CSP and CSC share CCM control implementation responsibility and accountability.
Shared CSP and third party - Any CCM control implementation responsibility is shared between CSP and the third party, but the CSP remains fully accountable.
Description

Establish, document, approve, communicate, apply, evaluate and maintain policies and procedures for logging and monitoring. Review and update the policies and procedures at least annually.