3.3.1.1 Full track data not stored after authorization
The full contents of any track are not retained after authorization.
5
artefacts
1
held by a system
0
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
- Data discovery scan for magstripe patterns · Vulnerability scanner / patch tooling
periodic reviewEvidence produced at each review
none for this control
governing documentDocuments that govern the control
- Application code search results · Document repository
- Database column audit · Policy repository / GRC workspace
- Sample QA test · Document repository
- Vendor confirmation letter · Vendor register / contract repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Vulnerability scanner / patch tooling 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
- Track data captured in debug logs
- Lab environments retain track
- Backups contain track data
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 SAD is not stored after authorization, even if encrypted. All sensitive authentication data received is rendered unrecoverable upon completion of the authorization process · 3.3.1.2 Card verification code not stored after authorization