Skip to main content

Guide

ISMS for telecommunications: Connect networks, services and responsibility

Build a telecommunications ISMS: connect sector rules, central network services, dependencies and recovery traceably.

ISMS for telecommunications: Connect networks, services and responsibility
Julian Köhn
|Read time: 3 minutes

In telecommunications, a small central service can affect many customer connections. An ISMS must look beyond individual devices: which service depends on which control system, location and partner?

Choose one customer service and trace its dependencies. These questions help identify an outage from the customer’s perspective and test an alternative upstream service before relying on it.

Assign sector rules first

For public telecommunications networks and publicly available telecommunications services, section 28 BSIG contains special size rules and distinctions for certain duties. Do not copy general BSIG reporting and risk management provisions as a complete obligation catalogue without checking.

Record the specific activities offered and their regulatory routes. Additional services may require further classification. Include this allocation in the ISMS baseline documentation.

Record the service chain

Choose one customer service and describe access, transport, control, authentication and support. Add power, site access and external upstream services. Supplement the network map with contacts, entry rules and approvals for alternatives.

QuestionWhy it matters
Which component is shared?One outage can affect several services
Who can act on site?Redundancy offers limited help without physical access
Which partner supplies an upstream service?Recovery may sit outside your direct control
What information does support need?Customer communication must match confirmed facts

Fictional case: Control available, access disrupted

A central authentication service runs but is unreachable from one network segment. Server monitoring reports no outage. Test service from affected customers’ perspectives and examine the communication-path dependency.

Record which tests detect the fault and which alternatives actually work. Two lines on an architecture diagram do not demonstrate redundancy.

Connect operations and the ISMS

Changes to network interconnection, upstream services or privileged access must feed into assessment. Use clear review triggers. Incidents additionally need defined decision and communication routes.

Supplier assessment should consider the affected service. An otherwise good partner may still be a difficult-to-replace dependency for a time-critical service.

Measure from the customer perspective, act from operations

A reachable server does not equal a usable telecommunications service. Define the observation that tests service from an affected connection or location. Separate this measurement from individual component health.

ISMS work needs a traceable chain: confirmed impairment, affected service, responsible operations team, treatment and subsequent functional check. Technical measurements can provide a basis. Interpretation must account for the measurement’s reach and limitations.

Challenge an alternative upstream service in practice

Check whether an alternative needs the same handover points, locations or organisational prerequisites. A commercially different source is not automatically a technically independent alternative.

Describe activation too: who may order or switch, which information does the partner need and how is functionality confirmed? Use a bounded service for testing so the evidence’s intended meaning is clear.

Kopexa’s BPMN processes can model these handovers. Measures hold test evidence, while risks and asset dependencies explain significance. For later customer communication, this clarifies which restriction is confirmed and which claim remains unresolved.

Govern traceably with Kopexa

Information assets, other assets, dependencies and BIA form the basis. Measures hold evidence; objectives and KPIs support effectiveness assessment. Software replaces neither network monitoring nor specialist determination of the correct reporting route.

Quick answers

Frequently Asked Questions

Still have a question? Find the answers here.

Does the general NIS2 size threshold apply unchanged to telecommunications?

No. Germany’s BSIG contains specific rules for public telecommunications networks and publicly available services. Check these before applying a blanket SME classification.

Sources

  1. BSIG section 28: Scope — Bundesministerium der Justiz [Accessed ]