How to Segment Your Network So Underwriters Credit It: A Nine-Step Playbook
Underwriters no longer take "yes, we segment" on trust. Here's a nine-step sequence for segmenting flat networks, backups, OT and admin tiers, plus the evidence that earns credit at renewal.
What Underwriters Mean When They Ask About Segmentation
If your renewal questionnaire asks whether your network is segmented and your honest answer is "partly," you have a pricing problem and possibly a coverage problem. Carriers and MGAs treat segmentation as a ransomware-severity control. It doesn't stop the first compromised laptop. It decides whether that laptop becomes a business-wide encryption event or a contained incident at one site.
Network segmentation requirements for cyber insurance usually come down to four questions, whatever the carrier or country:
- Is the user network separated from servers and critical systems, with east-west traffic restricted rather than open?
- Are backups isolated so that domain credentials and production hosts can't reach or delete them?
- Is operational technology (OT) separated from IT, if you run plants, warehouses, labs or building systems?
- Are privileged accounts tiered so domain admin credentials never touch ordinary workstations?
Four yeses with no evidence behind them earn little credit. Underwriters ask follow-up questions, may run external scans and, after a claim, can compare what you attested with what forensic investigators find. A misrepresentation in the application can give the insurer grounds to dispute coverage or, in some jurisdictions, rescind it. The rules differ between, say, England, Germany, India and the Gulf states, so have your broker or coverage counsel review material answers.
The nine steps below run in the order that cuts risk fastest while building your evidence file as you go.
Steps One to Three: Map the Flat Network and Choke Lateral Movement
Step 1: Inventory assets and real traffic flows
You can't segment what you haven't mapped. Pull an asset inventory from your EDR, CMDB or network access control tool, then capture actual flows over two to four weeks using firewall logs, NetFlow or a flow-visibility tool. Tag each asset by function: user endpoints, servers, identity infrastructure, backup, OT, guest/IoT, third-party access. Skip this and you'll likely break a payroll integration nobody documented.
Step 2: Define zones around crown jewels
Keep the first design coarse. Six to ten zones is plenty for most mid-size companies: users, general servers, identity (domain controllers, PKI, identity provider connectors), backup, management, OT, DMZ and guest. Write down the allowed flows between each pair of zones. That flow matrix becomes your most valuable evidence document.
Step 3: Apply lateral movement controls before full segmentation
Ransomware operators spread over a few familiar protocols: SMB, RDP, WinRM, WMI and remote PowerShell. Host firewall policy pushed through Group Policy or your endpoint manager can block most workstation-to-workstation traffic in days, long before any VLAN redesign finishes. Restrict RDP and SMB on servers so they're reachable only from designated jump hosts. These controls are cheap, quick and carry real weight with underwriters. If you complete only one step before renewal, make it this one.
Steps Four to Six: Backups, Admin Tiers and OT
Step 4: Build backup network isolation
Underwriters probe backups hard because attackers who delete them first leave victims with nothing to restore. Isolation means backup servers and repositories sit in their own zone, are managed with accounts that don't exist in the production domain, and accept only the ports your backup software needs. Add immutable or offline copies: object-lock storage, hardened Linux repositories or a vaulted cloud service. Veeam, Rubrik, Cohesity and Commvault all support immutability. The underwriter's real question is whether it's switched on and separately administered.
Step 5: Implement a tiered admin model
A tiered model splits privileged access into layers: Tier 0 for identity systems, Tier 1 for servers and applications, Tier 2 for workstations. Credentials from a higher tier never log on to a lower one. In practice that means separate admin accounts, privileged access workstations or hardened jump hosts for Tier 0, and logon restrictions enforced by policy. Microsoft's enterprise access model is the common reference, and the same principle applies to Entra ID, Okta and cloud consoles. Add MFA on every admin path; carriers often treat that as a hard requirement.
Step 6: Separate OT from IT
For manufacturers, logistics operators, utilities and hospitals, OT/IT segmentation often drives the premium conversation. The baseline is an industrial DMZ between corporate IT and plant networks, no direct internet access from control systems, and vendor remote access brokered through a monitored jump service rather than always-on VPNs or remote-desktop tools installed on HMIs. IEC 62443 zones and conduits give you an internationally recognized vocabulary for carriers in different regions. Operators in scope for the EU's NIS2, or following national frameworks in places like Saudi Arabia, Singapore or Australia, will often find regulatory expectations overlap with what underwriters ask, though you should confirm the specifics locally.
Steps Seven to Nine: Build the Evidence File
Step 7: Produce current, dated network diagrams
Two diagrams are enough: a logical zone diagram showing the allowed flow matrix, and a backup and recovery architecture diagram. Date them, assign an owner, and make sure they match reality. A diagram showing an OT DMZ your plant doesn't have is worse than no diagram.
Step 8: Run and document a firewall rule review
Review internal firewall and microsegmentation rules at least twice a year. Hunt for any-any rules, stale temporary exceptions and broad vendor rules. Record how many rules you reviewed, removed and justified, and who signed off. AlgoSec, Tufin and FireMon automate this at scale; smaller estates can manage with a structured spreadsheet export.
Step 9: Test that segmentation actually holds
Commission an internal penetration test or assumed-breach exercise focused on lateral movement. Start from a standard user workstation and try to reach domain controllers, backup consoles and OT. Breach-and-attack simulation tools can re-run those checks continuously. Keep the report, remediation tracker and retest results together.
| Workstream | Typical timeline | Indicative cost (2026, USD) | Main cost drivers |
|---|---|---|---|
| Lateral movement host-firewall policy | 2–6 weeks | Mostly internal effort; roughly $5k–$25k with a consultant | Endpoint count, legacy apps |
| Backup isolation and immutability | 4–10 weeks | $15k–$120k | Data volume, storage choice, licensing |
| Tiered admin model | 2–6 months | $20k–$150k | AD complexity, PAM tooling, cloud tenants |
| OT/IT segmentation per site | 3–9 months | $30k–$250k+ per site | Site count, downtime windows, legacy controllers |
| Microsegmentation platform | 3–12 months | Wide range; often tens of dollars per workload per year | Workload count, agent vs. agentless |
| Lateral-movement pen test | 2–4 weeks | $15k–$60k | Scope, number of sites, retest |
These are typical 2026 market ranges. Prices vary widely by contract and region, so confirm with vendors and local integrators.
Turning the Work Into Questionnaire Answers and Better Terms
Evidence only pays off if it shapes how the underwriter reads your risk. Don't stop at ticking "yes." Give your broker a two-page segmentation summary: zones in place, backup isolation design, admin tiering status, OT separation by site, the date of the last rule review and the headline results of the latest test. Where something is partial, say so and attach a dated remediation plan. A credible plan generally reads better to an underwriter than a vague yes that collapses on follow-up.
Check your own answers for these red flags before the underwriter does:
- Backup consoles joined to the production domain or reachable from user subnets.
- Domain admins logging on to everyday laptops, even occasionally.
- VLANs with no access control between them. That's separation on paper only.
- Vendor remote access straight into OT or server zones.
- Pen test findings on lateral movement marked "accepted risk" with no compensating control.
What good segmentation earns varies by carrier and market: possibly better pricing or retentions, fewer ransomware exclusions or sublimits, and fewer binding conditions. Nobody can promise a specific discount, so ask your broker to present your evidence pack to several markets and compare terms.
The decision rule: if renewal is under 90 days away, finish Steps 3 and 4 and document both. With six months, add admin tiering and the lateral-movement test. Everything else goes into the dated plan you hand the underwriter.
Questions buyers ask
Is VLAN separation enough to answer yes on a segmentation question?
Usually not by itself. Underwriters care whether traffic between segments is actually filtered by a firewall, ACL or microsegmentation policy. VLANs that route freely to each other give little protection against lateral movement, so document the enforcement points and the allowed-flow rules.
Do we need a microsegmentation platform to get underwriting credit?
No. Most carriers accept well-documented zone-based segmentation with internal firewalls plus host firewall policy blocking workstation-to-workstation traffic. Tools such as Illumio, Akamai Guardicore or Zero Networks help in large or dynamic estates, but they're one way to get there, not something carriers typically require.
What counts as isolated backups for insurance purposes?
In general: backups held in a separate network zone, managed with credentials outside the production domain, and at least one copy that is immutable or offline. Insurers often ask whether a compromised domain admin could delete the backups. If the honest answer is yes, the backups aren't isolated.
How does a tiered admin model differ from just using MFA for admins?
MFA protects the login. Tiering controls where privileged credentials may be used at all. Without tiering, an attacker on a compromised workstation can still harvest a domain admin's session or token after MFA has been passed. Carriers often ask about both.
We have no OT. Do segmentation questions still apply?
Yes. The user, server, identity and backup separation questions apply to almost every business, and many carriers also ask about guest, IoT and building-management networks. Mark the OT section not applicable, but expect the other answers to be weighed heavily.
Should we share our pen test report with the insurer?
Generally a summary works better than the full report. Give the scope, date, key lateral-movement findings and remediation status. Full reports can contain sensitive detail, and handling varies by insurer and jurisdiction, so agree the format with your broker and, for material disclosures, your legal adviser.
Written by the Armorinsurecorp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.