PSS-05 Authentication Mechanisms
Offer authentication mechanisms able to force strong multi factor authentication for the customers' users, IT components and applications, deploy them at every access point that interacts with the service, and make their
4
artefacts
1
held by a system
1
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
- Configuration evidence that multi factor authentication can be enforced per tenant · Identity provider / directory
periodic reviewEvidence produced at each review
- Test result demonstrating rejection of a single factor privileged login · Identity provider / directory
governing documentDocuments that govern the control
- Inventory of access points including APIs and legacy endpoints with their authentication settings · Policy repository / GRC workspace
- Policy setting showing enforcement applied to privileged accounts · 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
- Strong authentication offered on the web console but not for API or command line access
- Multi factor available as an option yet not enforceable for privileged roles
- Break glass accounts permanently exempted from the requirement
- Machine and application identities left on static long lived credentials
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 sheetPSS-04 Error handling and Logging Mechanisms · PSS-06 Session Management