PCI DSS 4.0
Req 6: Secure Systems and Software

PCI DSS 4.0 6.5.2: 6.5.2 Confirm PCI DSS controls after significant change

When a significant change is complete, the entity must confirm that every applicable PCI DSS requirement is in place on all new or altered systems and networks, and must update documentation where relevant. It applies to all entities. Applicability: such significant changes should also be recorded in, and reflected by, the scope confirmation the entity performs each year under Requirement 12.5.2. Customized approach objective: after a significant change, all system components are checked to be compliant with the PCI DSS requirements that apply to them.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

NIST SP 800-53 Rev 5 · 8 controls

ISO 22301:2019 · 5 controls

  • 6.3 Planning changes to the business continuity management system
  • 7.5.3 Control of documented information
  • 8.3.5 Implementation of solutions
  • 8.6 Evaluation of business continuity documentation and capabilities
  • 9.2.2 Audit programme(s)

CIS Controls v8 · 4 controls

  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-7.5 Perform Automated Vulnerability Scans of Internal Enterprise Assets
  • CIS-8.9 Centralize Audit Logs

CMMC 2.0 · 4 controls

FedRAMP High · 4 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • SR-11(2) Component Authenticity | Configuration Control for Component Service and Repair (SR-11(2))

FedRAMP Moderate · 4 controls

  • CM-3(2) Testing, Validation, and Documentation of Changes
  • CM-4 Impact Analyses
  • CM-4(2) Impact Analyses | Verification of Controls (CM-4(2))
  • SR-11(2) Component Authenticity | Configuration Control for Component Service and Repair (SR-11(2))

ISO/IEC 42001:2023 · 4 controls

  • 6.1.3 AI risk treatment
  • 7.5.2 Creating and updating documented information
  • 8.3 AI risk treatment
  • 9.2 Internal audit

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

ISO 27002:2022 · 3 controls

  • 5.36 Compliance with policies, rules and standards for information security
  • 5.8 Information security in project management
  • 8.32 Change management

C5 (Germany) · 2 controls

  • C5-DEV-05 Risk assessment, categorisation and prioritisation of changes
  • C5-DEV-06 Testing changes

HIPAA Security Rule · 2 controls

ISO 27001:2022 · 2 controls

  • 5.8 Information security in project management
  • 8.32 Change management

SOC 2 · 2 controls

  • SOC2-CC3.4 CC3.4 Identifying and assessing significant changes (COSO principle 9)
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

AWS Well-Architected Security Pillar · 1 control

  • SEC01-BP06 Automate deployment of standard security controls

Azure Security Benchmark · 1 control

  • PV-2 Audit and enforce secure configurations

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-ID.RA-07 Changes and exceptions are managed, assessed for risk impact, recorded, and tracked

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

NIST SP 800-66 Rev 2 · 1 control

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 6: Secure Systems and Software

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

PCI DSS 4.0 6.5.2 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 54 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls