Turkey's Cyber Security Directorate has opened a 38-page draft Cyber Resilience Regulation for comment. It sets a 12-hour incident notification window and a 72-hour status report.
Türkiye's Presidential Cyber Security Directorate opened the draft Cyber Resilience Regulation (Siber Dayanıklılık Yönetmeliği) for public comment on 18 November 2026. The 38-page draft rests on Law No. 7545 on Cyber Security, dated 12 March 2025, and Presidential Decree No. 177. It is not yet in force: scope and commencement will be settled after the consultation closes.
What the draft actually requires
The most concrete part of the text is reporting time. Cyber incidents are graded on five levels, from a low-impact event touching a limited number of systems up to a national cyber crisis that disrupts critical infrastructure. Under Article 33, level 1 and level 2 incidents must be reported to the organisation's sectoral incident response team (SOME) within 12 hours of detection. Level 3, 4 and 5 incidents go to both the sectoral SOME and the Directorate itself inside the same window. A status report covering the current state of the incident, the first assessment findings and the measures taken is due within 72 hours.
The draft also establishes a National Asset Inventory Database (UVET). Unless stated otherwise, changes to registered entries must be reported within one month. Organisations told to form an institutional SOME have one month from that notice to stand up a team of at least three people. The Directorate will publish a Cyber Security Maturity Model; first assessments are due within six months of its publication, with results reported by the end of January each year. Anyone below the minimum level has three months to submit an improvement plan.
Where this leaves a mid-sized company
The weight of the SOME, maturity-reporting and annual exercise obligations sits with critical infrastructure operators and public bodies. Article 26, however, sets baseline cyber hygiene duties for parties that have no institutional SOME obligation at all: strong passwords, never sharing one-time verification codes or access credentials with third parties, malware protection on computers, installing applications only from official vendor sources or app stores, keeping operating systems and software current, and backing up critical data at regular intervals.
Organisations serving customers through a public website, an e-commerce platform or a mobile app pick up extra duties: email or SMS verification at sign-up, automatic session termination after a period of inactivity, basic controls against unauthorised commands and database queries, and preventing passwords or account details from travelling in clear text in URLs. The same article notes that where a breach of these baseline duties is found to have enabled an attack on critical infrastructure, the sanctions under Law No. 7545 may follow. Supervision and enforcement are handled in Article 74; the draft sets out no separate fine schedule of its own.
The practical reading: for a construction office or logistics firm on Istanbul's Anatolian side, none of this is a live obligation today. But meeting a 12-hour window requires logging that surfaces the incident, a backup whose restore has been tested, and one named person who knows who to call. If those are missing now, the runway after publication will be short.
What we recommend at Kamer Bilişim
- Write your asset inventory down. Which server, firewall, NAS and cloud account belongs to whom, where each dataset sits, what depends on what — one table is enough. If a UVET-style filing arrives, that list is your starting point.
- Get your incident response flow onto one page. Who notices, who they call, who decides, which logs are preserved. Twelve hours is short for a team still working out whose number to dial.
- Close the basics now. Multi-factor authentication, a current patch level, central log collection and a backup you have restored from. Article 26 already asks for these, and no higher-order control works meaningfully without them.
If you would like to review how ready your current setup is against these points, reach us through our contact page.
Kaynak: CUMHA, "Siber Güvenlik Başkanlığından Siber Dayanıklılık Yönetmeliği Taslağı", 20 November 2026; Presidential Cyber Security Directorate announcement, 18 November 2026.
Source: CUMHA