Exam objective 2.3 asks you to describe secure network design and segmentation. This concept solves the problem of organising a network so that if one part gets attacked, the rest stays safe – it's the difference between a single house with one lock and a secure apartment building with multiple layers of security. For someone studying 350-701, this is foundational because every security technology you'll learn later (firewalls, VPNs, access control) relies on a well-designed, segmented network to work effectively.
Jump to a section
A simple way to picture Secure Network Design and Segmentation
Why do office buildings have a reception desk, a security guard in the lobby, and then locked doors on every floor and office, rather than just one big unlocked door at the street? That's the same problem Secure Network Design and Segmentation solves for a computer network. The reception desk is your first line of defence – it checks badges and asks who you're visiting. The security guard at the elevator is like a firewall that only lets you go to the floor you're allowed on. The locked doors on each office are like VLANs and subnets that keep the Finance team's data separate from Marketing's. Without this layered system, anyone who got past the front door could wander into the CEO's office or the server room. That's a network with no segmentation – a flat network. By dividing the building into secure zones, you limit how far an unauthorised person can go. If a visitor somehow gets past the receptionist, they still can't get to the server room because they need a special key card. In networking, segmentation means splitting the network into smaller parts, each with its own security rules. This stops a single breach from becoming a total disaster, because the intruder is trapped in one zone, just like a visitor stuck in the lobby.
Secure network design and segmentation is the practice of dividing a computer network into smaller, isolated sections to control traffic flow and limit the damage of a security breach. Think of a flat network – one where every device can talk directly to every other device – like a single-room house where an intruder can see everything at once. Segmentation breaks that house into separate rooms with locked doors, so an attacker breaking into the living room cannot automatically access the bedroom safe. This is critical because modern networks are huge, connecting thousands of devices like servers, laptops, printers, and IoT gadgets. Without segmentation, a single infected laptop could spread malware across the entire organisation in minutes.
At the heart of segmentation are a few key technologies. A Virtual Local Area Network (VLAN) is a logical grouping of devices that behave as if they are on their own separate physical network, even if they share the same switch. For example, all computers in the HR department can be on VLAN 10, and all computers in Engineering on VLAN 20. Traffic between VLANs must go through a device called a router or a firewall, which inspects the traffic and decides whether to allow it. This is where a firewall, a device that permits or blocks network traffic based on security rules, comes in. A firewall can be configured to allow only specific types of traffic between VLANs – for instance, allowing HR to access a shared database server but blocking Engineering from doing so.
A subnet, or subnetwork, is a more fundamental way to divide an IP network. Whereas VLANs are a layer-2 concept (they handle local network addressing), subnets are a layer-3 concept (they handle IP addresses). In practice, VLANs and subnets are often paired: each VLAN gets its own subnet. For example, VLAN 10 might use the subnet 192.168.10.0/24, which can host up to 254 devices. Segmentation also relies on Access Control Lists (ACLs), which are sets of rules applied to routers or firewalls that specify which traffic is permitted or denied based on source IP, destination IP, port numbers, and protocol. A common ACL rule might say 'allow traffic from the Finance subnet to the accounting server on port 1433 (SQL) but deny all other traffic.'
Secure network design also introduces the concept of zones. A zone is a collection of network segments with similar security requirements. Typical zones include a trusted zone (internal corporate network), an untrusted zone (the internet), a demilitarised zone (DMZ) for public-facing servers like web servers, and a guest zone for visitors' Wi-Fi. The DMZ is particularly important – it is a buffer zone that sits between the internal network and the internet. Servers in the DMZ are accessible from the internet but cannot initiate connections into the internal network, which prevents an attacker who compromises a web server from directly attacking internal databases.
Why does this matter for the 350-701 exam? The Cisco SCOR exam tests your understanding of how to design a network using these concepts to achieve defence in depth – a layered security strategy. You need to know the difference between east-west traffic (traffic between devices within the same data centre or segment) and north-south traffic (traffic entering or leaving the network). Most security policies focus on north-south traffic, but modern segmentation places equal emphasis on east-west traffic because attackers often move laterally once inside. Technologies like microsegmentation take this further by applying security rules to individual workloads, even within the same VLAN, often using software-defined networking (SDN) or virtual firewalls.
The exam also expects you to recognise that segmentation is not just about technology but about policy. You start by identifying assets (what needs protecting), classifying data sensitivity, and then mapping traffic flows. A typical design follows the 'least privilege' principle: every segment only has access to the specific resources it needs to function. This is often documented using a network diagram with clear labels for each zone, VLAN, and firewall rule. Finally, you must understand that segmentation can be implemented at multiple layers:
Physical segmentation: separate cables and switches for different departments (rare now due to cost).
Logical segmentation: using VLANs on shared switches.
Virtual segmentation: using virtual LANs in hypervisors for virtual machines.
Firewall-based segmentation: using next-generation firewalls (NGFWs) to filter traffic between zones.
The 350-701 exam will ask you to select the appropriate segmentation method for a given scenario, identify the correct placement of firewalls, and understand how segmentation prevents threats like ransomware propagation. You must also know that a well-segmented network makes compliance with regulations like GDPR or HIPAA easier because sensitive data is isolated and more easily monitored.
Asset Identification and Classification
First, list every device, server, and data store on the network. Classify each item by sensitivity (e.g., public, internal, confidential, restricted). This step matters because segmentation policies are built around protecting the most sensitive assets first.
Traffic Flow Mapping
Map out how users and applications communicate between assets. For example, does the HR application need to talk to the payroll database? This reveals which connections are necessary and which are unnecessary, so you can design firewall rules that allow only legitimate traffic.
Zone Design
Define security zones based on trust levels. Typical zones include untrusted (internet), DMZ (public servers), trusted (internal users), and restricted (high-value assets like financial databases). Each zone gets a specific security policy, which reduces complexity compared to having many individual rules.
VLAN and Subnet Allocation
Assign each zone one or more VLANs and corresponding subnets. For example, the trusted zone might use VLAN 10 with subnet 10.0.10.0/24. This step creates the logical separation that prevents devices in different zones from communicating directly at layer 2.
Firewall Rule Implementation
Install a firewall between zones and write ACLs that permit only necessary traffic. For example, allow port 443 from the DMZ web server to the internet, but block all traffic from the DMZ to the trusted zone. Test that the rules work as expected.
Microsegmentation for Critical Workloads
For the most sensitive servers, apply microsegmentation using virtual firewalls or host-based firewalls. For instance, allow only the specific application server to talk to the database on a particular port, blocking all other traffic even within the same VLAN.
An IT professional responsible for network security typically starts by gathering requirements from the business. For example, a mid-sized company with 500 employees wants to secure its network after a recent ransomware attack in the news. The IT professional's first step is to interview department heads to understand what data each department handles. The finance team manages payroll and bank details, HR holds personal employee records, research and development has intellectual property, and the sales team uses a customer relationship management (CRM) tool hosted in the cloud. The IT professional then creates a network segmentation plan.
Step by step, the IT professional does the following:
Conducts a risk assessment to identify the most sensitive assets. The finance server and HR database are classified as high-sensitivity, requiring the strictest segmentation. The sales CRM is already in the cloud, so it needs secure access but no internal hosting.
Designs a logical network map with VLANs. Finance gets VLAN 10 (subnet 10.0.10.0/24), HR gets VLAN 20 (10.0.20.0/24), R&D gets VLAN 30 (10.0.30.0/24), and guest Wi-Fi gets VLAN 100 (10.0.100.0/24) with internet-only access.
Configures a next-generation firewall (NGFW) as the core router between VLANs. The NGFW is programmed with ACLs that permit only necessary ports. For example, Finance can access HR's payroll application only on TCP port 443, but HR cannot initiate connections to R&D. All traffic between VLANs is inspected by the firewall, which also runs intrusion prevention systems (IPS) to detect malicious traffic.
Sets up a DMZ for the company's public-facing web server. The web server sits in VLAN 50 (10.0.50.0/24). The firewall rule allows inbound HTTPS from the internet to the web server but blocks the web server from initiating any connections to the internal VLANs. If an attacker exploits a vulnerability in the web server, they cannot reach the finance database.
Implements microsegmentation inside the data centre. The finance database server runs on a virtual machine. The IT professional creates a firewall rule that only the finance application server (in a different VM) can communicate with the database on port 1433. Even if another VM on the same physical host is compromised, it cannot connect to the database because the virtual firewall enforces the rule at the hypervisor level.
Deploys network access control (NAC) for employee devices. When an employee plugs a laptop into the network, the NAC system checks if the device has up-to-date antivirus software and the latest patches. If not, the device is placed into a remediation VLAN with limited access until it is compliant.
Tests the segmentation by running penetration tests against each zone. The IT professional uses a laptop on the guest VLAN and attempts to ping the finance server – the ping should be blocked. They also simulate a worm spreading from a compromised R&D workstation to HR – the firewall should block the lateral movement.
Monitors traffic continuously using a Security Information and Event Management (SIEM) system that collects logs from the firewall. If a sudden spike in traffic from HR to Finance occurs during non-business hours, the SIEM alerts the security team.
Documents everything in a network diagram and a security policy document. The diagram shows each VLAN, the firewall placement, and the DMZ. The policy states that any new device or service must go through a change management process that updates the segmentation rules.
In a real-world scenario, the IT professional also faces challenges like dealing with legacy systems that cannot be moved to new VLANs, or employees who demand open access between departments. The professional must balance security with usability, often by implementing jump servers – locked-down computers that allow authorised administrators to access high-security segments from a less secure network. This real-world process demonstrates that segmentation is not a one-time project but an ongoing cycle of assessment, design, implementation, and monitoring, which directly maps to the concepts tested in the 350-701 exam.
The 350-701 exam tests Secure Network Design and Segmentation in several specific ways. You will encounter multiple-choice questions, drag-and-drop ordering tasks, and scenario-based questions that ask you to select the best segmentation design for a given business requirement. The exam is relentless about precision, so knowing the exact definitions and distinctions is critical.
Key exam topics include:
VLAN vs Subnet: The exam may ask when to use a VLAN versus a subnet. Remember: VLANs are layer-2 constructs that isolate broadcast domains; subnets are layer-3 constructs for IP addressing. In practice, they work together, but the exam loves to test the conceptual difference.
Zone concepts: You must memorise the three primary zones – trusted, untrusted, and DMZ – plus variations like guest, management, and VPN zones. A common question shows a network diagram and asks where to place a public web server. The correct answer is always the DMZ. Another trap: placing the web server in the trusted zone is wrong because it exposes the internal network.
Firewall placement: Questions often describe a network with multiple segments and ask where to put a firewall. The answer is at the boundary between each zone, especially between the DMZ and the trusted zone. A firewall that sits only at the internet edge fails to protect east-west traffic.
ACLs: You may be given a scenario with a specific traffic flow (e.g., 'allow only HTTPS traffic from the Guest VLAN to the internet') and asked to choose the correct ACL rule. The exam expects you to understand the implicit denny at the end of every ACL, and that ACLs are processed top-down. A common trap is including an ACL that allows more traffic than necessary (e.g., allowing all TCP instead of just port 443).
East-west vs north-south traffic: The exam wants you to know that traditional firewalls focus on north-south (internet-bound) traffic, but modern segmentation must also handle east-west (internal) traffic. Microsegmentation is the solution for east-west traffic, and the exam may ask which technology enables microsegmentation (answer: software-defined networking or virtual firewalls).
Defence in depth: Multiple-choice questions often describe a flat network and ask which threat it is vulnerable to. The answer is lateral movement of malware or a single breach leading to total compromise. The correct design choice is to implement segmentation with VLANs and firewalls.
Traps to watch out for:
Confusing VLANs with VPNs. VPNs create encrypted tunnels over an untrusted network; VLANs create logical segments within a switched network. They are not the same.
Believing that a router alone provides segmentation. Routers can forward traffic between subnets, but they do not inspect traffic security. A firewall is required for security segmentation.
Assuming that placing a firewall between the internet and the internal network is sufficient. The exam emphasises that internal segmentation between high-value assets is equally important.
Misunderstanding the DMZ. Some questions paint the DMZ as a place for internal servers; that is incorrect. The DMZ is for servers accessed from the internet. Internal servers belong in the trusted zone.
Overlooking the 'least privilege' principle. The correct answer in a design question always restricts access to only what is necessary. Any answer that allows broad access (e.g., 'allow all traffic between HR and Finance') is wrong.
To prepare, focus on Cisco's own documentation for Campus LAN design and the Cisco SAFE model. Practice drawing network diagrams for different business scenarios: e.g., a hospital with patient records, a bank with trading servers, a university with student and faculty networks. For each, identify the zones, VLANs, and firewall rules. Finally, memorise the fact that the 350-701 exam considers segmentation as a foundation for all other security controls – if you get the segmentation wrong, every other control is weakened.
Segmentation divides a network into smaller zones to limit the spread of an attack, preventing a single breach from compromising the entire organisation.
A VLAN is a logical grouping of devices that isolates broadcast traffic at layer 2, but it does not provide security filtering without a firewall.
A DMZ is a buffer zone between the internet and the internal network where public-facing servers reside, with firewall rules that block inbound traffic from the DMZ to the trusted zone.
Microsegmentation enforces security policies at the individual workload level, even within the same VLAN, using virtual firewalls or software-defined networking.
The principle of least privilege dictates that each segment should only have access to the specific resources it needs to function, minimising lateral movement opportunities.
Defence in depth means layering multiple security controls – VLANs, firewalls, ACLs, and intrusion prevention – so that if one layer fails, others still protect the network.
These come up on the exam all the time. Here's how to tell them apart.
VLAN
Operates at layer 2 of the OSI model.
Isolates broadcast domains within a switch.
Uses VLAN IDs (1-4094) to group devices logically.
Subnet
Operates at layer 3 of the OSI model.
Isolates IP address ranges for routing.
Uses CIDR notation (e.g., 10.0.1.0/24) to define hosts.
DMZ
Contains public-facing servers accessible from the internet.
Has firewall rules that block inbound traffic to the internal network.
Considered a semi-trusted or untrusted zone with limited privileges.
Trusted Zone
Contains internal user workstations and private servers.
Has firewall rules that allow outbound connections to the internet but restrict inbound connections from the DMZ.
Considered a trusted zone with higher security privileges.
North-South Traffic
Traffic entering or leaving the network perimeter.
Historically the main focus of firewall security.
Typically inspected by edge firewalls.
East-West Traffic
Traffic flowing between devices within the same data centre or network.
Critical for lateral movement of attackers after a breach.
Requires microsegmentation or internal firewalls to control.
Physical Segmentation
Uses separate switches, routers, and cables for each network zone.
Provides absolute isolation with no risk of VLAN hopping or misconfiguration.
Expensive and difficult to scale because hardware cannot be shared.
Logical Segmentation
Uses VLANs, subnets, and firewalls on shared hardware.
Offers flexibility and lower cost but depends on correct configuration to prevent bypass.
Easier to scale and change by modifying software configs rather than swapping hardware.
Mistake
VLANs are enough for complete security; you don't need a firewall between them.
Correct
VLANs isolate broadcast domains but do not inspect or filter traffic. A firewall is required to enforce security policies between VLANs.
Many beginners assume VLANs provide security because they create separate networks, but VLANs are a layer-2 technology that can be bypassed by techniques like VLAN hopping.
Mistake
A DMZ is just a less secure part of the internal network where you put any server.
Correct
The DMZ is a separate zone with strict firewall rules: servers there are accessible from the internet, but they cannot initiate connections to the internal (trusted) network.
The term 'demilitarised zone' sounds like a neutral area, so people think it's a middle ground without understanding the directional traffic restrictions.
Mistake
Segmentation only matters for large enterprise networks; small businesses don't need it.
Correct
Any network with more than a few devices benefits from segmentation to contain threats, and small businesses are frequent targets because they often have flat networks.
People think security is only for big companies, but simple segmentation using VLANs on a cheap managed switch is accessible and effective for small networks.
Mistake
Subnetting and segmentation are the exact same thing.
Correct
Subnetting is an IP addressing technique that divides a network into smaller address ranges, while segmentation is a broader security concept that uses subnets, VLANs, firewalls, and ACLs to control traffic flow.
Both terms involve dividing a network, so beginners conflate them. Subnetting is a tool for segmentation, not a synonym.
Mistake
Once you set up VLANs and firewall rules, you never need to change the segmentation design.
Correct
Segmentation must be reviewed and updated regularly as business requirements change, new applications are deployed, and threats evolve.
It feels like an engineering task that is 'done' after initial configuration, but dynamic environments require ongoing adjustments.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A VLAN is a logical grouping at layer 2 that isolates broadcast traffic on a switch, while a subnet is an IP address range at layer 3. They are often used together, but a VLAN can span multiple subnets and vice versa.
A DMZ is a separate network zone that isolates public-facing servers from your internal network. Even with a firewall, putting a public web server directly on the internal network exposes it to attacks. The DMZ ensures that if the server is compromised, the attacker cannot reach internal assets.
A router can forward traffic between subnets, but it does not inspect traffic for security threats or enforce granular rules. A firewall is required for security segmentation because it can block or allow traffic based on application, user identity, and threat intelligence.
East-west traffic is data flow between devices within the same data centre or network zone, such as between application servers and databases. It matters because attackers who breach one device often move laterally using east-west traffic, so segmentation must control that traffic, not just north-south (internet-facing) traffic.
You can use VLANs on a managed switch and a low-cost or open-source firewall (like pfSense). For small networks, even a consumer router that supports VLANs and basic ACLs can provide decent segmentation.
Physical segmentation uses separate switches and cables for each network zone, which is expensive but completely isolates traffic. Logical segmentation uses VLANs and firewalls on shared hardware, which is cheaper and more flexible but relies on proper configuration to avoid bypass attacks.
You've finished Secure Network Design and Segmentation. Continue through the 350-701 study guide to build a complete picture of the exam.
Done with this chapter?