Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
USOM is Turkey’s national cyber incident response centre, and SOME are the sectoral and corporate response teams beneath it that organisations in regulated sectors must establish.

What Are SOME and USOM in Turkey?
Turkey organises cyber incident response as a three-tier structure. At the top sits USOM, the National Cyber Incident Response Centre, which acts as the country’s national CERT and is also known internationally as TR-CERT. Beneath it are sectoral SOME, the incident response teams established by sector regulators, and below those the corporate SOME that individual institutions and critical infrastructure operators are required to set up.
For a UK group with a Turkish subsidiary, supplier, or shared service centre, this matters for a practical reason: the obligation to build an internal response team, staff it with named people, and report upwards is imposed by rule rather than left to good practice, and it applies to the local entity regardless of what the parent does.
The structure was formalised by a communique published in the Official Gazette on 11 November 2013 setting out the establishment, duties, and working principles of these teams. Obligations were widened considerably by the Presidential Circular on Information and Communication Security of 2019 and the accompanying Information and Communication Security Guide published in 2020, which apply detailed measures to public institutions and operators of critical infrastructure across energy, transport, water, communications, finance, and health. Turkey’s Cybersecurity Law of 2025 placed national coordination under a new Cybersecurity Directorate, consolidating duties that had previously been spread across several bodies.
In scope organisations are expected to name a team with defined roles and a point of contact registered with the sectoral SOME, maintain documented detection and response procedures, keep logs for a defined retention period, report incidents upward within the timescales their sector sets, and act on alerts USOM issues. In many organisations the SOME is the same group of people who run the security operations centre, with the SOME designation covering the formal reporting and accountability layer on top.
Sector rules go further for regulated industries. Banks and capital markets institutions face detailed information systems requirements including data centre location, independent audit, and business continuity, as the capital markets information systems communique illustrates.
| Turkey | United Kingdom | |
|---|---|---|
| National body | USOM, under the communications regulator | NCSC, part of GCHQ |
| Internal team | Corporate SOME required for in-scope bodies | No legal requirement to form or register a team |
| Reporting route | Sectoral SOME, then USOM | Competent authority under the NIS Regulations; ICO for personal data breaches; FCA for regulated firms |
| Information sharing | USOM alerts and indicator feeds | Voluntary through the NCSC’s CiSP community |
| Network-level action | National blocklists implemented by providers | Protective DNS for the public sector; no general blocklist mandate |
The practical difference is compulsion and structure. UK organisations outside regulated sectors report when a legal duty bites, chiefly the 72-hour personal data breach notification to the ICO, and otherwise engage the NCSC voluntarily. Turkish in-scope organisations operate inside a defined hierarchy with named teams and prescribed channels.
Three things. First, establish whether the Turkish entity is actually in scope; many private companies outside regulated sectors and critical infrastructure are not, and the obligation is sometimes assumed where it does not apply. Second, make the Turkish reporting route an explicit branch of the group incident response plan, with named local contacts, since a parent company in London cannot discharge a reporting duty owed by a subsidiary in Istanbul. Third, remember that data protection notification runs on a separate track entirely: a personal data breach is reported to the Turkish data protection authority under its own rules, independently of any SOME or USOM reporting, and both may apply to the same incident.
If your group needs a response capability that satisfies obligations in more than one jurisdiction, our investigation and incident response services work across local and group reporting lines.
Only if the Turkish entity itself falls in scope, which generally means public institutions and operators of critical infrastructure in sectors such as energy, finance, communications, transport, water, and health, or organisations whose sector regulator imposes the requirement. An ordinary commercial subsidiary outside those categories is not required to establish a corporate SOME, though sector-specific rules should always be checked locally.
Functionally similar, structurally different. Both act as the national technical authority and issue alerts and guidance. USOM sits under the communications regulator and operates a hierarchy of sectoral and corporate teams with mandatory reporting lines, and it coordinates network-level blocking measures. The NCSC, part of GCHQ, works largely through voluntary engagement and guidance, with statutory reporting handled by sector regulators and the ICO.
To the Turkish Personal Data Protection Authority, under the data protection law and its board decisions, not to USOM. The authority expects notification within 72 hours of becoming aware, with affected individuals informed promptly afterwards. An incident can therefore trigger two separate reporting duties in Turkey, and neither satisfies the other.
Partly. The technical work can be delivered by a central team, including monitoring and investigation, but the obligation and the named contacts sit with the local entity, and communications with the sectoral SOME and USOM take place in Turkish through registered channels. Most groups keep central detection capability while appointing local staff to hold the formal roles.
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.