PCI DSS 4.0
Req 1: Network Security Controls

PCI DSS 4.0 1.4.1: 1.4.1 NSCs between trusted and untrusted networks

Network security controls must be implemented between trusted and untrusted networks. The guidance explains this lets the entity monitor and control every connection into and out of trusted networks; the Requirement 1 overview lists the internet, business-to-business links, wireless, carrier and third-party networks, and corporate networks outside PCI DSS scope as examples of untrusted networks. Applicability: no special notes; applies to every assessed entity. Customized approach objective: unauthorised traffic cannot cross the boundary between trusted and untrusted networks.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 59 controls across 24 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

FedRAMP High · 7 controls

  • AC-17(3) Managed Access Control Points
  • AC-4 Information Flow Enforcement
  • SC-7 Boundary Protection
  • SC-7(3) Access Points
  • SC-7(4) External Telecommunications Services
  • SC-7(5) Deny by Default Allow by Exception
  • SC-7(8) Route Traffic to Authenticated Proxy Servers

FedRAMP Moderate · 7 controls

  • AC-17(3) Managed Access Control Points
  • AC-4 Information Flow Enforcement
  • SC-7 Boundary Protection
  • SC-7(3) Access Points
  • SC-7(4) External Telecommunications Services
  • SC-7(5) Deny by Default Allow by Exception
  • SC-7(8) Route Traffic to Authenticated Proxy Servers

CIS Controls v8 · 6 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-13.9 Deploy Port-Level Access Control
  • CIS-4.4 Implement and Manage a Firewall on Servers
  • CIS-4.5 Implement and Manage a Firewall on End-User Devices

NIST SP 800-53 Rev 5 · 5 controls

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 4 controls

  • ANSSI-HYG-19 Segment the Network and Partition the Zones
  • ANSSI-HYG-22 Put in Place a Secure Internet Access Gateway
  • ANSSI-HYG-23 Partition Internet Facing Services from the Rest of the Information System
  • ANSSI-HYG-25 Secure Dedicated Network Interconnections with Partners

C5 (Germany) · 3 controls

  • C5-COS-01 Technical safeguards
  • C5-COS-02 Security requirements for connections in the Cloud Service Provider's network
  • C5-COS-03 Monitoring of connections in the Cloud Service Provider's network

ISO 27001:2022 · 3 controls

  • 8.20 Networks security
  • 8.21 Security of network services
  • 8.22 Segregation of networks

ISO 27002:2022 · 3 controls

  • 8.20 Networks security
  • 8.21 Security of network services
  • 8.22 Segregation of networks

ASD Strategies to Mitigate Cyber Security Incidents · 2 controls

  • ASD37-08 Deny direct internet connectivity (Excellent)
  • ASD37-22 Network segmentation (Excellent)

Azure Security Benchmark · 2 controls

  • NS-1 Establish network segmentation boundaries
  • NS-3 Deploy firewall at the edge of enterprise network

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

ISO 27701:2019 · 2 controls

  • 6.10 Communications security
  • 6.10.1 Network security management

NIST SP 800-172 · 2 controls

  • 3.1.3e Employ Secure Information Transfer Solutions
  • 3.13.1e Create Diversity in System Components to Limit Malicious Code Propagation

AWS Well-Architected Security Pillar · 1 control

Australia Consumer Data Right - Banking (CDR) · 1 control

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

CMMC 2.0 · 1 control

HIPAA Security Rule · 1 control

NIST Cybersecurity Framework 2.0 · 1 control

  • NIST-CSF-PR.IR-01 Networks and environments are protected from unauthorized logical access and usage

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-66 Rev 2 · 1 control

PCI 3DS Core Security Standard · 1 control

  • P1-2.1.3 P1-2.1.3 Physical or logical limits between trusted and untrusted zones

SOC 2 · 1 control

  • SOC2-CC6.6 CC6.6 Protection against threats from outside the system boundary

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

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

MCP endpointAll PCI DSS 4.0 controls