PCI DSS 4.0
Req 12: Information Security Policies

PCI DSS 4.0 12.3.4: 12.3.4 Annual review of hardware and software technologies

Hardware and software in use must undergo a check at least every 12 months, covering at minimum: analysis that vendors still supply timely security fixes; analysis that the technologies still support, and do not obstruct, PCI DSS compliance; documentation of industry announcements or trends about a technology, for instance a vendor's end-of-life notice; and a remediation plan for outdated technologies, including those with announced end-of-life, approved by senior management. Objective under the customized approach: hardware and software stay current and vendor supported, and plans to retire or replace unsupported components are reviewed periodically. Future-dated: treated as a best practice up to 31 March 2025 and mandatory since then.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 43 controls across 23 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 4 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-9.1 Ensure Use of Only Fully Supported Browsers and Email Clients

ISO 27001:2022 · 4 controls

  • 5.22 Monitoring, review and change management of supplier services
  • 7.13 Equipment maintenance
  • 8.19 Installation of software on operational systems
  • 8.8 Management of technical vulnerabilities

NIST SP 800-53 Rev 5 · 4 controls

NIST Cybersecurity Framework 2.0 · 3 controls

  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 2 controls

  • ANSSI-HYG-34 Define an Update Policy for Information System Components
  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

CMMC 2.0 · 2 controls

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

FedRAMP High · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components (SA-22)

FedRAMP Moderate · 2 controls

  • CM-8 System Component Inventory
  • SA-22 Unsupported System Components (SA-22)

ISO 27002:2022 · 2 controls

  • 5.9 Inventory of information and other associated assets
  • 8.8 Management of technical vulnerabilities

NIST SP 800-161 Rev 1 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-SU.1 Software Licensed and Supported
  • CE-SU.4 Remove Out-of-Support Software

APRA CPS 234 · 1 control

  • CPS234-P17 Active Maintenance of Capability Against Change

ASD Strategies to Mitigate Cyber Security Incidents · 1 control

  • ASD37-19 Patch operating systems (Essential)

AWS Well-Architected Security Pillar · 1 control

  • SEC01-BP08 Evaluate and implement new security services and features regularly

C5 (Germany) · 1 control

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

NIS2 Directive · 1 control

  • Art.21.3 Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-172 · 1 control

  • 3.11.5e Assess Effectiveness of Security Solutions

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Req 12: Information Security Policies

You are reading one control. How much of PCI DSS 4.0 have you already done?

PCI DSS 4.0 12.3.4 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of PCI DSS 4.0 your existing evidence covers. Hold ISO 27001:2022 and 139 of 280 PCI DSS 4.0 controls already carry evidence.

If you hold ISO 27001:202249.6% covered · 141 gapsIf you hold FedRAMP Moderate49.3% covered · 142 gapsIf you hold NIST SP 800-53 Rev 547.5% covered · 147 gapsIf you hold ISO 27002:202243.2% covered · 159 gapsIf you hold CIS Controls v838.2% covered · 173 gapsIf you hold Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.136.4% covered · 178 gaps

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 415 were rejected on the ISO 27001:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

The graph holds this control, the 43 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls