PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.2.4: 1.2.4 Accurate data-flow diagram for account data

The entity must keep one or more accurate data-flow diagrams that (a) show every path account data takes through networks and systems, and (b) are revised as required when the environment changes. Applicability: a data-flow diagram, or another technical or topological solution identifying how account data moves across systems and networks, can meet this requirement. Objective under the customized approach: a picture of how account data travels between system components and over network segments is kept and can be produced.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 36 controls across 15 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

SOC 2 · 5 controls

  • SOC2-C1.1 C1.1 Identifying and maintaining confidential information
  • SOC2-CC2.1 CC2.1 Relevant, quality information to support internal control (COSO principle 13)
  • SOC2-CC3.2 CC3.2 Identifying and analysing risks to objectives (COSO principle 7)
  • SOC2-CC6.1 CC6.1 Logical access security over protected information assets
  • SOC2-CC7.1 CC7.1 Detecting configuration changes and new vulnerabilities

ISO 27002: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

CIS Controls v8 · 3 controls

  • CIS-12.4 Establish and Maintain Architecture Diagram(s)
  • CIS-3.2 Establish and Maintain a Data Inventory
  • CIS-3.8 Document Data Flows

FedRAMP High · 3 controls

  • AC-4 Information Flow Enforcement
  • CM-12 Information Location (CM-12)
  • PL-8 Security and Privacy Architectures

FedRAMP Moderate · 3 controls

  • AC-4 Information Flow Enforcement
  • CM-12 Information Location (CM-12)
  • PL-8 Security and Privacy Architectures

ISO 27001:2022 · 3 controls

  • 5.9 Inventory of information and other associated assets
  • 8.20 Networks security
  • 8.22 Segregation of networks

ISO 22301:2019 · 2 controls

  • 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.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.

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