12.3.3 Cryptographic cipher suites and protocols inventory
Cryptographic cipher suites and protocols in use are documented and reviewed at least every 12 months, with a plan to address known weaknesses and respond to changes.
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
- Monitoring for deprecation · SIEM / log platform
periodic reviewEvidence produced at each review
- Annual review with NIST or industry alignment · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Inventory of crypto algorithms, protocols, key sizes · Policy repository / GRC workspace
- Migration plan for weak algorithms · Policy repository / GRC workspace
- Vendor and product list using crypto · Vendor register / contract 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
- No inventory
- Weak ciphers not flagged
- No migration plan
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 sheet12.3.2 TRA for customized approach · 12.3.4 Hardware and software technologies reviewed annually