Networks, Segmentation and Micro-segmentation

In a flat network every computer sees every server, and one compromised computer is enough to reach everything that matters to the business. We design and build networks divided into trust zones, with clear rules between the zones and isolation for whatever needs to be isolated.

Server and network equipment

Each zone in the network
sees only what it needs

Employees, servers, cameras, production machines and guests each sit in a zone of their own. Traffic between zones passes through the firewall and is checked against rules, so a fault or a breach in one zone has a much harder time spreading across the whole network.

  • VLANs and trust zones by role and risk level
  • Rules between zones: only what is defined gets through (default deny)
  • Isolation of servers, OT, IoT and the guest network

Call +972-3-3801180

Who it’s for

  • Businesses with one flat network

    An office where workstations, servers, printers, cameras and guests are all connected to the same network, and that wants to divide it without stopping work.

  • Factories and OT environments

    Production lines, controllers (PLC) and control systems (SCADA) that are hard to update and need to be isolated from the office network and from the internet.

  • Organizations that hold sensitive data

    Clinics, law and accounting firms and companies that hold databases, and need to show that access to the data is restricted and controlled (access control).

Sound familiar?

These findings come up again and again when we review business networks, and they are what lets a small incident turn into a company-wide outage.

  • Every device in the organization is on the same network and can see every other device
  • The security cameras and the time clock sit on the same network as the file server
  • The guest network is really the same network with a different password
  • An outside supplier gets a VPN with access to the entire network
  • There are no rules between zones, and on the inside “everything is allowed”
  • Nobody can draw the network layout (network diagram) or explain why it’s built that way

What network design and segmentation include

We start by mapping what is connected to the network, and build a division that fits the business and its level of risk.

  • Mapping the existing network

    Identifying the devices, servers and connections, and who talks to whom (traffic flows). Without this map the network can’t be divided safely.

  • VLANs and trust zones

    Dividing the network into zones by role and risk level: employees, servers, management, printing, cameras, OT and guests.

  • Rules between zones

    A firewall policy that defines which traffic is allowed between zones, on the principle of least privilege, with logging of what is blocked.

  • Isolating servers and sensitive systems

    Servers, databases and management interfaces sit in a separate zone, reachable only by those who need them and only for what they need.

  • OT, IoT and the guest network

    Isolating controllers, cameras, time clocks, displays and smart devices, and a guest network that gets internet access only.

  • Identity-based segmentation

    Access to systems by user, group and device health (ZTNA), instead of permission based on location on the network.

  • Micro-segmentation

    Isolation at the level of the server and workload, and an east-west traffic policy that stops one server from reaching a neighboring server when there is no need.

  • Enterprise Wi-Fi

    Separate wireless networks for employees, guests and devices, with enterprise authentication (802.1X) and automatic assignment to the right VLAN.

What we take care of, in detail

Network-level segmentation

  • Segmentation: VLANs, trust zones, micro-segmentation, enterprise Wi-Fi and a guest network
  • Mapping devices, traffic flows and dependencies before any change
  • VLAN and addressing plan by role: employees, servers, management, printing, telephony, cameras, OT and guests
  • Trust zones and firewall rules between zones on the principle of minimum required access (default deny)
  • A separate management network for the management interfaces of switches, firewalls, hosts and iDRAC/iLO
  • OT and IoT isolation: controllers, cameras, time clocks and building management systems (BMS), with no direct access to the internet or the office network
  • A guest network with internet access only and isolation between connected devices (client isolation)

Identity-based segmentation and micro-segmentation

  • ZTNA / Zero Trust: secure access to applications without a classic VPN, based on identity and device health
  • Access to resources by user and group in AD or Entra ID, instead of by IP address
  • 802.1X network authentication and NAC: VLAN assignment by user or device identity
  • Micro-segmentation at the server and workload level: host firewall and policy between virtual machines
  • East-west traffic policy between servers, and blocking management and sharing protocols between workstations (SMB, RDP, WinRM)
  • Supplier access limited to only the system they need, for a set time (just-in-time) and with documentation
  • Logging and monitoring of traffic between zones to detect lateral movement

Firewall, remote access and network operations

  • Firewall / UTM: setup, policy, High Availability
  • Web Filter: web filtering by category and user, exceptions, SSL Inspection, browsing reports
  • IPS / IDS: network-level intrusion detection and prevention, signatures, ATP
  • A uniform security policy for all employees: browsing rules, applications, remote access, central enforcement
  • VPN for employees and between remote sites (site-to-site), with OTP/MFA
  • High Availability for firewalls
  • Enterprise Wi-Fi: managed access points, a separate network for each zone, WPA2/WPA3-Enterprise
  • Diagnosing network faults, disconnections, performance
  • UPS, power monitoring and the server room environment

