PCI DSS 4.0
Req 2: Secure Configurations

PCI DSS 4.0 2.2.6: 2.2.6 System security parameters configured against misuse

System security parameters must be configured so that they prevent misuse. The guidance recommends that configuration standards and related processes address the settings with known security implications on every kind of system deployed, including parameters used to reach cloud portals, and that the people who configure or administer systems understand those settings. Applicability: no special notes; applies to every assessed entity. Objective under the customized approach: wrongly set security parameters give no route to compromising system components.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 45 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.

ASD Strategies to Mitigate Cyber Security Incidents · 4 controls

  • ASD37-03 Configure Microsoft Office macro settings (Essential)
  • ASD37-04 User application hardening (Essential)
  • ASD37-09 OS generic exploit mitigation (Excellent)
  • ASD37-11 Operating system hardening (Very Good)

HIPAA Security Rule · 4 controls

ISO 27001:2022 · 4 controls

  • 8.20 Networks security
  • 8.27 Secure system architecture and engineering principles
  • 8.32 Change management
  • 8.9 Configuration management

NIST SP 800-66 Rev 2 · 4 controls

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC5.3 CC5.3 Deploying controls through policies and procedures (COSO principle 12)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CIS Controls v8 · 3 controls

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.6 Securely Manage Enterprise Assets and Software
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

CMMC 2.0 · 3 controls

FedRAMP High · 3 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification

FedRAMP Moderate · 3 controls

  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings
  • CM-6(1) Automated Management, Application, and Verification

AWS Well-Architected Security Pillar · 2 controls

  • SEC01-BP06 Automate deployment of standard security controls
  • SEC06-BP02 Provision compute from hardened images

Azure Security Benchmark · 2 controls

  • ASBv3-PV-3 Define and establish secure configurations for compute resources
  • ASBv3-PV-4 Audit and enforce secure configurations for compute resources

ACSC Essential Eight · 1 control

  • E8-UAH-ML2 User Application Hardening - Maturity Level 2

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-14 Apply a Minimum Security Level Across the Whole Estate

C5 (Germany) · 1 control

  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

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

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

ISO 27701:2019 · 1 control

  • 6.9.6 Technical vulnerability management

NIST Cybersecurity Framework 2.0 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-53 Rev 5 · 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 2: Secure Configurations

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

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

MCP endpointAll PCI DSS 4.0 controls