A.8 Technological controls

A.8.21 Security of network services

Not mandatory by default – decided in your SoA

What it means in plain language

Define and apply security mechanisms, service levels and requirements for network services, whether in-house or outsourced.

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

Security of network services depends on more than a working connection; it requires agreed security mechanisms, measurable service expectations, and a clear split between the organization and the provider. Teams can describe how ISP links, managed DNS, VPN, DDoS protection, and inter-site circuits are assessed and monitored. It also supports evidence that service security obligations are understood before reliance is placed on them.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Network service agreements exist, but they do not state security commitments such as encryption, availability targets, incident notification, or log retention.
  • The organization relies on supplier-managed connectivity without checking whether configuration changes, maintenance windows, or support contacts are controlled.
  • Service reviews do not compare promised protections with actual performance, so gaps in resilience or incident handling remain unchallenged.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Document each network service with its purpose, provider, security features, service levels, dependencies, and customer responsibilities. Include in-house and outsourced services alike, because the control applies to both. Where traffic crosses public or third-party infrastructure, record whether encryption, authenticated management, filtering, or redundancy is required and who owns each setting.
  • Build security clauses into procurement and change workflows: incident notification time, support availability, maintenance notice, configuration approval, subcontractor visibility, and evidence of testing after changes. The supplier relationship owner or service manager should review these terms before renewal, service extension, or major topology change.
  • Monitor service behavior against agreed criteria, not just uptime. Track failed connection attempts, latency spikes, certificate or tunnel errors, maintenance overruns, and abuse events such as DDoS or route anomalies. Escalate deviations through incident or supplier management, and record whether the provider supplied root-cause detail and remediation commitments.
  • Retain practical records showing the service is controlled: signed contract schedules, SLA or SLO extracts, architecture diagrams, support contact lists, quarterly review notes, and evidence of approved encrypted site-to-site links or protected public services. When service changes occur, note the business impact assessment, implementation date, and post-change validation outcome.

What an auditor will ask to see

  • Network Security Policy or procedure section listing required security mechanisms for each service type.
  • Supplier agreement or service schedule showing availability, incident notification, and change notification commitments.
  • Quarterly service review with metrics, open issues, and follow-up actions for the network provider.
  • Configuration evidence for encrypted tunnels, DNS protections, or DDoS controls on public-facing services.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.21. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.5.20 — Addressing information security within supplier agreements and A.5.22 — Monitoring, review and change management of supplier services. Keep the ownership and evidence consistent across these activities.

Required information and the kit’s 19-document core for the wider implementation context.

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.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.