3.3.1.2 Card verification code not stored after authorization
The card verification code is not retained after authorization.
5
artefacts
1
held by a system
2
at each review
hard
to go live
SIEM / log platform
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Log search for three- or four-digit CVV patterns · SIEM / log platform
periodic reviewEvidence produced at each review
- Application code review · Source control / CI pipeline
- Vendor attestations · Vendor register / contract repository
governing documentDocuments that govern the control
- Database column inventory · Policy repository / GRC workspace
- QA test cases · Document repository
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your SIEM / log platform 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
- CVV in app debug logs
- Saved in fraud screening systems
- Found in support tickets
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.1 Full track data not stored after authorization · 3.3.1.3 PIN and PIN block not stored after authorization