Skip to content
Cyber Defense Technologies

Insights

Reference Architecture: Segmenting a Defense Contractor Network

Most defense contractors run one flat network that holds email, engineering data, controlled information and the guest Wi-Fi. A practical segmentation design in six zones, how traffic should flow between them, and how to get there without a forklift upgrade.

By Cyber Defense Technologies November 17, 2026 4 min read

Many defense contractors grew their networks the way most small businesses do: one office, one switch stack, one big network. Laptops, file servers, printers, engineering workstations, cameras and guest devices all sit side by side.

That design has two costs. When an attacker compromises one laptop, nothing stops them from reaching everything else. And when a contract requires protecting sensitive information, such as Controlled Unclassified Information (CUI) or export-controlled technical data, the requirements apply to the whole flat network, because everything can reach the data.

Segmentation addresses both. This reference architecture describes a practical design for a small or midsize contractor.

Six zones

Six zones for a contractor network

  1. Internet edge

    Firewalls, remote access and public services. Management never faces the internet.

  2. User zone

    Laptops and desktops. No workstation-to-workstation traffic.

  3. Server zone

    Business services, open only on the ports each service needs.

  4. Sensitive enclave

    Systems and people that handle CUI or other sensitive data.

  5. Management zone

    Administrative interfaces and backups, reached only from admin workstations.

  6. Guest and IoT

    Guest Wi-Fi, cameras, building systems and printers: internet access only.

Traffic between zones is denied by default and allowed only for named flows.

1. Internet edge

Firewalls, the VPN or remote access gateway, and any public-facing services. Nothing in this zone should be trusted by internal systems simply because it is "inside." Edge devices are the most attacked systems on the internet, as our monthly threat roundups show, so management interfaces must never face the internet.

2. User zone

Employee laptops and desktops. Users reach the services they need in the server zone and the internet through the edge. Workstations should not be able to reach each other directly; most ransomware spreads laterally between workstations.

3. Server zone

General business services: file shares, line-of-business applications, print servers and internal web applications. Only the ports each service needs are open to the user zone.

4. Sensitive enclave

Systems that store or process sensitive information, such as CUI, export-controlled data or proprietary engineering data, along with the workstations that work with it. Access is limited to named people on managed devices, with phishing-resistant MFA. Keeping this zone small keeps it affordable to protect and to assess; we cover how to draw the line in Scoping CUI: How to Shrink Your Compliance Boundary.

5. Management zone

Administrative interfaces for network gear, hypervisors, storage, backup systems and identity infrastructure, reachable only from dedicated administrator workstations or jump hosts. If an attacker cannot reach a management interface, they cannot use a stolen administrator password against it.

6. Guest and IoT

Guest Wi-Fi, cameras, badge readers, smart TVs, building systems and printers that do not need to reach internal servers. These devices are hard to patch and rarely monitored, so they get internet access and little else.

How traffic should flow

  • Deny by default. Firewall rules between zones allow only named flows, such as "user zone to file server on SMB," and everything else is blocked and logged.
  • Administer from one place. Administration happens only from the management zone, never directly from user workstations.
  • Keep backups out of reach. Backup servers sit in the management zone, and backup storage is not reachable from the user or server zones. See Backups That Survive Ransomware.
  • Log the crossings. Allowed and denied traffic between zones goes to central logging, so investigators can trace movement.
  • Separate identity for administrators. Administrators use separate accounts for administration, never their everyday account.

Getting there without a forklift upgrade

Most organizations can segment with the equipment they already own: VLANs on existing switches, with routing between them forced through a firewall. Move in order of value:

  1. Isolate management interfaces. The fastest, highest-value change.
  2. Separate guest and IoT devices. Low risk to operations, immediate reduction in exposure.
  3. Build the sensitive enclave. Move sensitive data and the people who use it into a defined zone.
  4. Split servers from users and tighten rules service by service, using logs to learn what traffic is actually needed.
  5. Block workstation-to-workstation traffic.

Test each change before and after, and document every allowed flow. The documentation becomes part of your system security plan.

Verify it works

A segmentation design is only as good as its enforcement. Have someone try to cross the boundaries from a compromised user workstation, the way an attacker would. A penetration test focused on lateral movement will show whether the rules hold.

How CDT can help

CDT's secure architecture team designs segmentation for contractor networks of every size, and our hardening and penetration testing teams implement and verify it.

Sources

Let's talk

Ready to strengthen your security posture?

Talk with a CDT engineer about your mission, your systems and your deadlines. We'll tell you honestly what it takes.