2.3.2 Wireless encryption keys rotated
For wireless environments connected to the CDE, encryption keys are changed when personnel with knowledge of the key leave or when keys are suspected of being compromised.
5
artefacts
2
held by a system
2
at each review
moderate
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
- Wireless key rotation log · Key management / PKI
- Leaver process linked to key rotation · Key management / PKI
periodic reviewEvidence produced at each review
- Incident records triggering rotation · Key management / PKI
- Distribution records · Key management / PKI
governing documentDocuments that govern the control
- Approved key management procedure · Policy repository / GRC workspace
First move
Start with the 2 of 5 artefacts that already live in a system (Key management / PKI); keep the periodic reviews but log each one as a dated record with a named reviewer.
Common gaps auditors find
- No rotation on leavers
- PSKs never changed
- No documented process
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 sheet2.3.1 Wireless vendor defaults changed before installation · 3.1.1 All security policies and operational procedures that are identified in Requirement 3 are: • Documented. • Kept up to date. • In use. • Known to all affected parties