PCI DSS 4.0
Req 6: Secure Systems and Software

PCI DSS 4.0 6.1.1: 6.1.1 Requirement 6 policies and procedures maintained and communicated

Every security policy and operational procedure that Requirement 6 calls for must meet four conditions: it is written down; it is kept current; it is actually applied in practice; and every affected party is aware of it. This covers the full set of documents behind secure development, vulnerability handling, protection of public-facing web applications and change control. It applies to all entities. Customized approach objective: the expectations, controls and oversight for Requirement 6 activities are set out and followed by the relevant staff, with every supporting activity performed in a repeatable, consistent way that matches what management intends.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 46 controls across 17 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 · 7 controls

ISO 22301:2019 · 5 controls

  • 5.2.2 Communicating the business continuity policy
  • 6.1.1 Determining risks and opportunities
  • 7.4 Communication
  • 7.5.3 Control of documented information
  • 8.4.4 Business continuity plans

ISO 27701:2019 · 5 controls

  • 5.3.2 Policy
  • 5.5.4 Communication
  • 5.5.5 Documented information
  • 6.2.1 Management direction for information security
  • 6.9.1 Operational procedures and responsibilities

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

ISO 27002:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.36 Compliance with policies, rules and standards for information security
  • 5.37 Documented operating procedures
  • 6.3 Information security awareness, education and training

ISO/IEC 42001:2023 · 3 controls

  • 5.2 AI policy
  • 7.4 Communication
  • 7.5.3 Control of documented information

SOC 2 · 3 controls

  • SOC2-CC2.2 CC2.2 Internal communication of objectives and control responsibilities (COSO principle 14)
  • SOC2-CC4.2 CC4.2 Evaluating and communicating control deficiencies (COSO principle 17)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)

FedRAMP High · 2 controls

  • SA-5 System Documentation
  • SI-1 Policy and Procedures

FedRAMP Moderate · 2 controls

  • SA-5 System Documentation
  • SI-1 Policy and Procedures

HIPAA Security Rule · 2 controls

NIST Cybersecurity Framework 2.0 · 2 controls

  • NIST-CSF-GV.PO-01 Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
  • NIST-CSF-GV.PO-02 Policy for managing cybersecurity risks is reviewed, updated, communicated, and enforced to reflect changes in requirements, threats, technology, and organizational mission

NIST SP 800-218 · 2 controls

Azure Security Benchmark · 1 control

  • ASBv3-GS-10 Define and implement DevOps security strategy

C5 (Germany) · 1 control

  • C5-DEV-01 Policies for the development/procurement of information systems

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 1 control

  • CCM-AIS-01 Application and Interface Security Policy and Procedures

NIST SP 800-171 Rev 3 · 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.1.1 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 46 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls