PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.2.1: 1.2.1 Ruleset configuration standards for NSCs

The entity must have configuration standards for the rulesets of its network security controls, and those standards must be defined, put into effect on the devices, and kept maintained over time. The guidance gives firewalls, cloud virtual networks and routers filtered by ACLs as examples of NSCs such standards cover. Applicability: no special notes; applies to every assessed entity. Customized approach objective: how NSCs are set up and how they behave is specified in advance and applied the same way across the environment.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 43 controls across 18 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 · 5 controls

ISO 27001:2022 · 4 controls

  • 5.1 Policies for information security
  • 5.37 Documented operating procedures
  • 8.20 Networks security
  • 8.9 Configuration management

SOC 2 · 4 controls

  • 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-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • SOC2-CC8.1 CC8.1 Managing changes to procedures, software, data and infrastructure
  • ASBv3-GS-4 Define and implement network security strategy
  • ASBv3-NS-7 Simplify network security configuration
  • ASBv3-PV-1 Define and establish secure configurations

FedRAMP High · 3 controls

  • CA-9 Internal System Connections
  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings

FedRAMP Moderate · 3 controls

  • CA-9 Internal System Connections
  • CM-2 Baseline Configuration
  • CM-6 Configuration Settings

ISO 27002:2022 · 3 controls

  • 5.37 Documented operating procedures
  • 8.20 Networks security
  • 8.9 Configuration management

C5 (Germany) · 2 controls

  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-OPS-23 Managing Vulnerabilities, Malfunctions and Errors - System Hardening

CIS Controls v8 · 2 controls

  • CIS-4.1 Establish and Maintain a Secure Configuration Process
  • CIS-4.2 Establish and Maintain a Secure Configuration Process for Network Infrastructure

CMMC 2.0 · 2 controls

ISO 27701:2019 · 2 controls

  • 5.6.1 Operational planning and control
  • 6.10.1 Network security management

NIST SP 800-171 Rev 3 · 2 controls

  • AUCDR-IS-2 Secure the network and systems within the data environment

UK Cyber Essentials · 1 control

  • CE-FW.2 Change Default Firewall Passwords

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 1: Network Security Controls

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

PCI DSS 4.0 1.2.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.

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.

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.