IA-2 Identification and Authentication (Organizational Users)
Uniquely identify and authenticate organizational users and associate identity with processes acting on behalf of users.
6
artefacts
3
held by a system
0
at each review
easy
to go live
Identity provider / directory
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- MFA enrolment report for all privileged and remote users · Identity provider / directory
- Password policy configuration export from the identity provider · Identity provider / directory
- Service account credential vault inventory and rotation logs · Identity provider / directory
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Control implementation statement for IA-2 citing the system mission and inheritance from common controls · Policy repository / GRC workspace
- Authenticator lifecycle procedure including reset and revocation · Policy repository / GRC workspace
- Identification and authentication policy · Policy repository / GRC workspace
First move
Automate the pull from your Identity provider / directory. Scheduled export of users, roles and MFA state from the directory; access-review completion pulled from the IdP, not a spreadsheet.
Common gaps auditors find
- Default vendor credentials remain on appliances and IoT devices
- Password complexity enforced but reuse not blocked across systems
- Federation trust relationships not reviewed when partnerships change
- MFA exceptions granted indefinitely without compensating controls
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 sheetIA-1 Policy and Procedures · IA-2(1) MFA to Privileged Accounts