What evidence do auditors commonly ask for on IAM-03 Identity Inventory?

Identity inventory export from the identity provider covering human, service and machine identities; Documented storage location and protection of the identity store; Periodic inventory review records with orphaned or stale identities removed; Monitoring report or dashboard of access levels and privilege changes.

What is the most common gap auditors find on IAM-03?

Service and machine identities missing from the inventory

CSA CCM v4.1 · IAM - Identity & Access Management

`IAM-03` Identity Inventory

Hold an inventory of identities, keep it securely, review it on a regular cycle and watch the level of access each identity holds.

Source: CSA CCM v4.1, IAM-03. The statement above is our statement of the clause, read from the published text and cited so you can check it against the official text, not the instrument verbatim. Open CSA CCM v4.1 in the compliance library.

Version 4.1 adds 11 controls (among them API security, log sanitisation and a service bill of materials) and renumbers several domains. CSA accepts v4.0.x during its transition; if your STAR assessment is still on v4.0.1, check the numbering against it.

artefacts

held by a system

at each review

easy

to go live

Policy repository / GRC workspace

where the evidence lives

teal = a system already holds it · olive = produced at each review. To go live: easy when half or more of the artefacts are already held by a system, moderate from a quarter to a half, hard below a quarter.

These are the artefacts auditors commonly ask for on this requirement, our guidance rather than text from the standard. Your assessor decides what is sufficient in your context, and asks for samples across the period when a report covers one.

system holds itEvidence a system already holds

Identity inventory export from the identity provider covering human, service and machine identities · Policy repository / GRC workspace
Monitoring report or dashboard of access levels and privilege changes · SIEM / log platform

periodic reviewEvidence produced at each review

Periodic inventory review records with orphaned or stale identities removed · Policy repository / GRC workspace

governing documentDocuments that govern the control

Documented storage location and protection of the identity store · Document repository

First move

Automate the pull from your Policy repository / GRC workspace. Version-controlled policy set with approval metadata; review dates tracked as records, not a calendar note.

Common gaps auditors find

Service and machine identities missing from the inventory
Inventory reviewed rarely, leaving dormant accounts
No monitoring of privilege creep between reviews

Do this for your whole sheet

Paste the rows you run your controls from and get this mapping for every control at once, with the periodic-review ones flagged and a first move per row. No account for the first run.

Build my evidence sheet

IAM-02 Credentials Management Policy and Procedures · IAM-04 Separation of Duties