PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.4.4: 1.4.4 Cardholder data stores not reachable from untrusted networks

System components that store cardholder data must not be directly reachable from untrusted networks. Applicability: this does not target account data held in volatile memory, but it does apply where memory is used as persistent storage (for example a RAM disk); account data may sit in volatile memory only for as long as the related business process needs it, such as until the payment transaction completes. Objective under the customized approach: stored cardholder data cannot be reached from untrusted networks.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

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

  • AC-17 Remote Access
  • CM-12 Information Location (CM-12)
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(5) Deny by Default Allow by Exception

FedRAMP Moderate · 5 controls

  • AC-17 Remote Access
  • CM-12 Information Location (CM-12)
  • SC-7 Boundary Protection
  • SC-7(12) Boundary Protection | Host-based Protection (SC-7(12))
  • SC-7(5) Deny by Default Allow by Exception

ISO 27001:2022 · 5 controls

  • 7.1 Physical security perimeters
  • 8.12 Data leakage prevention
  • 8.20 Networks security
  • 8.22 Segregation of networks
  • 8.3 Information access restriction

CIS Controls v8 · 4 controls

  • CIS-12.2 Establish and Maintain a Secure Network Architecture
  • CIS-13.10 Perform Application Layer Filtering
  • CIS-13.4 Perform Traffic Filtering Between Network Segments
  • CIS-3.12 Segment Data Processing and Storage Based on Sensitivity

HIPAA Security Rule · 4 controls

ISO 27002:2022 · 4 controls

  • 7.1 Physical security perimeters
  • 8.20 Networks security
  • 8.22 Segregation of networks
  • 8.3 Information access restriction

ISO 27701:2019 · 4 controls

  • 6.10.1 Network security management
  • 6.5.2 Information classification
  • 6.6.1 Business requirements of access control
  • 6.8.1 Secure areas

NIST SP 800-66 Rev 2 · 4 controls

  • ASBv3-DP-1 Discover, classify, and label sensitive data
  • NS-2 Secure cloud services with network controls

CMMC 2.0 · 2 controls

SOC 2 · 2 controls

  • 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
  • ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System
  • ASD37-22 Network segmentation (Excellent)
  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

UK Cyber Essentials · 1 control

  • CE-FW.1 Boundary Firewalls Deployed

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