Telekommunikationsgesetz (TKG), Section 165 Technical and Organisational Protective Measures
TKG § 165, Technische und organisatorische Schutzmaßnahmen
In force since .
A sector security regimes rule binding public and private bodies.
- Private right of action
- No
- Obligation class
- Security, Governance
As of .
What it requires
- If you provide telecommunications services or contribute to them, take appropriate technical precautions and other measures, taking the state of the art into account, to protect the secrecy of telecommunications and against personal-data breaches (Section 165(1)).NIST CSF 2.0PR.DS-02
- If you operate a public telecommunications network or provide a publicly available telecommunications service, take appropriate technical and organisational measures against disruptions that significantly impair networks and services and to control the risks to their security, including encryption where appropriate and measures that secure systems against unauthorised access and limit the effects of security breaches (Section 165(2)).NIST CSF 2.0PR.IR-01
- If you are an essential or important entity under Section 28 of the BSI Act, base those measures on an all-hazards approach that covers at least risk analysis and security concepts, incident handling, business continuity, supply-chain security, security in acquisition, development and maintenance including vulnerability management and disclosure, effectiveness assessment, basic cyber hygiene and training, cryptography, personnel security and access control, and multi-factor or continuous authentication (Section 165(2a)); have your management implement and monitor them and take part in regular training (Section 165(2b) and (2d)).NIST CSF 2.0GV.PO-01NIST CSF 2.0GV.RR-01
- If you operate a public network or provide a public service with increased hazard potential, use attack-detection systems that capture and evaluate threats continuously and automatically (Section 165(3)); as a network operator, use critical components only after a recognised certification body has examined and certified them (Section 165(4)), and undergo a review by a qualified independent body or competent national authority every two years, sending a copy of the report to the Bundesnetzagentur and the BSI and bearing the cost (Section 165(9)).NIST CSF 2.0DE.CM-01NIST CSF 2.0ID.RA-09
- If you operate a public telecommunications network, take measures to keep it operating properly and its services continuously available (Section 165(5)).NIST CSF 2.0PR.IR-03
These lines are LexLint's reading of the law's text, as of . Also read by: Bundesnetzagentur (Federal Network Agency), catalogue of security requirements under Section 167 TKG (guidance, recorded ).
In the frameworks
- NIST Privacy Framework
- PR.PO-P7Response plans (Incident Response and Business Continuity) and recovery plans (Incident Recovery and Disaster Recovery) are established, in place, and managed.
- PR.DS-P5Protections against data leaks are implemented.
- PR.PT-P4Mechanisms (e.g., failsafe, load balancing, hot swap) are implemented to achieve resilience requirements in normal and adverse situations.
- NIST CSF 2.0
- GV.RR-01Organizational leadership is responsible and accountable for cybersecurity risk and fosters a culture that is risk-aware, ethical, and continually improving
- GV.PO-01Policy for managing cybersecurity risks is established based on organizational context, cybersecurity strategy, and priorities and is communicated and enforced
- ID.RA-09The authenticity and integrity of hardware and software are assessed prior to acquisition and use
- PR.DS-02The confidentiality, integrity, and availability of data-in-transit are protected
- PR.IR-01Networks and environments are protected from unauthorized logical access and usage
- PR.IR-03Mechanisms are implemented to achieve resilience requirements in normal and adverse situations
1 more
- DE.CM-01Networks and network services are monitored to find potentially adverse events
- CIS Controls
- 3.2A maintained catalogue of the sensitive data the enterprise holds and where it sits.
- 3.10Encryption of sensitive data as it crosses networks.
- 3.11Encryption of sensitive data where it is stored on servers and applications.
- 6.8Access rights defined by job role, and kept up to date.
- 7.1A documented, reviewed approach to finding and handling weaknesses.
- 8.2Turning on and gathering logs from the enterprise's systems.
- FINOS AIGF
- AIR-PREV-005System Acceptance Testing
- AIR-PREV-006Data Quality & Classification/Sensitivity
- AIR-PREV-007Legal and Contractual Frameworks for AI Systems
- AIR-PREV-008Quality of Service (QoS) and DDoS Prevention for AI Systems
- AIR-PREV-012Role-Based Access Control for AI Data
- AIR-PREV-014Encryption of AI Data at Rest
7 more
- AIR-PREV-017AI Firewall Implementation and Management
- AIR-PREV-020MCP Server Security Governance
- AIR-PREV-024Human-in-the-Loop Action Approval Gate
- AIR-DET-001AI Data Leakage Prevention and Detection
- AIR-DET-004AI System Observability
- AIR-DET-011Human Feedback Loop for AI Systems
- AIR-DET-021Agent Decision Audit and Explainability
- ENISA NIS2 guidance
Our reading of where this law's duties sit in each framework, and in the NIST CSF 2.0, line by line beside each duty above. It never says that running a control meets the law. How we read a framework against the law
CIS Critical Security Controls® (CIS Controls®) v8.1 © Center for Internet Security, Inc. Safeguard numbers are used under a CIS Controls Supporter License; the one-line descriptions beside them are our own, not CIS text.
Who enforces it
Enforcement body
Bundesnetzagentur, which can order measures to remedy a security incident or avert a danger and can order a review under Section 165(8) and (9).
Settledness
A revised draft catalogue (Version 2025-10) was open for comment until ; it is a draft and is not recorded as guidance.
- As of
- Guidance link
- https://www.bundesnetzagentur.de/DE/Fachthemen/Telekommunikation/OeffentlicheSicherheit/KatalogSicherheitsanforderungen/start.html
- Guidance body
- Bundesnetzagentur (Federal Network Agency), catalogue of security requirements under Section 167 TKG
- Open questions
- Does the catalogue of security requirements of , which the Bundesnetzagentur still treats as valid ('aktuell noch gültig'), satisfy the ten categories of measures that Section 165(2a) TKG requires of an essential or important entity until a revised catalogue replaces it?
What this law does
Section 165(1) of the Telekommunikationsgesetz (TKG) requires anyone who provides telecommunications services or contributes to them to take appropriate technical precautions and other measures, taking the state of the art into account, to protect the secrecy of telecommunications and against personal-data breaches.
Section 165(2) requires an operator of a public telecommunications network or provider of a publicly available telecommunications service to take appropriate technical and organisational precautions and other measures against disruptions that significantly impair networks and services and to control the risks to their security.
Where the operator or provider is an essential or important entity under Section 28 of the BSI Act, Section 165(2a) requires the Section 165(2) measures to follow an all-hazards approach and to cover at least ten categories, among them risk analysis and security concepts, incident handling, business continuity, supply-chain security, vulnerability management, cryptography, access control and multi-factor authentication.
Under Section 165(2b) the management of such an entity must implement the measures and monitor their implementation, and under Section 165(2d) it must take part in regular training. Operators and providers with increased hazard potential must use attack-detection systems under Section 165(3), and operators of public networks with increased hazard potential may use critical components only after a recognised certification body has examined and certified them under Section 165(4).
Operators of public networks with increased hazard potential must undergo a review by a qualified independent body or competent national authority every two years under Section 165(9). The Act entered into force on .
When LexLint raises it
When your app profile says your app provides telecom services or runs an essential service.