PCI DSS 4.0
Req 2: Secure Configurations

PCI DSS 4.0 2.2.4: 2.2.4 Only necessary functionality enabled

Only the services, protocols, daemons and functions that are needed may be enabled, and all functionality that is not needed must be removed or disabled. The guidance gives examples of unneeded functionality, such as drivers, scripts, subsystems, features, file systems, Bluetooth and USB interfaces, and unused web servers, and explains that removing it narrows the attack surface. Applicability: no special notes; applies to every assessed entity. Objective under the customized approach: system components cannot be compromised through unnecessary functionality present on them.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

ASD Strategies to Mitigate Cyber Security Incidents · 4 controls

  • ASD37-01 Application control (Essential)
  • ASD37-04 User application hardening (Essential)
  • ASD37-10 Server application hardening (Very Good)
  • ASD37-11 Operating system hardening (Very Good)

ISO 27001:2022 · 4 controls

  • 8.20 Networks security
  • 8.22 Segregation of networks
  • 8.27 Secure system architecture and engineering principles
  • 8.9 Configuration management

SOC 2 · 4 controls

  • SOC2-CC5.2 CC5.2 General controls over technology (COSO principle 11)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC6.8 CC6.8 Preventing and detecting unauthorised or malicious software
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure

CIS Controls v8 · 3 controls

  • CIS-12.3 Securely Manage Network Infrastructure
  • CIS-2.3 Address Unauthorized Software
  • CIS-4.8 Uninstall or Disable Unnecessary Services on Enterprise Assets and Software

FedRAMP High · 3 controls

FedRAMP Moderate · 3 controls

ACSC Essential Eight · 2 controls

  • E8-UAH-ML1 User Application Hardening - Maturity Level 1
  • E8-UAH-ML3 User Application Hardening - Maturity Level 3

Azure Security Benchmark · 2 controls

  • AM-2 Use only approved services
  • ASBv3-NS-8 Detect and disable insecure services and protocols

C5 (Germany) · 2 controls

  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CMMC 2.0 · 2 controls

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

HIPAA Security Rule · 2 controls

NIST Cybersecurity Framework 2.0 · 2 controls

NIST SP 800-53 Rev 5 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

PCI 3DS Core Security Standard · 2 controls

  • P1-3.2.5 P1-3.2.5 Build standards remove defaults, excess functions and mixed trust levels
  • P2-3.4.1 P2-3.4.1 Only required HTTP methods accepted

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

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

AWS Well-Architected Security Pillar · 1 control

CFTC System Safeguards (17 CFR 37, 38, 39, 49) · 1 control

ISO 27002:2022 · 1 control

  • 8.9 Configuration management

ISO 27701:2019 · 1 control

  • 6.9.5 Control of operational software

NIST SP 800-171 Rev 3 · 1 control

UK Cyber Essentials · 1 control

  • CE-SC.1 Remove or Disable Unused Software

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.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 48 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpointAll PCI DSS 4.0 controls