PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.2.3: 1.2.3 Accurate network diagram of CDE connections

The entity must keep one or more accurate network diagrams that show each connection linking the cardholder data environment to other networks, wireless networks included. Applicability: an up-to-date network diagram, or some other technical or topological means of identifying devices and network connections, can satisfy this requirement. Objective under the customized approach: a current depiction of the boundaries separating the CDE from every trusted and every untrusted network is kept and can be produced when needed.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 42 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 · 6 controls

FedRAMP High · 4 controls

  • CA-9 Internal System Connections
  • CM-8 System Component Inventory
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • PL-8 Security and Privacy Architectures

FedRAMP Moderate · 4 controls

  • CA-9 Internal System Connections
  • CM-8 System Component Inventory
  • CP-2(8) Contingency Plan | Identify Critical Assets (CP-2(8))
  • PL-8 Security and Privacy Architectures

ISO 27001:2022 · 4 controls

  • 5.9 Inventory of information and other associated assets
  • 8.20 Networks security
  • 8.22 Segregation of networks
  • 8.27 Secure system architecture and engineering principles

ISO 27002:2022 · 4 controls

  • 5.37 Documented operating procedures
  • 5.9 Inventory of information and other associated assets
  • 8.20 Networks security
  • 8.22 Segregation of networks

ISO 27701:2019 · 3 controls

  • 6.10.1 Network security management
  • 6.5.1 Responsibility for assets
  • 6.9.1 Operational procedures and responsibilities

CIS Controls v8 · 2 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-12.4 Establish and Maintain Architecture Diagram(s)

HIPAA Security Rule · 2 controls

ISO 22301:2019 · 2 controls

NIST SP 800-66 Rev 2 · 2 controls

SOC 2 · 2 controls

  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary
  • ANSSI-HYG-04 Identify the Most Sensitive Information and Servers and Maintain a Network Diagram

C5 (Germany) · 1 control

  • C5-COS-07 Documentation of the network topology

CMMC 2.0 · 1 control

  • NIST-CSF-ID.AM-03 Representations of the organization's authorized network communication and internal and external network data flows are maintained
  • P1-2.1.2 P1-2.1.2 Current network and data-flow records for every 3DS path

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