8.3.2 Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components
Strong cryptography is used to render all authentication factors unreadable during transmission and storage on all system components.
5
artefacts
2
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
- Vendor documentation and system configuration showing authentication factors are rendered unreadable with strong cryptography in transmission and in storage · Identity provider / directory
- Capture or configuration evidence that authentication factors are not sent in the clear on any path · Identity provider / directory
periodic reviewEvidence produced at each review
- Key or salt management evidence for the stored factors · Identity provider / directory
governing documentDocuments that govern the control
- Examination of authentication factor repositories confirming stored values are not readable · Policy repository / GRC workspace
- Evidence the hashing or encryption method meets a strong cryptography definition, including the algorithm and parameters · Policy repository / GRC workspace
First move
Start with the 2 of 5 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
- Application credentials protected while an underlying directory, database or legacy store keeps reversible or weakly hashed values
- Transmission protected to the front end and forwarded internally in the clear
- Legacy hash algorithms retained for old accounts because rehashing requires a reset
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 sheet8.3.1 All user access to system components for users and administrators is authenticated via at least one of the following authentication factors: • Something you know, such as a password or passphrase. • Something you · 8.3.3 User identity is verified before modifying any authentication factor