Cookies on this site. Help us understand what works and improve your experience. Essential cookies keep the site working. With your permission, our visit insights and Google Analytics measure usage, and Google Ads measures advertising. Optional cookies are not required to use the free kit. Change your choice anytime in Cookie settings. Privacy policyCookie policy
Separate networks into segments (users, servers, guests, production) to limit damage.
Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.
Why this control matters
A flat network allows a compromised device or account to reach systems unrelated to its legitimate purpose. Segregation limits that movement by separating groups of users, services and information systems according to risk. The boundary only has value when traffic rules enforce the intended separation; a collection of differently named subnets can still behave as one unrestricted environment.
Common auditor findings to check for
Potential gaps to test in your own environment, not a claim about observed audit frequency.
Guest and corporate networks use different address ranges but permissive routing allows guests to reach internal management interfaces or sensitive services.
Firewall rules accumulate broad temporary exceptions without owners or expiry, undermining the separation described in the network architecture and risk assessment.
Cloud or remote-access paths bypass established network boundaries, and these alternative routes are not included in segmentation testing or change review.
How you can implement it
Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.
Define network zones around information sensitivity, trust and operational purpose rather than organisational convenience alone. Identify the flows required between users, workloads, administrators and external services. Keep a diagram that includes cloud environments, remote access and shared infrastructure dependencies.
Implement explicit traffic rules with accountable service owners and documented business justification. Restrict administrative paths separately where appropriate, and consider the effect of identity-based or application-layer controls alongside network boundaries. Record approved exceptions with a review condition instead of leaving them open-ended.
Test both permitted and prohibited paths using controlled connectivity checks. Include guest access, compromised-user scenarios and alternative routes through shared services. Retain results that show the boundary rejects unwanted traffic, not merely that normal business connections continue to work.
Review rules after architecture changes and on a risk-based schedule. Remove obsolete access, compare deployed configuration with the approved design and investigate unexpected traffic. Link significant changes to testing and rollback arrangements so urgent modifications do not silently flatten the environment.
What an auditor will ask to see
A network-zone model and traffic-flow matrix explaining the trust boundaries, sensitive systems and business justification for connections permitted between separate zones.
Firewall, cloud-policy or equivalent configurations with approved rule owners and exceptions, supported by tests of both authorised connectivity and blocked access paths.
Rule-review and change records demonstrating removal of unnecessary flows, assessment of bypass routes and verification that the deployed segmentation still matches the intended design.
Baseline documents in the kit
These free kit documents help you document or evidence A.8.22. Each one is tailored to your organization when you build your kit.
Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.
For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.
Get these documents tailored to your organization
109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.