3.3.2 SAD stored prior to authorization is encrypted
SAD stored electronically prior to completion of authorization is encrypted using strong cryptography.
5
artefacts
1
held by a system
2
at each review
hard
to go live
Document repository
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Encryption configuration for SAD storage · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Cryptographic library version evidence · Document repository
- Code review records · Source control / CI pipeline
governing documentDocuments that govern the control
- Key strength documentation · Document repository
- Test of stored SAD format · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Cloud console / configuration management on a schedule; put the documents under version control with an owner and review date, and log each review as a dated record with a named reviewer.
Common gaps auditors find
- Cleartext SAD on disk pre-auth
- Weak ciphers used
- No verification testing
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 sheet3.3.1.3 PIN and PIN block not stored after authorization · 3.3.3 SAD storage by issuers limited