CIS Safeguard 13.4: Perform Traffic Filtering Between Network Segments

CIS Safeguard 13.4: Perform Traffic Filtering Between Network Segments

By Steve Gold
Posted in Security
On August 25, 2026

In Severance, the employees of Lumon Industries live in a world of strict compartmentalization. Your work self cannot access what your personal self knows, and you certainly cannot wander into another department's floor without authorization. Every boundary is enforced at the threshold, with no exceptions. That is exactly what good network traffic filtering looks like.

What Is Perform Traffic Filtering Between Network Segments?

Traffic filtering between network segments means controlling what can talk to what across the internal boundaries of your network. Not every device needs to reach every other device, and not every segment should be accessible from every other segment.

The official CIS definition:

Perform traffic filtering between network segments, where appropriate, on enterprise assets. Example implementations include the use of a next generation firewall (NGFW) as a network gateway, or other network-based filtering solution (for example, router-based Access Control Lists (ACLs)).

The word "appropriate" is doing real work in that sentence. You are not required to filter everything everywhere. You are required to think about where the boundaries matter and actually enforce them there.

Why It Matters

Attackers who land inside one part of your network should not automatically inherit access to everything else. If your guest Wi-Fi can reach your financial systems, that is a problem waiting to happen. If a compromised workstation can talk directly to your domain controllers, attackers will use that path, and they will use it fast.

Traffic filtering creates friction. Friction slows attackers down. Slowing them down gives you time to detect and respond before the situation gets worse.

From a compliance perspective, frameworks like PCI-DSS, HIPAA, and NIST all point toward network segmentation with enforced boundaries. Auditors want to see documented controls. Traffic filtering rules are documented controls. This one does double duty.

Key Details or How It Works

  • Network segments are logical groupings of assets: production servers, user workstations, guest access, IoT devices, and management interfaces each belong in their own zone.
  • Traffic filtering rules define what is permitted to flow between segments. Everything else is denied.
  • Next-generation firewalls (NGFWs) operate at Layer 7 and can filter based on application identity, user context, and behavior, not just IP addresses and ports.
  • Router-based ACLs are a lighter-weight option that enforces basic filtering at Layer 3, appropriate for simpler environments or as a first step.
  • East-west traffic (between internal segments) matters just as much as north-south traffic (to and from the internet). Most organizations underinvest here.
  • A default-deny posture means traffic is blocked unless explicitly permitted. That is the correct default.

How to Implement Perform Traffic Filtering Between Network Segments

  1. Map your network segments. Before you can filter traffic, you need to know what segments exist. Document your zones: user workstations, servers, DMZ, OT/IoT, management network, guest. If distinct segments do not exist yet, define them now based on sensitivity and function.
  2. Identify the legitimate traffic flows between segments. Work with application owners and IT to catalog what communication actually needs to happen across boundaries. A web server in your DMZ reaching a database on a specific port is a permitted flow. Everything else is not. Build from that list.
  3. Deploy filtering controls at segment boundaries. A NGFW is the preferred tool for enforcing this at scale. For smaller or simpler environments, ACLs on managed switches or routers can provide baseline enforcement. Place the control point at the boundary where segments meet, not somewhere downstream.
  4. Configure rules with a default-deny posture. Start with deny-all and add explicit permit rules for known-good traffic. Do not start with permit-all and try to block the bad stuff. You will miss something, and attackers will find it before you do.
  5. Test and validate before calling it done. Verify that permitted traffic flows as expected and that denied traffic is actually blocked. Use scanning tools or traffic analysis to confirm boundaries are working. Misconfigurations are common and easy to miss without active validation.
  6. Build a periodic rule review into your process. Traffic filtering rules go stale. Applications change, systems move, and business requirements shift. Schedule a review cadence, tie it to your change management process, and keep the rules current.

Final Thoughts

Lumon's floor access controls are fictional and dystopian, but the underlying principle is sound. You do not let people wander freely between sensitive areas just because they are already inside the building. Your network should work the same way. Define your floors, enforce the boundaries, and make sure your filtering devices are actually doing the job you think they are. Attackers count on flat, open networks. Do not hand them one.

Resources

Here is a link to the Policy Templates provided free of charge from the fine folks at the Center for Internet Security.

Looking for even more detail? Here you go. If this still does not satisfy your curiosity, DM me.

Official CIS Text

CIS Control 13: Network Monitoring and Defense Operate processes and tooling to establish and maintain comprehensive network monitoring and defense against security threats across the enterprise's network infrastructure and user base.

CIS Safeguard 13.4: Perform Traffic Filtering Between Network Segments Perform traffic filtering between network segments, where appropriate, on enterprise assets. Example implementations include the use of a next generation firewall (NGFW) as a network gateway, or other network-based filtering solution (for example, router-based Access Control Lists (ACLs)).

Shameless Marketing Information

Gotham Technology Group helps organizations design and implement network segmentation strategies, from NGFW deployment and zone-based architecture to ACL configuration and policy review. If your network is flatter than it should be, we can help you change that.

Steve Gold

Steve Gold

Steve Gold is the Cybersecurity Practice Director at Gotham Technology Group (Gotham). He is responsible for providing the vision and thought leadership to expand Gotham’s legacy of success and build a world-class cybersecurity practice. He works closely with Gotham’s customers, industry partners, and subject matter experts to develop relevant solutions for Gotham’s clients and prospects.

Prior to joining Gotham, Steve worked with the Center for Internet Security (CIS), where he expanded the global reach, revenue, and impact of the CIS Benchmarks, CIS Controls, and CIS Hardened Images. He led the efforts to promote the CIS portfolio of low-cost and no-cost cybersecurity products and services that help private and public organizations stay secure in the connected world. He grew a team of security specialists from 12 to over 40 to assist organizations with implementing security best practices in their continual journey of cybersecurity maturity.

During his more than 20-year career, Steve led teams responsible for developing and implementing technology solutions at some of the industry’s most recognized companies such as Varonis, VMware, Dell & Wyse Technology

Steve is a frequent speaker/moderator at industry conferences and webinars, covering a wide array of information security topics. He resides and works remotely in Baltimore, MD.