`PR.AA-02` Identities are proofed and bound to credentials based on the context of interactions

Q: What evidence do auditors commonly ask for on PR.AA-02 Identities are proofed and bound to credentials based on the context of interactions?

Identity proofing policy aligned to risk tiers; Issuance and binding records for credentials; Re proofing triggers for elevated access; Identity verification audit logs; Exception register for proofing variances.

Identities are proofed and bound to credentials based on the context of interactions. Control from NIST Cybersecurity Framework 2.0 framework, domain: PR - Protect.

Source: NIST CSF 2.0, PR.AA-02. 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 NIST CSF 2.0 in the compliance library.

artefacts

held by a system

at each review

hard

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 verification audit logs · SIEM / log platform

periodic reviewEvidence produced at each review

Issuance and binding records for credentials · Identity provider / directory

governing documentDocuments that govern the control

Identity proofing policy aligned to risk tiers · Policy repository / GRC workspace
Re proofing triggers for elevated access · Document repository
Exception register for proofing variances · Policy repository / GRC workspace

First move

Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.

Common gaps auditors find

Proofing relies on email only
Binding records incomplete
Re proofing never triggered
Exceptions never reviewed

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

PR.AA-01 Identities and credentials for authorized users, services, and hardware are managed by the organization · PR.AA-03 Users, services, and hardware are authenticated