Skip to content

Egress Filtering

What is Egress Filtering?

The practice of monitoring and controlling outbound network traffic to prevent unauthorised data transfers and communication with known malicious destinations. A key defence against data exfiltration and malware beaconing.

Information Security

What the standards actually require on egress filtering

Requirements naming egress filtering across this standard, quoted from the control text.

PCI DSS 4.01 control

Service providers must apply intrusion-detection and/or intrusion-prevention methods that find the covert channels malware uses to communicate, raise alerts on them or block them, and deal with them, such as DNS tunneling to command-and-control servers.

11.5.1.1 · 11.5.1.1 Service providers detect covert malware channels →

Questions people ask about egress filtering

What is Egress Filtering?
The practice of monitoring and controlling outbound network traffic to prevent unauthorised data transfers and communication with known malicious destinations. A key defence against data exfiltration and malware beaconing.
Why is Egress Filtering important for compliance?
Egress Filtering is a key concept in Information Security. Understanding egress filtering helps organizations meet regulatory requirements, reduce risk, and demonstrate due diligence during audits. Our compliance platform maps 1,016 frameworks with 316K cross-framework control mappings.
Which compliance frameworks address Egress Filtering?
Egress Filtering appears in the requirement text of PCI DSS 4.0. Across these standards we have identified 1 control that names it directly, each linked to the control text on the compliance platform.
Where can I learn more about Egress Filtering?
Explore our compliance framework pages to see how egress filtering applies across different standards and regulations. Our implementation guides provide step-by-step guidance, and the compliance platform offers AI-powered analysis of how this concept maps across 1,016 frameworks.

See how Egress Filtering applies across compliance frameworks

Our platform maps 1,016 frameworks with 316K cross-framework control mappings. Explore how this concept is addressed across standards.

Written and maintained by Gerard Blokdyk, The Art of Service.