Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
BTK is Turkey’s telecoms regulator, and its network and information security rules set binding security management, incident reporting, and subscriber data duties for operators in the sector.

What Is BTK Electronic Communications Security?
BTK, the Information and Communication Technologies Authority, is the regulator for Turkey’s electronic communications sector. It licenses operators, allocates spectrum, sets tariff and interconnection rules, and, relevant here, imposes a security regime on anyone providing electronic communications services in the country. If your group owns a Turkish operator, sells managed connectivity there, or supplies an operator as a vendor, these rules reach your systems.
The framework rests on Electronic Communications Law No. 5809 and the secondary regulations BTK issues under it. Two matter most. The regulation on network and information security in the electronic communications sector requires operators to run a formal information security management system, appoint accountable security personnel, carry out risk assessment, test their networks, report security incidents to the regulator, and submit periodic audit reports. The regulation on the processing of personal data and the protection of privacy in the electronic communications sector covers traffic data, location data, subscriber consent for value-added services, data breach notification, and retention periods.
Incident response has its own structure. USOM, the national cyber incident response centre, operates under BTK, and sector organisations are required to establish their own response teams, known as SOMEs, which report into USOM. For a UK reader the closest mental model is a CERT hierarchy written into regulation rather than offered as a service: your Turkish operating company does not choose whether to have a response team, and it does not choose where to report.
British readers will recognise the subject matter and almost none of the institutional arrangement. In the UK, telecoms security duties come from the Telecommunications (Security) Act 2021, with detail in the Electronic Communications (Security Measures) Regulations 2022 and a statutory code of practice underpinned by NCSC’s Telecoms Security Requirements. Ofcom monitors and enforces, providers are tiered by size with staged compliance dates, and the specified measures are prescriptive about things such as management plane separation and privileged access.
Privacy in UK telecoms sits with the ICO under the Privacy and Electronic Communications Regulations 2003, which require communications providers to notify personal data breaches to the ICO within 24 hours, alongside UK GDPR. Three differences are worth planning around.
First, regulator count. Turkey concentrates network security, incident reporting, and sector privacy supervision around BTK, with KVKK as the general data protection authority. The UK splits security to Ofcom and privacy to the ICO, which means two relationships and two reporting routes for one incident.
Second, data retention. Turkish rules impose retention obligations on communications data directly in regulation. The UK withdrew from blanket retention after the European case law of the last decade, and retention now depends on a notice served under the Investigatory Powers Act 2016 on a specific operator. A compliance template written for Istanbul will overcollect in London.
Third, content regulation. Turkish internet law, particularly Law No. 5651, imposes access-blocking and hosting obligations with no UK equivalent, and the Online Safety Act 2023 addresses a different problem through a different mechanism.
Keep one technical control framework and two evidence packs. The controls an operator needs are substantially the same in both markets; what differs is who you prove them to, in what format, and how fast. Map your incident classification to both reporting thresholds up front, because the moment to work out whether something is reportable to BTK, to Ofcom, to the ICO, or to all three is not during the incident. At Privia Security, we help operators build detection and reporting capability that satisfies both regimes through our SOC maturation services.
A cyber incident response team that Turkish regulation requires certain organisations to establish, reporting into USOM, the national incident response centre operating under BTK. Sector and institutional teams have defined responsibilities for detection, response, and notification. The requirement is structural rather than advisory: an in-scope operator must have the team, name its members, and use the defined reporting path.
Both, in different layers. BTK sets sector-specific rules for traffic data, location data, subscriber consent, and breach notification in electronic communications. The general personal data regime under Turkish Personal Data Protection Law No. 6698 applies on top, supervised by the Turkish data protection authority. An operator incident can therefore engage two regulators, much as a UK telecoms breach can engage both Ofcom and the ICO.
Directly, no. The duties bind licensed operators. In practice they reach suppliers through contract, because an operator must manage supplier risk, must be able to evidence the security of outsourced components, and may need to include supplier environments in its testing and audit scope. If you sell network, billing, or support systems into a Turkish operator, expect those obligations to appear in your agreement.
Timescales are set in the applicable regulation and depend on the type of incident, with notification to BTK and through the SOME and USOM structure, followed by fuller reporting on cause and remediation. For comparison, UK communications providers must notify personal data breaches to the ICO within 24 hours under PECR, and security compromises are reported to Ofcom under the Telecommunications (Security) Act regime.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.