4.2.1.1 Inventory of trusted keys and certificates
An inventory of trusted keys and certificates used to protect PAN during transmission is maintained.
5
artefacts
1
held by a system
2
at each review
hard
to go live
Key management / PKI
where the evidence lives
teal = a system already holds it · olive = produced at each review
system holds itEvidence a system already holds
- Automated discovery scan output · Key management / PKI
periodic reviewEvidence produced at each review
- Revocation check evidence · Key management / PKI
- Trust store review · Key management / PKI
governing documentDocuments that govern the control
- Certificate and key inventory with expiry dates · Policy repository / GRC workspace
- Renewal calendar · Policy repository / GRC workspace
First move
Mostly documents and reviews. Pull the 1 system-held artefact from your Key management / PKI 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
- No central inventory
- Expired certs in use
- Forgotten internal CAs
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 sheet4.2.1 Strong cryptography and security protocols are implemented as follows to safeguard PAN during transmission over open, public networks: • Only trusted keys and certificates are accepted. • Certificates used to safeguard PAN during transmission · 4.2.1.2 Wireless networks transmitting PAN use strong cryptography