From the first conversation to an organized routine

  1. 1

    Mapping

    What is connected to the network, who talks to whom and which systems are sensitive.

  2. 2

    Zone design

    Division into trust zones, a table of rules between the zones and a phased migration plan.

  3. 3

    Phased rollout

    Moving one zone at a time, with a monitoring period (monitor mode) before blocking, so work processes don’t stop.

  4. 4

    Ongoing control

    Reviewing rules, checking exceptions and updating the map when something changes.

How segmentation stops an incident before it shuts down the business

Attackers and ransomware usually get in through a single point: an employee’s computer, an unpatched device or a compromised account. The extent of the damage (blast radius) depends on where they can reach from there.

  1. A flat network lets an attacker reach everywhere

    When all devices are on the same network, one compromised computer can scan the organization, connect to servers and reach the backups (lateral movement), and ransomware does exactly that before it encrypts. The result is a shutdown of the entire business, and sometimes also exposure of data that has to be dealt with toward customers and the Privacy Protection Authority. Dividing the network into zones forces every such attempt to pass through the firewall, where it can be blocked and detected.

  2. The difference between segmentation and micro-segmentation

    Segmentation divides the network into large zones, such as employees, servers and guests. Micro-segmentation goes down to the level of the individual server or workload, and ensures that even two servers in the same zone don’t talk to each other unless there is a need. It matters especially for east-west traffic between servers, which the perimeter firewall usually doesn’t see.

  3. Identity-based segmentation

    When people work from home, from the field and from the office, location on the network no longer says much about who is connecting. Identity-based segmentation grants access according to the user, their group and the health of the device. This is the basis of the Zero Trust approach and of ZTNA solutions.

  4. OT and IoT don’t get updated like computers

    A controller on a production line, a camera or a building management system sometimes runs for years on the same firmware, with vulnerabilities that will never be fixed. These devices are protected mainly by isolation: a separate zone, no internet access beyond what is required, and no way to reach the office network from them.

  5. Network separation in standards and regulation

    ISO 27001 includes a dedicated control for segregation of networks, NIST CSF addresses protecting networks from unauthorized access, and the Israel National Cyber Directorate guidelines recommend dividing the network into zones and restricting the traffic between them. The Privacy Protection Regulations (Data Security) require access control to the database systems, and a network where every workstation can reach the database server makes that requirement very hard to meet.

Guide: Office Wi-Fi that stays up: what to check first

Frequently asked questions

About segmentation and network design.

Didn’t find an answer? +972-3-3801180

Not when it’s done gradually. We start by mapping the existing traffic, define rules that allow what is needed, and turn on blocking only after a monitoring period. Each zone is moved separately, with the option to roll back.

Yes, at the right scale. Even in a small office it’s worth separating the workstations, the server, the cameras and the guest network. In many cases this can be done with the existing firewall and switches, if they are managed.

A VLAN divides the network into logical parts, and the firewall decides what is allowed to pass between them. VLANs without rules between them give order but little protection, and rules without a division into zones don’t protect internal traffic. You need both.

It’s the stage where an attacker who has already gotten into one computer tries to move to other computers and servers, gather permissions and reach the data and the backups. Segmentation, least privilege and blocking management protocols between workstations make this stage much harder, and buy time to detect the attack.

Not always. On Windows and Linux servers you can start with the local firewall (host firewall) and a central policy, and virtual environments have built-in capabilities for isolating machines from each other. Large, complex environments have dedicated tools, and we check whether they are worth it.

Because the structure of the network determines whether an incident stays on one workstation or reaches all the servers and backups. A network designed only so that “it works” usually ends up flat. We design the network taking into account the Israel National Cyber Directorate guidelines, ISO 27001 and the requirements of the Privacy Protection Law, so that it works and can hold up under review.

Want to divide your network into zones without stopping work?

Tell us briefly about your business and what concerns you about your IT. We’ll get back to you to understand what you need and suggest a way of working that fits.

Business hours: Sunday to Thursday, 09:00 to 17:00

Existing client? Open a support ticket

Leave your details and we’ll get back to you

Your details are used only to get back to you. Privacy policy

Call +972-3-3801180Get in touch