SAMMY UI is optimized for resolutions with a width 1024px and higher.
Cloud Controls Matrix
Browse Cloud Controls...
IAM-03: Identity Inventory
Identity Inventory
IAM-03: Is system identity information and levels of access managed, stored, and reviewed?
Organizations should maintain a database of all system identities having access to different cloud environments and assets. The database should illustrate a correlation between digital identities, assets where the access is provisioned, and the type of access being provisioned (i.e., business users, system users, privilege users, etc.). In addition, the database should be regularly reviewed to ensure access is revoked or changed based on job role changes.

The identity and access management database should incorporate single sign-on and multi-factor authentication for user access.
Database access should be based on need-to-know and least-privilege principles and should follow best practices (such as role-based access control and segregation of duties). Finally, all access (especially privileged access) should be logged and monitored for anomalies and unauthorized use and linked to alerting systems as appropriate.
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

Manage, store, and review the information of system identities, and level of access.