IAM-14 Strong Authentication
Authenticate access to systems, applications and data, using multifactor authentication at minimum for privileged users and sensitive data, and digital certificates or equivalent strength for system identities.
4
artefacts
1
held by a system
2
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
system holds itEvidence a system already holds
- Authentication configuration per system showing the factors required · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence multifactor authentication covers all privileged users and sensitive data access · Identity provider / directory
- Exception records where multifactor authentication is not applied · Identity provider / directory
governing documentDocuments that govern the control
- The mechanism used for system identity authentication · 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
- Multifactor authentication enforced at the perimeter but bypassable by direct application access
- Service and system identities authenticating with static shared secrets
- Exceptions granted with no expiry or compensating control
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 sheetIAM-13 Uniquely Identifiable Users · IAM-15 Passwords Management