12.3.4 Hardware and software technologies reviewed annually
Hardware and software technologies in use are reviewed at least once every 12 months to confirm vendor support and address end-of-life or unsupported components.
5
artefacts
0
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
none for this control
periodic reviewEvidence produced at each review
- Annual review records · Policy repository / GRC workspace
governing documentDocuments that govern the control
- Inventory of hardware and software with vendor support status · Vendor register / contract repository
- EOL or unsupported component list with plan · Policy repository / GRC workspace
- Sample replacement projects · Policy repository / GRC workspace
- Vendor support contracts · Vendor register / contract repository
First move
This control is evidenced by people and documents, not systems. Put the document under version control with an owner and review date, and log each review as a record with reviewer and date. Do not try to automate it.
Common gaps auditors find
- EOL components in CDE
- No annual review
- No remediation 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.3 Cryptographic cipher suites and protocols inventory · 12.4.1 Executive management responsibility for the PCI DSS compliance program (service providers)