If your sites take cards, PCI DSS is your floor. The good news: the controls PCI 4 asks for map directly onto capabilities already in the platform — and they deploy to a thousand stores as easily as one, via zero-touch.
The mapping at a glance
| PCI DSS 4 asks for | Peplink control |
|---|---|
| Network segmentation of the cardholder data environment | VLANs + grouped networks & MAC lists + internal firewall rules |
| Strong cryptography in transit | AES-256 / TLS 1.3 SpeedFusion tunnels, per-link keys; FIPS mode on 8.6 |
| Restrict inbound/outbound traffic | Four-domain firewall with DPI and application blocking |
| Unique IDs, no shared/default accounts | Changeable usernames, rotating passwords, TACACS+/RADIUS |
| Track and monitor all access | NetFlow, URL & session logging, SNMP to your SIEM |
| Consistent config across all sites | InControl 2 zero-touch + group policies (hardening guide) |
The full step-by-step is in our PCI-DSS hardening guide for InControl 2, and the video below walks the whole pattern including zero-touch deployment to card-handling sites.
PCI DSS 4.1 white paper: our updated 4.1 white paper is being prepared for this page — ask us for the current draft in the meantime.