Hands-on tutorial
Tutorials · Compliance
PCI DSS v4.0 for Networks: Segmentation, Firewalls and Wi-Fi
How the Payment Card Industry Data Security Standard applies to your network: defining the cardholder data environment, segmentation to reduce scope, firewall and router rules, wireless, logging, testing and secure management.
Quick answer
PCI DSS applies to every organisation that stores, processes or transmits payment card data. Version 4.0 (with 4.0.1) is the current standard; its future-dated requirements became mandatory on 31 March 2025.
The most important network decision is segmentation: isolating the cardholder data environment (CDE) so that the rest of the network is out of scope.
This guide explains network controls that commonly support compliance. It is not legal advice; confirm your obligations with your legal or compliance adviser.
Key terms
- CDE
- Cardholder data environment: systems that store, process or transmit card data, and systems connected to them.
- Segmentation
- Network controls that isolate the CDE so that other systems cannot affect it; this reduces assessment scope but must be tested.
- QSA / SAQ
- Qualified security assessor; self-assessment questionnaire for smaller merchants.
Before you start
- An inventory of payment systems: POS terminals, payment servers, kiosks
- Data-flow diagrams showing how card data enters and leaves
- Your acquirer's requirements and SAQ type
Step by step
Define the CDE
List every system that touches card data and everything that can connect to it. Draw network and card-data-flow diagrams (Requirement 1.2.3 and 1.2.4).
Segment the CDE
Place POS terminals and payment servers in a dedicated VLAN and firewall zone. Allow only the flows to the payment processor and required management systems.
POS VLAN 60 → payment processor: TCP 443 POS VLAN 60 → everything else: deny Guest / staff → POS VLAN: deny
Control traffic with firewalls and ACLs
Implement network security controls between the CDE and other networks, with documented business justification for every allowed rule, and review rules at least every six months.
Secure wireless
Keep guest Wi-Fi fully isolated from the CDE. If wireless is used in the CDE, use strong encryption and authentication, and test for rogue access points every quarter (Requirement 11.2).
Harden and manage securely
Change vendor defaults, disable insecure services, use SSH/HTTPS for management, MFA for all access into the CDE, and keep firmware patched.
Log and monitor
Log access to CDE systems and security events, synchronise time, review logs daily (automated tools help) and keep logs for at least 12 months, three months immediately available.
Test segmentation and vulnerabilities
Run internal and external vulnerability scans every quarter and penetration tests yearly, including segmentation testing (every six months for service providers).
Keep backup connectivity in scope
If 4G/5G backup carries payment traffic, it must meet the same controls: firewall rules, encryption and logging.
Commands are generic, industry-standard examples. Exact syntax and menu names vary by model and firmware; check your device's manual on the Documentation page.
Pro tips
- The smaller the CDE, the cheaper and easier compliance becomes.
- Point-to-point encrypted (P2PE) payment terminals can reduce scope further.
- Keep evidence: rule reviews, scan reports and change records.
PCI DSS v4.0 requirements and network controls
| PCI DSS v4.0 requirement | Network control |
|---|---|
| 1: Network security controls | Firewalls/ACLs, segmentation, rule reviews |
| 2: Secure configurations | No vendor defaults, hardened devices |
| 4: Strong cryptography in transit | TLS, VPN, WPA2/WPA3-Enterprise |
| 8: Identify and authenticate | Individual accounts, MFA into the CDE |
| 10: Log and monitor | Central logging, time sync, retention |
| 11: Test regularly | Scans, penetration and segmentation tests, rogue AP detection |
Standards and references
FAQ
Frequently asked questions
Does guest Wi-Fi put us in PCI scope?
Not if it is properly segmented from the CDE and segmentation is tested.
Is a VLAN alone enough segmentation?
Only together with controls that block traffic between VLANs, such as firewall rules or ACLs, and testing that proves isolation.
How often must firewall rules be reviewed?
At least once every six months under PCI DSS v4.0.
Keep learning
Related guides
Retail store network design
Read more →Write ACLs on a Layer 3 switch
Read more →NJR gateways and controllers
Read more →4G backup router NJL-1503
Read more →NavEDGE security
Read more →GDPR for Network Teams: Practical Security Controls and Checklist
What the EU General Data Protection Regulation expects from your network: security of processing, access control, logging, encryption, guest Wi-Fi data, CCTV, retention and breach readiness, with a checklist you can apply.
Read more →Stuck on a step?
Ask Navijin technical support or an authorised partner for help with your configuration.