What evidence do auditors commonly ask for on IAM-07 Access Changes and Revocation?

Defined timeframes for access removal on termination and for changes on role moves; Leaver and mover samples comparing HR effective date with account disable or change date; Automated deprovisioning configuration from the HR system to the identity provider; Exception reports for accounts still active after the leaver date.

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

No defined timeframe, so timeliness cannot be tested

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

`IAM-07` Access Changes and Revocation

Remove or adjust an identity's access promptly when it is no longer appropriate.

Source: CSA CCM v4.1, IAM-07. 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

moderate

to go live

Identity provider / directory

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

Automated deprovisioning configuration from the HR system to the identity provider · Identity provider / directory

periodic reviewEvidence produced at each review

Exception reports for accounts still active after the leaver date · Identity provider / directory

governing documentDocuments that govern the control

Defined timeframes for access removal on termination and for changes on role moves · Policy repository / GRC workspace
Leaver and mover samples comparing HR effective date with account disable or change date · Policy repository / GRC workspace

First move

Start with the 1 of 4 artefacts that already live in a system (Identity provider / directory); keep the periodic reviews but log each one as a dated record with a named reviewer.

Common gaps auditors find

No defined timeframe, so timeliness cannot be tested
Cloud console and SaaS accounts left active after directory removal
Role moves add new access without removing the old

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-06 Access Provisioning · IAM-08 Access Review