EvidenceSheet

IA-12 Identity proofing

Requires users who need accounts for logical access to be identity proofed to the assurance level applicable under the relevant standards, requires identities to be resolved to a unique individual, and requires identity

4
artefacts
0
held by a system
2
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

system holds itEvidence a system already holds

none for this control

periodic reviewEvidence produced at each review

  • Records of identity evidence collected, validated and verified per user population · Identity provider / directory
  • Evidence that each identity resolves to a unique individual with no shared records · Identity provider / directory

governing documentDocuments that govern the control

  • Documented identity proofing procedure and the assurance level applied · Policy repository / GRC workspace
  • Distinct proofing treatment for remote onboarding and for contractors · Policy repository / GRC workspace

First move

This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.

Common gaps auditors find

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

IA-11 Re-authentication · IA-13 Identity Providers and Authorization Servers. Employ identity providers and authorization servers to manage user, device, and non-person entity (NPE) identities, attributes, and access rights supporting authentication and authorization decisions in accordance with [organization-defined] using