SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
LOG-12: Access Control Logs
Access Control Logs
LOG-12: Is physical access logged and monitored using an auditable access control system?
The organization should monitor and log all physical access via the following means:
a. Verifying physical access of individuals when they enter secure areas.
b. Maintaining physical access logs for the facilities
c. Escorting visitors at all times.
d. Reviewing access control logs regularly.

The organization should use either video cameras or access control mechanisms (or both) to monitor individual physical access to sensitive areas. Review collected data, correlate with other entries, and store the data for at least three months (unless otherwise restricted by law.)

The organization should implement physical and/or logical controls to restrict access to publicly accessible network jacks. For example, limit physical access to wireless access points, gateways, handheld devices, networking/communications hardware, and telecommunication lines.

The organization should develop procedures to distinguish between onsite personnel and visitors with an emphasis on the following considerations:
e. Identifying onsite personnel and visitors (for example, assigning badges)
f. Changing access requirements
g. Revoking or terminating onsite personnel and expired visitor identification

The organization should develop procedures to control physical access for onsite personnel to sensitive areas as follows:
h. Access should be authorized and based on individual job functions.
i. Access should be revoked immediately upon termination. Furthermore, all physical access mechanisms, such as keys, access cards, etc., must be returned or disabled.
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

Monitor and log physical access using an auditable access control system.