SC.L2-3.13.15 Communications Authenticity
Protect the authenticity of communications sessions so a session cannot be hijacked or spoofed.
3
artefacts
2
held by a system
1
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
- Session authenticity mechanism configuration, for example session tokens and mutual authentication · Identity provider / directory
- Configuration preventing session fixation and reuse · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Evidence sessions are bound and validated · Document repository
governing documentDocuments that govern the control
none for this control
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
- Confidentiality protected while session authenticity is not
- Session identifiers predictable or not regenerated after authentication
- Application sessions 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 sheetSC.L2-3.13.14 Voice over Internet Protocol · SC.L2-3.13.16 Data at Rest