3.4.1 PAN is masked when displayed (the BIN and last four digits are the maximum number of digits to be displayed), such that only personnel with a legitimate business need can
PAN is masked when displayed (the BIN and last four digits are the maximum number of digits to be displayed), such that only personnel with a legitimate business need can.
5
artefacts
1
held by a system
1
at each review
hard
to go live
Policy repository / GRC workspace
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Asset inventory export · Cloud console / configuration management
periodic reviewEvidence produced at each review
- Baseline change records · Cloud console / configuration management
governing documentDocuments that govern the control
- Approved baselines per OS and platform · Policy repository / GRC workspace
- Examine baseline currency · Policy repository / GRC workspace
- Test inventory completeness · Policy repository / GRC workspace
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
- Shadow IT not in inventory
- Firmware versions not tracked
- Baseline for network devices missing
- Documentation not version controlled
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.3 SAD storage by issuers limited · 3.4.2 Technical controls prevent unauthorized PAN copy