IA.L2-3.5.4 Replay-Resistant Authentication
Use authentication mechanisms that resist replay for network access to both privileged and non privileged accounts.
3
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
- Authentication protocol configuration demonstrating replay resistance · Identity provider / directory
periodic reviewEvidence produced at each review
- Evidence deprecated protocols vulnerable to replay are disabled · Identity provider / directory
governing documentDocuments that govern the control
- Coverage across network accessible services · Policy repository / GRC workspace
First move
Start with the 1 of 3 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
- Legacy authentication protocols retained for compatibility
- Replay resistance assumed rather than verified
- Application level authentication outside the assessed scope
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.L2-3.5.3 Multifactor Authentication · IA.L2-3.5.5 Identifier Reuse