What this policy is
The umbrella policy for network-layer security — segmentation strategy, perimeter controls, encryption-in-transit standards, remote-access (VPN/ZTNA) rules, and DNS / mail-flow protections.
Why every organization needs one
Modern attackers move laterally fast once they're inside. Network architecture decisions — written down and enforced — are the difference between containment and total compromise.
What a competent Network Security Policy typically contains
- Purpose and scope
- Roles and responsibilities
- Definitions
- Segmentation model (zones, micro-segments)
- Perimeter-control standards
- Encryption-in-transit minimum (TLS 1.2+, etc.)
- Remote-access pattern (VPN vs ZTNA)
- Review cadence (typically annual) and version control
- Approval, sign-off and effective date
How iCompaas tracks this policy
The icompaas policy-doc producer manages this document through an 8-state lifecycle: draft → generated → internal_qa → customer_review → in_review → approved → signed (with rejected as a terminal side-state). The producer publishes a policy_doc_network_security_policy_signed compliance finding once at least one document of this kind reaches the signed state for the account being assessed; the finding then rolls up into every compliance framework that references this policy (see the table below).
Compliance frameworks that reference this policy
The icompaas compliance controls library links every policy document to the controls in each framework that require, evidence, or otherwise rely on it. Below: every control across every framework in the iCompaas catalogue that names this policy as part of its evidence base. Each control links to its own dedicated page with auditor-view content + implementation guidance.
| Framework | Control | Title | Component |
|---|---|---|---|
| ISO/IEC 27001:2022 | A.5.23 | Information security for use of cloud services | Organizational controls |
| ISO/IEC 27001:2022 | A.8.21 | Security of network services | Technological controls |
2 controls across 1 framework reference this policy.
About this page
This article is part of the iCompaas Policy Documents library — one page per signed-document type the icompaas policy-doc producer tracks for customer accounts. The article is intentionally framework-agnostic: a customer signing a policy of this kind gets the same regulatory benefit across every framework that references it.