Киберрегулиране: кой е в обхвата и какво следва
Повечето насоки по темата искат да им се доверите. Тези не: всяко правило, което прилагаме, посочва разпоредбата, от която идва, а инструментът показва кои правила са задействани от отговорите ви.
Регулаторната картина
Всеки инструмент по-долу е такъв, който следим: кой го е издал, дали ви задължава по закон или се поема по договор, коя версия е в сила и връзка към официалния текст, а не към нечие резюме.
120 инструмента от 42 юрисдикции и органа по стандартизация.
Показани са всички 120 инструмента
Нищо не отговаря на тези филтри. Опитайте да изчистите някой от тях.
| Инструмент | Произход | Вид | Статус | Версия | Прилага се от | Официален текст |
|---|---|---|---|---|---|---|
| Международни | ||||||
| Trust Services Criteria for service organisation reportsAICPA Trust Services Criteria (2017, revised 2022)КиберсигурностПоверителност и защита на данните | AICPA | Схема за сертифициранеЗадължително в контекст | В сила | TSC 2017 (2022 revision) | — | Официален текст — SOC 2 |
Кого задължаваService organisations, especially SaaS vendors selling into North America. An attestation report by a licensed CPA firm, not a certificate — Type I is a point in time, Type II covers a period. | ||||||
| CIS Critical Security ControlsКиберсигурност | Center for Internet Security | РамкаДоброволно | В сила | v8.1 | — | Официален текст — CIS Controls |
Кого задължаваAny organisation. 18 controls in three implementation groups sized by organisational capability — the usual starting point for a company too small to carry ISO/IEC 27001. | ||||||
| Cloud Controls Matrix and the STAR registryКиберсигурност | Cloud Security Alliance | РамкаДоброволно | В сила | CCM v4 | — | Официален текст — CSA CCM / STAR |
Кого задължаваCloud providers and their customers. 197 control objectives across 17 domains, with a public registry of self-assessments and third-party attestations — often the fastest way to answer a cloud vendor security questionnaire. | ||||||
| Trusted Information Security Assessment ExchangeКиберсигурностСекторно | ENX Association | Схема за сертифициранеЗадължително в контекст | В сила | Based on VDA ISA | — | Официален текст — TISAX |
Кого задължаваThe automotive supply chain. Effectively mandatory to supply German OEMs: an assessment against the VDA ISA catalogue, with results shared through a common exchange rather than re-audited by each customer. | ||||||
| Cyber security for consumer internet of thingsETSI EN 303 645Сигурност на продукти и IoT | ETSI | СтандартЗадължително в контекст | В сила | V3.1.3 | — | Официален текст — ETSI EN 303 645 |
Кого задължаваConsumer IoT manufacturers. Thirteen provisions, of which the first three — no universal default passwords, a vulnerability disclosure policy, and software updates — are what the UK PSTI Act turned into law. | ||||||
| HITRUST Common Security FrameworkКиберсигурностПоверителност и защита на даннитеСекторно | HITRUST | Схема за сертифициранеЗадължително в контекст | В сила | CSF v11 | — | Официален текст — HITRUST CSF |
Кого задължаваPredominantly US healthcare and its supply chain. A prescriptive, certifiable framework that maps onto HIPAA, ISO/IEC 27001, NIST and PCI DSS at once — its selling point being that one assessment answers several. | ||||||
| Security for industrial automation and control systemsIEC 62443 seriesСигурност на продукти и IoTСекторноКиберсигурност | IEC | СтандартЗадължително в контекст | В сила | Series, parts published 2009–2024 | — | Официален текст — IEC 62443 |
Кого задължаваAsset owners, system integrators and product suppliers in OT environments. Organised around security levels SL1–SL4 and zones and conduits, and increasingly cited directly in energy and manufacturing regulation. | ||||||
| Framework for the governance and management of enterprise ITКиберсигурностОперативна устойчивост | ISACA | РамкаДоброволно | В сила | 2019 | — | Официален текст — COBIT 2019 |
Кого задължаваEnterprise IT governance rather than security specifically. Its value here is as the layer that connects board-level objectives to the control frameworks below it — which is exactly what NIS2 management liability asks a board to demonstrate. | ||||||
| Evaluation criteria for IT securityISO/IEC 15408 series (CC:2022)Сигурност на продукти и IoT | ISO / IEC | СтандартЗадължително в контекст | В сила | ISO/IEC 15408:2022 / CC:2022 | — | Официален текст — Common Criteria |
Кого задължаваIT product vendors seeking assurance certification, graded EAL1 to EAL7. The basis of the EU’s EUCC scheme and of procurement requirements in defence and government markets. | ||||||
| Business continuity management systems — RequirementsISO 22301:2019Оперативна устойчивост | ISO / IEC | СтандартЗадължително в контекст | В сила | 2019 | — | Официален текст — ISO 22301 |
Кого задължаваAny organisation. The usual evidence for the business continuity and crisis management limb of NIS2 Article 21(2)(c), DORA and CPS 230. | ||||||
| Risk management — GuidelinesISO 31000:2018Оперативна устойчивост | ISO / IEC | СтандартДоброволно | В сила | 2018 | — | Официален текст — ISO 31000 |
Кого задължаваEnterprise-wide risk management principles. Deliberately not certifiable — it is a set of guidelines, and any body offering ISO 31000 certification is selling something ISO does not recognise. | ||||||
| Information security management systems — RequirementsISO/IEC 27001:2022 + Amd 1:2024Киберсигурност | ISO / IEC | СтандартЗадължително в контекст | В сила | 2022 (Amd 1:2024) | — | Официален текст — ISO/IEC 27001 |
Кого задължаваAny organisation, voluntarily or under contract. The 2022 revision cut Annex A to 93 controls in four themes; Amendment 1:2024 added climate change considerations to the context clause. Добре е да знаетеCertificates issued against the 2013 edition ceased to be valid after 31 October 2025. | ||||||
| Information security controlsISO/IEC 27002:2022Киберсигурност | ISO / IEC | СтандартДоброволно | В сила | 2022 | — | Официален текст — ISO/IEC 27002 |
Кого задължаваImplementation guidance for the Annex A controls of ISO/IEC 27001. Not certifiable in itself — it is the explanation, not the requirement. | ||||||
| Guidance on managing information security risksISO/IEC 27005:2022Киберсигурност | ISO / IEC | СтандартДоброволно | В сила | 2022 | — | Официален текст — ISO/IEC 27005 |
Кого задължаваOrganisations building the risk assessment process that ISO/IEC 27001 clause 6.1.2 requires but deliberately does not prescribe. | ||||||
| Information security controls for cloud servicesISO/IEC 27017:2015Киберсигурност | ISO / IEC | СтандартДоброволно | В сила | 2015 | — | Официален текст — ISO/IEC 27017 |
Кого задължаваCloud service providers and customers, splitting responsibility for each control between them. Usually certified as an extension to an existing ISO/IEC 27001 scope. | ||||||
| Protection of personally identifiable information in public cloudsISO/IEC 27018:2019Поверителност и защита на данните | ISO / IEC | СтандартДоброволно | В сила | 2019 | — | Официален текст — ISO/IEC 27018 |
Кого задължаваPublic cloud providers acting as processors of personal data. Frequently cited in procurement as evidence of GDPR Article 28 processor commitments. | ||||||
| Privacy information management systemISO/IEC 27701Поверителност и защита на данните | ISO / IEC | СтандартЗадължително в контекст | В сила | 2025 revision | — | Официален текст — ISO/IEC 27701 |
Кого задължаваControllers and processors wanting a certifiable privacy management system. The revision restructures it as a standalone PIMS rather than an extension that could only be certified alongside ISO/IEC 27001. | ||||||
| Artificial intelligence management systemISO/IEC 42001:2023Изкуствен интелект | ISO / IEC | СтандартЗадължително в контекст | В сила | 2023 | — | Официален текст — ISO/IEC 42001 |
Кого задължаваOrganisations providing or using AI systems. The first certifiable AI management standard, and the most common answer to how an EU AI Act quality management system gets evidenced. | ||||||
| NIST Cybersecurity FrameworkNIST Cybersecurity Framework (CSF) 2.0Киберсигурност | NIST (US) | РамкаДоброволно | В сила | 2.0 | — | Официален текст — NIST CSF 2.0 |
Кого задължаваAny organisation. Version 2.0 dropped the critical-infrastructure framing and added Govern as a sixth function alongside Identify, Protect, Detect, Respond and Recover. | ||||||
| Protecting controlled unclassified information in nonfederal systemsNIST SP 800-171 Rev. 3Киберсигурност | NIST (US) | РамкаЗадължително в контекст | В сила | Revision 3 | — | Официален текст — NIST SP 800-171 |
Кого задължаваNon-federal organisations holding US Controlled Unclassified Information — in practice, defence and federal supply chains worldwide. It is the control set CMMC Level 2 assesses against. | ||||||
| Zero Trust ArchitectureNIST SP 800-207Киберсигурност | NIST (US) | РамкаДоброволно | В сила | 2020 | — | Официален текст — NIST SP 800-207 |
Кого задължаваArchitectural guidance rather than a control set. The reference definition that US executive orders and a growing number of procurement documents point at when they say "zero trust". | ||||||
| Security and privacy controls for information systems and organizationsNIST SP 800-53 Rev. 5КиберсигурностПоверителност и защита на данните | NIST (US) | РамкаЗадължително в контекст | В сила | Revision 5, with patch releases | — | Официален текст — NIST SP 800-53 |
Кого задължаваMandatory for US federal systems under FISMA; voluntary elsewhere, but the source catalogue that FedRAMP, StateRAMP and many national baselines derive from. | ||||||
| Application Security Verification StandardСигурност на продукти и IoT | OWASP | СтандартДоброволно | В сила | v5.0 | — | Официален текст — OWASP ASVS |
Кого задължаваSoftware teams and the people testing their work. Three verification levels, and the usual way a secure-development requirement in a contract or in the Cyber Resilience Act gets made concrete. | ||||||
| Payment Card Industry Data Security StandardPCI DSS v4.0.1КиберсигурностСекторно | PCI Security Standards Council | СтандартЗадължително в контекст | В сила | v4.0.1 | 31.03.2025 г.предстоящ | Официален текст — PCI DSS |
Кого задължаваAnyone storing, processing or transmitting cardholder data. Not law anywhere, but enforced through the card brands’ contracts, which is a sharper instrument than most statutes. Сроковеv4.0.1 replaced v3.2.1 in March 2024; the 51 future-dated requirements became mandatory on 31 March 2025. | ||||||
| Customer Security Controls FrameworkКиберсигурностСекторно | SWIFT | РамкаЗадължително | В сила | Published annually | — | Официален текст — SWIFT CSCF |
Кого задължаваEvery institution connected to the SWIFT network. Annual self-attestation against the mandatory controls is a condition of continued access, with independent assessment required. | ||||||
| Европейски съюз | ||||||
| Czech Cybersecurity Act (NIS2)Zákon č. 264/2025 Sb., o kybernetické bezpečnostiКиберсигурностДокладване на инциденти | ЧехияПроверете обхвата си | ЗаконЗадължително | В сила | 264/2025 Sb. | 1.11.2025 г. | Официален текст — Zákon o kybernetické bezpečnosti |
Кого задължаваRegulated services in Czechia, split into a higher and a lower obligation regime rather than NIS2’s essential/important wording — one of the clearer examples of a transposition renaming the tiers. Добре е да знаетеImplementing decrees 334/2025, 408/2025, 409/2025 and 410/2025 Sb. carry the actual security measures. | ||||||
| Thresholds identifying German critical installationsBSI-Kritisverordnung (BSI-KritisV)КиберсигурностСекторно | ГерманияПроверете обхвата си | Подзаконов актЗадължително | В сила | BSI-KritisV | — | Официален текст — BSI-KritisV |
Кого задължаваSets the quantitative thresholds — 500 000 supplied persons is the recurring one — that turn a German operator into a KRITIS operator. | ||||||
| German NIS2 implementation actGesetz über das Bundesamt für Sicherheit in der Informationstechnik (BSIG)КиберсигурностДокладване на инциденти | ГерманияПроверете обхвата си | ЗаконЗадължително | В сила | BSIG in the version of the NIS2UmsuCG | 1.01.2026 г. | Официален текст — BSIG 2025 |
Кого задължаваAround 29 000 German entities: besonders wichtige and wichtige Einrichtungen by size and sector, plus operators of critical installations under the BSI-KritisV thresholds. ЕкспозицияUp to €10 000 000 or 2% of worldwide turnover, with explicit management liability for failure to approve and monitor risk measures. | ||||||
| German CER Directive transpositionKRITIS-Dachgesetz (KRITIS-DachG)Оперативна устойчивостСекторно | ГерманияПроверете обхвата си | ЗаконЗадължително | В сила | KRITIS-DachG | — | Официален текст — KRITIS-Dachgesetz |
Кого задължаваOperators of critical infrastructure, for physical resilience: risk assessments, resilience plans and background checks — the non-cyber half that the BSIG does not cover. | ||||||
| Estonian Cybersecurity ActKüberturvalisuse seadusКиберсигурностДокладване на инциденти | ЕстонияПроверете обхвата си | ЗаконЗадължително | В сила | Consolidated text | — | Официален текст — KüTS |
Кого задължаваProviders of vital services and other entities designated under the act, together with the state information system. | ||||||
| Cyber Solidarity Act and the European Cybersecurity Alert SystemRegulation (EU) 2025/38КиберсигурностОперативна устойчивост | Европейски съюзПроверете обхвата си | РегламентЗадължително в контекст | В сила | (EU) 2025/38 | 4.02.2025 г. | Официален текст — Cyber Solidarity Act |
Кого задължаваPrimarily Member States and their CSIRTs, through the alert system and the EU Cybersecurity Reserve. Private entities meet it as recipients of incident response support rather than as duty-holders. | ||||||
| Harmonised rules on fair access to and use of dataRegulation (EU) 2023/2854Поверителност и защита на даннитеОперативна устойчивост | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2023/2854 | 12.09.2025 г. | Официален текст — Data Act |
Кого задължаваManufacturers of connected products and providers of related services, and — through the cloud-switching chapter — every provider of data processing services offered in the EU. Добре е да знаетеThe chapter people miss is switching: contractual, technical and (from January 2027) charge-free egress obligations on cloud providers. | ||||||
| European data governanceRegulation (EU) 2022/868Поверителност и защита на данните | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2022/868 | 24.09.2023 г. | Официален текст — Data Governance Act |
Кого задължаваPublic sector bodies re-using protected data, data intermediation service providers, and recognised data altruism organisations. | ||||||
| Digital Operational Resilience ActRegulation (EU) 2022/2554 on digital operational resilience for the financial sectorОперативна устойчивостКиберсигурностДокладване на инцидентиСекторно | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2022/2554 | 17.01.2025 г. | Официален текст — DORA |
Кого задължаваAround 20 categories of financial entity — banks, insurers, investment firms, payment and e-money institutions, crypto-asset service providers, trading venues — and the critical ICT third-party providers serving them. Добре е да знаетеWhere DORA and NIS2 both reach a financial entity, DORA prevails as lex specialis for ICT risk and incident reporting. | ||||||
| Privacy and electronic communicationsDirective 2002/58/EC as amended by Directive 2009/136/ECПоверителност и защита на данните | Европейски съюзПроверете обхвата си | ДирективаЗадължително | В сила | 2002/58/EC (consolidated) | 31.10.2003 г. | Официален текст — ePrivacy Directive |
Кого задължаваProviders of electronic communications services, and anyone storing or reading information on a user’s device — which is what makes it, not the GDPR, the source of the cookie consent rule. Добре е да знаетеThe ePrivacy Regulation intended to replace it was withdrawn in 2025. The 2002 directive remains the operative text. | ||||||
| ENISA mandate and the European cybersecurity certification frameworkRegulation (EU) 2019/881КиберсигурностСигурност на продукти и IoT | Европейски съюзПроверете обхвата си | РегламентЗадължително в контекст | В сила | (EU) 2019/881 | 27.06.2019 г. | Официален текст — EU Cybersecurity Act |
Кого задължаваGives ENISA a permanent mandate and creates the machinery for EU-wide certification schemes. Certification under it is voluntary unless another instrument makes a scheme mandatory. | ||||||
| European cybersecurity certification scheme on Common CriteriaCommission Implementing Regulation (EU) 2024/482Сигурност на продукти и IoTКиберсигурност | Европейски съюзПроверете обхвата си | Схема за сертифициранеДоброволно | В сила | (EU) 2024/482 | 27.02.2025 г. | Официален текст — EUCC |
Кого задължаваICT products certified against Common Criteria. The first scheme adopted under the Cybersecurity Act; it succeeds the SOG-IS mutual recognition arrangement. | ||||||
| General Data Protection RegulationRegulation (EU) 2016/679Поверителност и защита на даннитеДокладване на инциденти | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2016/679 | 25.05.2018 г. | Официален текст — GDPR |
Кого задължаваAny controller or processor established in the EU, and any outside it that offers goods or services to, or monitors the behaviour of, people in the EU. ЕкспозицияUp to €20 000 000 or 4% of worldwide annual turnover, whichever is higher. | ||||||
| Technical and methodological requirements for digital infrastructure entitiesCommission Implementing Regulation (EU) 2024/2690КиберсигурностДокладване на инциденти | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2024/2690 | 7.11.2024 г. | Официален текст — NIS2 Implementing Regulation |
Кого задължаваDNS providers, TLD registries, cloud and data-centre providers, CDNs, managed service and managed security providers, online marketplaces, search engines, social networks and trust service providers. Добре е да знаетеThis is the only place NIS2 states concrete technical requirements. For every other sector the measures stay at the level of Article 21 and are filled in nationally. | ||||||
| Payment services and strong customer authenticationDirective (EU) 2015/2366 and Commission Delegated Regulation (EU) 2018/389СекторноКиберсигурност | Европейски съюзПроверете обхвата си | ДирективаЗадължително | В сила | Directive (EU) 2015/2366 + RTS (EU) 2018/389 | 14.09.2019 г. | Официален текст — PSD2 / SCA |
Кого задължаваPayment service providers in the EU, including account information and payment initiation services. Добре е да знаетеThe PSD3 directive and Payment Services Regulation proposals are still in the legislative process; PSD2 remains the law. | ||||||
| Cybersecurity essential requirements for radio equipmentCommission Delegated Regulation (EU) 2022/30Сигурност на продукти и IoT | Европейски съюзПроверете обхвата си | РегламентЗадължително | В сила | (EU) 2022/30 | 1.08.2025 г. | Официален текст — RED delegated regulation |
Кого задължаваInternet-connected radio equipment, and equipment processing personal data, traffic data or location data — in practice most consumer IoT sold in the EU. Добре е да знаетеPresumption of conformity comes from the harmonised standards EN 18031-1/-2/-3, cited with restrictions. | ||||||
| Threat intelligence-based ethical red teaming frameworkОперативна устойчивостСекторно | Европейски съюзПроверете обхвата си | РамкаЗадължително в контекст | В сила | 2025 revision | — | Официален текст — TIBER-EU |
Кого задължаваFinancial market infrastructures and significant financial entities, as directed by their national authority. The 2025 revision aligns it with DORA’s threat-led penetration testing requirement. | ||||||
| Italian NIS2 transpositionDecreto legislativo 4 settembre 2024, n. 138КиберсигурностДокладване на инциденти | ИталияПроверете обхвата си | ЗаконЗадължително | В сила | D.lgs. 138/2024 | 16.10.2024 г. | Официален текст — D.lgs. 138/2024 |
Кого задължаваItalian essential and important entities, which register annually with ACN through a portal window that opens each January. | ||||||
| Европа (извън ЕС) | ||||||
| Mandatory cyberattack reporting for critical infrastructureInformationssicherheitsgesetz (ISG), Art. 74a ff.Докладване на инцидентиКиберсигурност | Швейцария | ЗаконЗадължително | В сила | ISG as amended | 1.04.2025 г. | Официален текст — ISA reporting duty |
Кого задължаваSwiss operators of critical infrastructure — energy, water, transport, healthcare, finance, public administration and more. Cyberattacks must be reported to BACS within 24 hours of discovery. | ||||||
| Revised Federal Act on Data ProtectionBundesgesetz über den Datenschutz (DSG)Поверителност и защита на данните | Швейцария | ЗаконЗадължително | В сила | DSG (total revision) | 1.09.2023 г. | Официален текст — revFADP |
Кого задължаваProcessing of personal data with an effect in Switzerland. Broadly GDPR-aligned, but sanctions fall on responsible individuals rather than the company — up to CHF 250 000. | ||||||
| Norwegian Digital Security ActLov om digital sikkerhet (digitalsikkerhetsloven)КиберсигурностДокладване на инциденти | Норвегия | ЗаконЗадължително | В сила | Digitalsikkerhetsloven | 1.01.2025 г. | Официален текст — Digitalsikkerhetsloven |
Кого задължаваNorwegian providers of essential services and digital service providers. It implements NIS1; NIS2 has not yet been incorporated into the EEA Agreement, so Norway sits a directive behind the EU. | ||||||
| Turkish Cybersecurity LawSiber Güvenlik Kanunu (No. 7545)КиберсигурностДокладване на инциденти | Турция | ЗаконЗадължително | В сила | No. 7545 | 19.03.2025 г. | Официален текст — Cybersecurity Law No. 7545 |
Кого задължаваPublic bodies and operators of critical infrastructure in Türkiye, with certification requirements for cybersecurity products and services sold into them. | ||||||
| Law on the Protection of Personal DataKişisel Verilerin Korunması Kanunu (No. 6698)Поверителност и защита на данните | Турция | ЗаконЗадължително | В сила | No. 6698, as amended in 2024 | 7.04.2016 г. | Официален текст — KVKK |
Кого задължаваData controllers processing personal data of people in Türkiye. The 2024 amendment reworked the rules on special categories and international transfers towards the GDPR model. | ||||||
| Sectors of critical infrastructure and criteria for identifying CII objectsПостанова Кабінету Міністрів України № 1109 від 09.10.2020СекторноКиберсигурност | УкрайнаПроверете обхвата си | Подзаконов актЗадължително | В сила | № 1109 від 09.10.2020 | — | Официален текст — CMU Resolution 1109 |
Кого задължаваLists 26 sectors of critical infrastructure and names the sectoral body responsible for each. If you are looking for the question "is my sector in scope in Ukraine", this is the document that answers it. | ||||||
| Procedure for responding to cyber incidents and cyber attacksПостанова Кабінету Міністрів України № 1533 від 26.11.2025Докладване на инциденти | УкрайнаПроверете обхвата си | Подзаконов актЗадължително | В сила | № 1533 від 26.11.2025 | — | Официален текст — CMU Resolution 1533 |
Кого задължаваUkrainian operators of critical infrastructure. The deadline is ONE HOUR from detection of a significant cyber incident — the shortest in this table, and 24 times shorter than the NIS2 early warning. | ||||||
| General cyber protection requirements for critical infrastructure objectsПостанова Кабінету Міністрів України № 518 від 19.06.2019 (у ред. постанови КМУ № 1470 від 13.11.2025)Киберсигурност | УкрайнаПроверете обхвата си | Подзаконов актЗадължително | В сила | № 518 (ред. № 1470 від 13.11.2025) | — | Официален текст — CMU Resolution 518 |
Кого задължаваThe substantive control set for Ukrainian critical infrastructure operators — the closest counterpart to NIS2 Article 21. Substantially rewritten in November 2025. | ||||||
| Vulnerability detection and cyber incident response systemПостанова Кабінету Міністрів України № 943 від 23.10.2020КиберсигурностДокладване на инциденти | УкрайнаПроверете обхвата си | Подзаконов актЗадължително | В сила | № 943 від 23.10.2020 | — | Официален текст — CMU Resolution 943 |
Кого задължаваState bodies and critical infrastructure operators connected to the national vulnerability detection and incident response system. | ||||||
| Law of Ukraine on Critical InfrastructureЗакон України «Про критичну інфраструктуру» № 1882-IXОперативна устойчивостКиберсигурностСекторно | УкрайнаПроверете обхвата си | ЗаконЗадължително | В сила | № 1882-IX (ред. 21.09.2024) | 27.06.2022 г. | Официален текст — Law 1882-IX |
Кого задължаваObjects of critical infrastructure and their operators. Article 10 sets four criticality categories — not the two classes a NIS2 reader expects. Добре е да знаетеUkraine’s regime is a critical-infrastructure regime, not a NIS2 transposition: a different legal theory, a different sector taxonomy and a much shorter reporting clock. | ||||||
| Law on the Basic Principles of Cybersecurity of UkraineЗакон України «Про основні засади забезпечення кібербезпеки України» № 2163-VIIIКиберсигурност | УкрайнаПроверете обхвата си | ЗаконЗадължително | В сила | № 2163-VIII | 9.05.2018 г. | Официален текст — Law 2163-VIII |
Кого задължаваThe framework statute: it defines critical information infrastructure, the national cybersecurity system and who does what within it. | ||||||
| Law on Personal Data ProtectionЗакон України «Про захист персональних даних» № 2297-VIПоверителност и защита на данните | УкрайнаПроверете обхвата си | ЗаконЗадължително | В сила | № 2297-VI | 1.01.2011 г. | Официален текст — Law 2297-VI |
Кого задължаваControllers and processors of personal data in Ukraine. It predates the GDPR and is materially weaker; a GDPR-style replacement has been in draft for several years. Добре е да знаетеEU accession will require alignment with the GDPR. Companies serving EU customers are usually already bound by the GDPR directly under its Article 3(2). | ||||||
| Criteria for determining a significant cyber incidentНаказ Адміністрації Держспецзв’язку № 351 від 14.05.2026 (зареєстровано в Мін’юсті 22.06.2026 за № 900/46294)Докладване на инциденти | УкрайнаПроверете обхвата си | Подзаконов актЗадължително | В сила | № 351 від 14.05.2026 | 30.06.2026 г. | Официален текст — SSSCIP Order 351 |
Кого задължаваDefines the threshold that starts the one-hour clock. Without it the reporting duty had no measurable trigger; it took effect on 30 June 2026. | ||||||
| Cyber Essentials and Cyber Essentials PlusКиберсигурност | Обединеното кралство | Схема за сертифициранеЗадължително в контекст | В сила | Montpellier question set | — | Официален текст — Cyber Essentials |
Кого задължаваVoluntary in general, mandatory for suppliers bidding for UK government contracts that handle sensitive information. | ||||||
| Network and Information Systems Regulations 2018The Network and Information Systems Regulations 2018 (SI 2018/506)КиберсигурностДокладване на инциденти | Обединеното кралство | Подзаконов актЗадължително | В сила | SI 2018/506 | 10.05.2018 г. | Официален текст — NIS Regulations 2018 |
Кого задължаваUK operators of essential services in energy, transport, health, water and digital infrastructure, plus relevant digital service providers. ЕкспозицияUp to £17 000 000 for the most serious contraventions. Добре е да знаетеDerived from NIS1, which the EU has repealed. The UK did not follow NIS2 — the divergence is now substantial. | ||||||
| Product Security and Telecommunications Infrastructure Act 2022Product Security and Telecommunications Infrastructure Act 2022Сигурност на продукти и IoT | Обединеното кралство | ЗаконЗадължително | В сила | 2022 c. 46, with the 2023 security requirements regulations | 29.04.2024 г. | Официален текст — PSTI Act |
Кого задължаваManufacturers, importers and distributors of consumer connectable products in the UK: no universal default passwords, a vulnerability disclosure policy, and a published support period. | ||||||
| Telecommunications (Security) Act 2021 and the Security Code of PracticeСекторноКиберсигурност | Обединеното кралство | ЗаконЗадължително | В сила | 2021 c. 31, with SI 2022/933 | 1.10.2022 г. | Официален текст — Telecommunications (Security) Act |
Кого задължаваUK public electronic communications networks and services, on a tiered timetable by provider size. | ||||||
| UK General Data Protection Regulation and Data Protection Act 2018Data Protection Act 2018 and the retained Regulation (EU) 2016/679Поверителност и защита на данните | Обединеното кралство | ЗаконЗадължително | В сила | DPA 2018, as amended by the Data (Use and Access) Act 2025 | 25.05.2018 г. | Официален текст — UK GDPR / DPA 2018 |
Кого задължаваControllers and processors with a UK establishment, or targeting people in the UK. ЕкспозицияUp to £17 500 000 or 4% of worldwide annual turnover. | ||||||
| Северна Америка | ||||||
| Technology and cyber risk management guidelineКиберсигурностОперативна устойчивостСекторно | Канада | НасокиЗадължително в контекст | В сила | Guideline B-13 | 1.01.2024 г. | Официален текст — OSFI B-13 |
Кого задължаваFederally regulated financial institutions in Canada. Supervisory expectation rather than statute, enforced through the supervisory relationship. | ||||||
| Personal Information Protection and Electronic Documents ActПоверителност и защита на даннитеДокладване на инциденти | Канада | ЗаконЗадължително | В сила | S.C. 2000, c. 5 | 1.01.2001 г. | Официален текст — PIPEDA |
Кого задължаваPrivate-sector organisations handling personal information in the course of commercial activity. Breaches posing a real risk of significant harm must be reported to the Commissioner and to affected individuals. | ||||||
| Act to modernise legislative provisions on the protection of personal informationLoi 25 / Loi sur la protection des renseignements personnels dans le secteur privéПоверителност и защита на данните | Канада — Квебек | ЗаконЗадължително | В сила | Loi 25 | 22.09.2024 г. | Официален текст — Law 25 (Québec) |
Кого задължаваAnyone handling personal information about people in Québec. The closest thing in North America to the GDPR, including data portability and a private right of action. ЕкспозицияAdministrative penalties up to CAD 10 000 000 or 2% of worldwide turnover; penal fines up to CAD 25 000 000 or 4%. | ||||||
| Executive orders on strengthening the nation’s cybersecurityКиберсигурностСигурност на продукти и IoT | Съединени щати | НасокиЗадължително в контекст | В сила | EO 14144 (2025), amended by EO 14306 (2025) | 16.01.2025 г. | Официален текст — EO 14144 / 14306 |
Кого задължаваFederal agencies directly, and software vendors selling to them through the procurement conditions the orders create — secure development attestations, post-quantum planning and identity requirements. | ||||||
| Federal Risk and Authorization Management ProgramКиберсигурностСекторно | Съединени щати | Схема за сертифициранеЗадължително в контекст | В сила | Rev. 5 baselines | — | Официален текст — FedRAMP |
Кого задължаваCloud service providers selling to US federal agencies. Authorization is effectively a precondition of the sale rather than a legal duty on the provider. | ||||||
| Federal Information Security Modernization ActFederal Information Security Modernization Act of 2014, 44 U.S.C. ch. 35КиберсигурностСекторно | Съединени щати | ЗаконЗадължително | В сила | Pub. L. 113-283 | 18.12.2014 г. | Официален текст — FISMA |
Кого задължаваUS federal agencies and, through contract flow-down, the contractors operating systems on their behalf. The control set it mandates is NIST SP 800-53. | ||||||
| Standards for safeguarding customer information16 CFR Part 314Поверителност и защита на даннитеСекторноДокладване на инциденти | Съединени щати | РегламентЗадължително | В сила | 16 CFR Part 314 (as amended 2023) | 9.06.2023 г. | Официален текст — GLBA Safeguards Rule |
Кого задължаваNon-bank financial institutions under FTC jurisdiction — a wider set than it sounds, reaching mortgage brokers, tax preparers, car dealers and many fintechs. Добре е да знаетеSince May 2024 a security event affecting 500 or more consumers must be notified to the FTC within 30 days. | ||||||
| Security standards for the protection of electronic protected health information45 CFR Part 164, Subpart CПоверителност и защита на даннитеСекторноКиберсигурност | Съединени щати | РегламентЗадължително | В сила | 45 CFR §§ 164.302–164.318 | 20.04.2005 г. | Официален текст — HIPAA Security Rule |
Кого задължаваCovered entities — health plans, clearinghouses and most providers — and their business associates, including non-US processors handling PHI under contract. ЕкспозицияCivil money penalties tiered by culpability, with an annual cap per violation category that is adjusted for inflation each year. Добре е да знаетеA January 2025 proposed rule would remove the "addressable" category and make encryption, MFA and asset inventories mandatory. Still a proposal. | ||||||
| Critical Infrastructure Protection reliability standardsСекторноКиберсигурност | Съединени щати | СтандартЗадължително | В сила | CIP-002 through CIP-015 | — | Официален текст — NERC CIP |
Кого задължаваOwners and operators of the bulk electric system in the US, Canada and part of Mexico. Enforced by audit with penalties up to USD 1 million per violation per day. Добре е да знаетеCIP-015, adding internal network security monitoring, is the most recent addition to the family. | ||||||
| Cybersecurity risk management, strategy, governance and incident disclosureSEC Release Nos. 33-11216; 34-97989Докладване на инцидентиКиберсигурност | Съединени щати | РегламентЗадължително | В сила | Release 33-11216 | 18.12.2023 г. | Официален текст — SEC cyber disclosure rules |
Кого задължаваSEC registrants, including foreign private issuers. A material cybersecurity incident goes on Form 8-K Item 1.05 within four business days of the materiality determination; Regulation S-K Item 106 requires annual disclosure of governance and risk management. Добре е да знаетеThe clock runs from the materiality determination, not from discovery — but that determination must be made without unreasonable delay. | ||||||
| Management assessment of internal controlsSarbanes-Oxley Act of 2002, section 404Секторно | Съединени щати | ЗаконЗадължително | В сила | Pub. L. 107-204 | 30.07.2002 г. | Официален текст — SOX §404 |
Кого задължаваUS public companies. Reaches IT because the general IT controls over financial reporting systems — access, change management, operations — are in scope of the audit. | ||||||
| Data breach notification statutes of the 50 statesПоверителност и защита на даннитеДокладване на инциденти | Съединени щати | ЗаконЗадължително | В сила | All 50 states, DC and territories | — | Официален текст — State breach notification laws |
Кого задължаваAnyone holding personal information about residents of a given state. There is no federal breach notification law of general application, so a single incident routinely triggers dozens of statutes with different definitions and deadlines. | ||||||
| Pipeline and rail cybersecurity security directivesСекторноКиберсигурностДокладване на инциденти | Съединени щати | Подзаконов актЗадължително | В сила | Reissued annually | — | Официален текст — TSA Security Directives |
Кого задължаваDesignated pipeline, freight rail, passenger rail and higher-risk airport and aircraft operators. Requires a cybersecurity implementation plan, an assessment programme and 24-hour incident reporting to CISA. | ||||||
| Cybersecurity requirements for financial services companies23 NYCRR Part 500КиберсигурностСекторноДокладване на инциденти | Съединени щати — Ню Йорк | РегламентЗадължително | В сила | Second Amendment | 1.11.2025 г.предстоящ | Официален текст — NYDFS Part 500 |
Кого задължаваEntities licensed by NYDFS — banks, insurers, mortgage servicers, virtual currency businesses. Widely copied by other state regulators, so it functions as a de facto national baseline. СроковеThe Second Amendment phased in over two years, with the final tranche — MFA everywhere, asset inventories — from 1 November 2025. ЕкспозицияAnnual certification of compliance is signed by the CISO and highest-ranking executive; a false certification is itself an enforcement matter. | ||||||
| Азиатско-тихоокеански регион | ||||||
| Prudential Standard CPS 230 Operational Risk ManagementОперативна устойчивостСекторно | Австралия | РегламентЗадължително | В сила | CPS 230 | 1.07.2025 г. | Официален текст — APRA CPS 230 |
Кого задължаваAPRA-regulated entities. Requires identification of critical operations, tolerance levels for disruption, and active management of material service provider risk — the Australian counterpart to DORA’s third-party chapter. | ||||||
| Prudential Standard CPS 234 Information SecurityКиберсигурностСекторно | Австралия | РегламентЗадължително | В сила | CPS 234 (determination F2018L01745) | 1.07.2019 г. | Официален текст — APRA CPS 234 |
Кого задължаваAPRA-regulated banks, insurers and superannuation funds. Requires board-level accountability, controls sized to the threat, testing, and notification to APRA within 72 hours of a material information security incident. | ||||||
| Essential Eight Maturity ModelКиберсигурност | Австралия | РамкаЗадължително в контекст | В сила | Maturity Model, revised periodically | — | Официален текст — Essential Eight |
Кого задължаваMandatory for Australian non-corporate Commonwealth entities at Maturity Level Two; voluntary elsewhere, but widely used as a contractual baseline. Eight mitigations, three maturity levels, and unusually specific about what each level means. | ||||||
| Australian Government Information Security ManualКиберсигурност | Австралия | РамкаЗадължително в контекст | В сила | Updated quarterly | — | Официален текст — ISM |
Кого задължаваAustralian government entities and their suppliers. A large control catalogue organised around a risk management framework, and the source the Essential Eight is drawn from. | ||||||
| Security of Critical Infrastructure Act 2018Security of Critical Infrastructure Act 2018 (Cth)КиберсигурностОперативна устойчивостСекторноДокладване на инциденти | Австралия | ЗаконЗадължително | В сила | Act No. 29 of 2018, as amended through 2024 | 11.07.2018 г. | Официален текст — SOCI Act |
Кого задължаваResponsible entities for critical infrastructure assets across 11 sectors. Obligations stack: an asset register, a critical infrastructure risk management programme, mandatory incident reporting (12 hours for significant, 72 for other), and government assistance powers that can direct an entity mid-incident. Добре е да знаетеThe step-in powers are the part with no European equivalent: in a serious incident the government can issue directions, or intervene on the network itself. | ||||||
| Cybersecurity directions under section 70B(6) of the IT ActДокладване на инцидентиКиберсигурност | Индия | Подзаконов актЗадължително | В сила | Directions of 28 April 2022 | 28.06.2022 г. | Официален текст — CERT-In Directions |
Кого задължаваService providers, intermediaries, data centres, body corporates and government organisations in India. Reportable incidents go to CERT-In within SIX HOURS of noticing them — the shortest general reporting deadline of any major jurisdiction. Добре е да знаетеIt also mandates 180-day log retention within India and five-year KYC retention for VPN, cloud and VPS providers. | ||||||
| Cybersecurity and Cyber Resilience FrameworkКиберсигурностОперативна устойчивостСекторно | Индия | РегламентЗадължително | В сила | CSCRF, August 2024 | — | Официален текст — SEBI CSCRF |
Кого задължаваSEBI-regulated entities, graded into five categories by size and systemic importance, each with a different depth of audit and testing. | ||||||
| Act on the Protection of Personal Information個人情報の保護に関する法律(平成15年法律第57号)Поверителност и защита на даннитеДокладване на инциденти | Япония | ЗаконЗадължително | В сила | Act No. 57 of 2003, as amended | 1.04.2005 г. | Официален текст — APPI |
Кого задължаваBusinesses handling personal information about people in Japan, including foreign businesses supplying goods or services there. Leaks likely to harm individuals must be reported to the PPC — a preliminary report within about 3–5 days and a full report within 30. Добре е да знаетеJapan holds an EU adequacy decision, which is why EU–Japan transfers do not need standard contractual clauses. | ||||||
| Basic Act on Cybersecurityサイバーセキュリティ基本法(平成26年法律第104号)Киберсигурност | Япония | ЗаконЗадължително | В сила | Act No. 104 of 2014, as amended | 9.01.2015 г. | Официален текст — Basic Act on Cybersecurity |
Кого задължаваSets national strategy and allocates responsibility across government, critical infrastructure operators and businesses. Duties on private entities are largely cooperative rather than penal. | ||||||
| Information Security Management System and personal information certificationКиберсигурностПоверителност и защита на данните | Южна Корея | Схема за сертифициранеЗадължително в контекст | В сила | ISMS-P | — | Официален текст — ISMS-P |
Кого задължаваMandatory for Korean telecoms, large ISPs, hospitals and universities above revenue or user thresholds; voluntary for everyone else. Certification is annual with a three-year cycle. | ||||||
| Personal Information Protection ActПоверителност и защита на даннитеДокладване на инциденти | Южна Корея | ЗаконЗадължително | В сила | As amended in 2023 | 30.09.2011 г. | Официален текст — PIPA |
Кого задължаваAny personal information controller handling data about people in Korea. Among the strictest regimes in Asia: breaches are notifiable within 72 hours, and penalties reach 3% of total turnover. | ||||||
| New Zealand Privacy ActПоверителност и защита на даннитеДокладване на инциденти | Нова Зеландия | ЗаконЗадължително | В сила | 2020 No. 31 | 1.12.2020 г. | Официален текст — Privacy Act 2020 |
Кого задължаваAgencies handling personal information in New Zealand, including overseas businesses carrying on business there. Privacy breaches causing serious harm must be notified as soon as practicable. | ||||||
| Singapore Cybersecurity Act, as amended in 2024Cybersecurity Act 2018 (Act 9 of 2018)КиберсигурностДокладване на инциденти | Сингапур | ЗаконЗадължително | В сила | Act 9 of 2018, amended by Act 39 of 2024 | 31.08.2018 г. | Официален текст — Cybersecurity Act |
Кого задължаваOwners of critical information infrastructure in 11 sectors, plus — since the 2024 amendment — foundational digital infrastructure providers, entities of special cybersecurity interest and major systems of national interest. Incidents are reportable within 2 hours. Добре е да знаетеThe 2024 amendment extended the Act to CII physically located outside Singapore, and to systems owned by third parties on which a CII depends. | ||||||
| Technology Risk Management GuidelinesКиберсигурностОперативна устойчивостСекторно | Сингапур | НасокиЗадължително в контекст | В сила | January 2021 revision | — | Официален текст — MAS TRM Guidelines |
Кого задължаваAll MAS-regulated financial institutions. Guidelines rather than law, but non-compliance weighs in MAS’s risk assessment; the binding counterpart is the Notice on Cyber Hygiene. | ||||||
| Personal Data Protection ActПоверителност и защита на даннитеДокладване на инциденти | Сингапур | ЗаконЗадължително | В сила | Act 26 of 2012, as amended in 2020 | 2.07.2014 г. | Официален текст — PDPA |
Кого задължаваOrganisations collecting, using or disclosing personal data in Singapore. Notifiable breaches go to the Commission within 3 calendar days of assessment. ЕкспозицияUp to 10% of annual turnover in Singapore, or SGD 1 000 000, whichever is higher. | ||||||
| Близкия изток и Африка | ||||||
| UAE Information Assurance StandardsКиберсигурност | Обединени арабски емирства | СтандартЗадължително | В сила | IAS v1.1 | — | Официален текст — UAE IA Standards |
Кого задължаваUAE government entities and designated critical information infrastructure operators. Structured as 4 security priorities across 188 controls, mapped closely to ISO/IEC 27001. | ||||||
| Federal Personal Data Protection LawFederal Decree-Law No. 45 of 2021 on the Protection of Personal DataПоверителност и защита на данните | Обединени арабски емирства | ЗаконЗадължително | В сила | Federal Decree-Law No. 45 of 2021 | 2.01.2022 г. | Официален текст — UAE PDPL |
Кого задължаваControllers and processors in the UAE, and those abroad processing data of people in the UAE. The financial free zones — DIFC and ADGM — run their own separate data protection laws, which is the usual trap. | ||||||
| Privacy Protection Law, as amended by Amendment 13Поверителност и защита на данните | Израел | ЗаконЗадължително | В сила | Amendment 13 | 14.08.2025 г. | Официален текст — Privacy Protection Law (Amendment 13) |
Кого задължаваControllers and processors handling personal data in Israel. Amendment 13 brought in administrative fines, mandatory DPOs for large processors, and a substantially expanded enforcement power — a decisive move towards the GDPR model. Добре е да знаетеIsrael holds an EU adequacy decision, which the reform was partly intended to protect. | ||||||
| Essential Cybersecurity ControlsEssential Cybersecurity Controls (ECC-2:2024)Киберсигурност | Саудитска Арабия | СтандартЗадължително | В сила | ECC-2:2024 | — | Официален текст — NCA ECC |
Кого задължаваSaudi government bodies and their contractors, plus operators of critical national infrastructure. Compliance is assessed annually and reported to the NCA. | ||||||
| Cyber Security FrameworkКиберсигурностСекторно | Саудитска Арабия | РамкаЗадължително | В сила | Version 1.0 | — | Официален текст — SAMA CSF |
Кого задължаваBanks, insurers, financing and credit bureau companies regulated by SAMA. Maturity-model based, assessed on a 0–5 scale with level 3 as the minimum expectation. | ||||||
| Personal Data Protection LawПоверителност и защита на данните | Саудитска Арабия | ЗаконЗадължително | В сила | Royal Decree M/19, as amended | 14.09.2023 г. | Официален текст — Saudi PDPL |
Кого задължаваAny processing of personal data of people in Saudi Arabia, including by entities outside the Kingdom. Enforcement began after a one-year grace period in September 2024. | ||||||
| Cybercrimes Act 19 of 2020КиберсигурностДокладване на инциденти | Южна Африка | ЗаконЗадължително | В сила | Act 19 of 2020 (Government Gazette No. 44651) | 1.12.2021 г. | Официален текст — Cybercrimes Act |
Кого задължаваCreates cybercrime offences and, unusually for a criminal statute, puts a reporting duty on electronic communications service providers and financial institutions: 72 hours to report an offence they become aware of. | ||||||
| Protection of Personal Information ActProtection of Personal Information Act 4 of 2013Поверителност и защита на даннитеДокладване на инциденти | Южна Африка | ЗаконЗадължително | В сила | Act 4 of 2013 | 1.07.2021 г. | Официален текст — POPIA |
Кого задължаваResponsible parties processing personal information in South Africa. Security compromises must be reported to the Regulator and to data subjects as soon as reasonably possible. ЕкспозицияAdministrative fines up to ZAR 10 000 000, and criminal liability for some offences. | ||||||
| Латинска Америка | ||||||
| Cybersecurity policy for financial institutionsResolução CMN nº 4.893/2021КиберсигурностСекторно | Бразилия | Подзаконов актЗадължително | В сила | Resolução CMN nº 4.893/2021 | 1.07.2021 г. | Официален текст — CMN Resolution 4.893 |
Кого задължаваBrazilian financial institutions: a documented cybersecurity policy, an incident response plan, and prior notice to the central bank before contracting relevant cloud or data processing services abroad. | ||||||
| General Personal Data Protection LawLei Geral de Proteção de Dados Pessoais, Lei nº 13.709/2018Поверителност и защита на даннитеДокладване на инциденти | Бразилия | ЗаконЗадължително | В сила | Lei nº 13.709/2018 | 18.09.2020 г. | Официален текст — LGPD |
Кого задължаваAny processing of personal data carried out in Brazil, aimed at people in Brazil, or of data collected there — regardless of where the controller sits. ЕкспозицияUp to 2% of Brazilian turnover, capped at BRL 50 000 000 per infraction. Добре е да знаетеANPD Resolution 15/2024 sets the security incident notification procedure and a three-working-day deadline. | ||||||
| Resilience of critical entitiesDirective (EU) 2022/2557 on the resilience of critical entitiesОперативна устойчивостСекторно | Европейски съюзПроверете обхвата си | ДирективаЗадължително | Поетапно въвеждане | Directive (EU) 2022/2557 | 18.10.2024 г.предстоящ | Официален текст — CER Directive |
Кого задължаваEntities identified by Member States as critical in 11 sectors. This is the physical-resilience twin of NIS2 — same sectors, non-cyber threats. СроковеTransposition was due 17 October 2024; Member States were to identify their critical entities by 17 July 2026. Добре е да знаетеAn entity identified under CER is automatically an essential entity under NIS2. The reverse does not hold. | ||||||
| Horizontal cybersecurity requirements for products with digital elementsRegulation (EU) 2024/2847Сигурност на продукти и IoTКиберсигурностДокладване на инциденти | Европейски съюзПроверете обхвата си | РегламентЗадължително | Поетапно въвеждане | (EU) 2024/2847 | 11.12.2027 г.предстоящ | Официален текст — Cyber Resilience Act |
Кого задължаваAnyone placing a product with digital elements on the EU market — hardware and software alike, including remote data processing solutions. Manufacturers carry the weight; importers and distributors carry checks. СроковеIn force since 10 December 2024. Reporting of actively exploited vulnerabilities applies from 11 September 2026; conformity assessment body provisions from 11 June 2026; the full regime from 11 December 2027. ЕкспозицияUp to €15 000 000 or 2.5% of worldwide annual turnover for breach of the essential requirements. Добре е да знаетеThe obligation that surprises people is the support period: security updates for the expected product lifetime, presumed to be at least five years. | ||||||
| European Digital Identity FrameworkRegulation (EU) 2024/1183 amending Regulation (EU) No 910/2014Поверителност и защита на даннитеКиберсигурност | Европейски съюзПроверете обхвата си | РегламентЗадължително | Поетапно въвеждане | (EU) 2024/1183 | 20.05.2024 г.предстоящ | Официален текст — eIDAS 2 |
Кого задължаваTrust service providers, Member States issuing wallets, and — on the acceptance side — very large online platforms, banks, telecoms and other regulated relying parties. СроковеMember States must offer at least one EU Digital Identity Wallet by the end of 2026; large online platforms and regulated sectors must accept it thereafter. | ||||||
| Artificial Intelligence ActRegulation (EU) 2024/1689 laying down harmonised rules on artificial intelligenceИзкуствен интелектСигурност на продукти и IoT | Европейски съюзПроверете обхвата си | РегламентЗадължително | Поетапно въвеждане | (EU) 2024/1689 | 2.08.2026 г.предстоящ | Официален текст — EU AI Act |
Кого задължаваProviders, deployers, importers and distributors of AI systems placed on or used in the EU market, including providers established outside it whose output is used in the Union. СроковеIn force since 1 August 2024. Prohibited practices and AI literacy applied from 2 February 2025; general-purpose AI obligations from 2 August 2025; most high-risk obligations from 2 August 2026; Annex I embedded high-risk from 2 August 2027. ЕкспозицияUp to €35 000 000 or 7% of worldwide annual turnover for prohibited practices; €15 000 000 or 3% for most other breaches. Добре е да знаетеA Commission simplification package has proposed deferring parts of the high-risk timetable. Check the current position before planning to a 2026 date. | ||||||
| Measures for a high common level of cybersecurity across the UnionDirective (EU) 2022/2555 on measures for a high common level of cybersecurity across the UnionКиберсигурностДокладване на инцидентиОперативна устойчивост | Европейски съюзПроверете обхвата си | ДирективаЗадължително | Поетапно въвеждане | Directive (EU) 2022/2555 | 18.10.2024 г.предстоящ | Официален текст — NIS2 |
Кого задължаваMedium and large entities in 18 sectors (Annexes I and II), plus named entities of any size — DNS providers, TLD registries, trust service providers, public administration and sole providers of an essential service. СроковеTransposition was due 17 October 2024. National laws are still landing — Germany applied its act from January 2026, Czechia from November 2025, Poland from 2026; France and Spain have none in force. ЕкспозицияEssential entities: up to €10 000 000 or 2% of worldwide annual turnover. Important entities: up to €7 000 000 or 1.4%. Management bodies can be held personally liable. | ||||||
| Polish national cybersecurity system act, as amended for NIS2Ustawa o krajowym systemie cyberbezpieczeństwaКиберсигурностДокладване на инциденти | ПолшаПроверете обхвата си | ЗаконЗадължително | Поетапно въвеждане | Dz.U. 2026 poz. 252 | —предстоящ | Официален текст — KSC (NIS2 amendment) |
Кого задължаваKey and important entities established in Poland, replacing the earlier operator-of-essential-services designation model with self-identification and registration. СроковеPublished in the Journal of Laws as Dz.U. 2026 poz. 252, with a vacatio legis before the substantive duties bite and separate transition periods for registration and for the security measures. Registration deadlines run from the date an entity meets the criteria, not from a single national cut-off. | ||||||
| Cybersecurity Maturity Model Certification32 CFR Part 170 and DFARS 252.204-7021КиберсигурностСекторно | Съединени щати | Схема за сертифициранеЗадължително | Поетапно въвеждане | CMMC 2.0 (32 CFR Part 170) | 16.12.2024 г.предстоящ | Официален текст — CMMC |
Кого задължаваThe defence industrial base — any contractor or subcontractor handling Federal Contract Information or Controlled Unclassified Information, including non-US suppliers. СроковеThe programme rule took effect in December 2024; the acquisition rule that puts the requirement into contracts followed in November 2025, starting a three-year phase-in. | ||||||
| California Consumer Privacy Act, as amendedCalifornia Civil Code § 1798.100 et seq.Поверителност и защита на даннитеКиберсигурност | Съединени щати — Калифорния | ЗаконЗадължително | Поетапно въвеждане | CCPA as amended by CPRA, plus the 2025 CPPA regulations | 1.01.2023 г.предстоящ | Официален текст — CCPA / CPRA |
Кого задължаваFor-profit businesses meeting revenue or data-volume thresholds that handle personal information of California residents — including businesses with no California presence. СроковеThe 2025 regulations add cybersecurity audits, risk assessments and rules for automated decision-making technology, phasing in from 2027 through 2030. Добре е да знаетеAround twenty other US states now have comprehensive privacy laws of their own; California is the one that has added a security audit obligation. | ||||||
| Australian Cyber Security ActCyber Security Act 2024 (Cth)КиберсигурностДокладване на инцидентиСигурност на продукти и IoT | Австралия | ЗаконЗадължително | Поетапно въвеждане | Act No. 106 of 2024 | 30.05.2025 г.предстоящ | Официален текст — Cyber Security Act 2024 |
Кого задължаваBusinesses with annual turnover above AUD 3 million must report a ransomware or cyber extortion payment within 72 hours. Separately, manufacturers and suppliers of internet-connectable consumer products must meet mandatory security standards. СроковеRansomware payment reporting began on 30 May 2025. Mandatory security standards for smart devices commenced in March 2025 for newly supplied products. Добре е да знаетеIt also creates a limited-use protection: information given to the National Cyber Security Coordinator during an incident is restricted in how it may be used against the reporting entity. | ||||||
| Privacy Act and the Notifiable Data Breaches schemePrivacy Act 1988 (Cth)Поверителност и защита на даннитеДокладване на инциденти | Австралия | ЗаконЗадължително | Поетапно въвеждане | As amended by the Privacy and Other Legislation Amendment Act 2024 | 1.01.1989 г.предстоящ | Официален текст — Privacy Act 1988 |
Кого задължаваAustralian government agencies and organisations with turnover above AUD 3 million, plus smaller entities in health and credit. Eligible data breaches must be assessed within 30 days and notified to the OAIC and affected individuals. СроковеThe 2024 amendments phase in through 2026, including a statutory tort for serious invasions of privacy and transparency duties for automated decisions. ЕкспозицияUp to AUD 50 000 000, three times the benefit obtained, or 30% of adjusted turnover for the relevant period. | ||||||
| Digital Personal Data Protection ActThe Digital Personal Data Protection Act, 2023Поверителност и защита на даннитеДокладване на инциденти | Индия | ЗаконЗадължително | Поетапно въвеждане | Act No. 22 of 2023, with the 2025 Rules | 11.08.2023 г.предстоящ | Официален текст — DPDP Act |
Кого задължаваAnyone processing digital personal data in India, and processing outside India connected with offering goods or services to people in India. СроковеThe Act was passed in 2023 but only became operable with the DPDP Rules notified in November 2025; the substantive obligations phase in over the following 18 months. ЕкспозицияUp to INR 250 crore for failure to take reasonable security safeguards. | ||||||
| Act on Active Cyber DefenceКиберсигурностДокладване на инциденти | Япония | ЗаконЗадължително | Поетапно въвеждане | Enacted 2025 | 16.05.2025 г.предстоящ | Официален текст — Active Cyber Defence Law |
Кого задължаваDesignated critical infrastructure operators, who gain reporting duties; and, on the state side, powers to monitor certain communications and neutralise attacker infrastructure. СроковеEnacted in May 2025 with provisions commencing in stages through 2027, including incident reporting duties on designated critical infrastructure operators. | ||||||
| European Health Data SpaceRegulation (EU) 2025/327Поверителност и защита на даннитеСекторно | Европейски съюзПроверете обхвата си | РегламентЗадължително | Приет, още не се прилага | (EU) 2025/327 | 26.03.2029 г.предстоящ | Официален текст — EHDS |
Кого задължаваHealthcare providers, EHR system manufacturers and wellness app vendors, plus health data holders and users on the secondary-use side. СроковеIn force since 26 March 2025, with the primary-use and secondary-use chapters applying in stages from 2029 through 2031. | ||||||
| Machinery, including cybersecurity of safety functionsRegulation (EU) 2023/1230Сигурност на продукти и IoTСекторно | Европейски съюзПроверете обхвата си | РегламентЗадължително | Приет, още не се прилага | (EU) 2023/1230 | 20.01.2027 г. | Официален текст — Machinery Regulation |
Кого задължаваManufacturers of machinery and related products for the EU market. It replaces the Machinery Directive 2006/42/EC and, for the first time, treats corruption of safety-related control software as a safety requirement. | ||||||
| Cyber Incident Reporting for Critical Infrastructure ActCyber Incident Reporting for Critical Infrastructure Act of 2022Докладване на инциденти | Съединени щати | ЗаконЗадължително | Приет, още не се прилага | Pub. L. 117-103, Div. Y | 15.03.2022 г.предстоящ | Официален текст — CIRCIA |
Кого задължаваCovered entities in the 16 critical infrastructure sectors. As drafted: substantial cyber incidents reported within 72 hours, ransom payments within 24. СроковеThe statute is in force but creates no duty until CISA’s implementing rule takes effect. The proposed rule was published in April 2024; the final rule has slipped repeatedly. | ||||||
| Spanish cybersecurity coordination and governance billAnteproyecto de Ley de Coordinación y Gobernanza de la CiberseguridadКиберсигурност | Испания | ЗаконЗадължително | Предложен | Draft bill | — | Официален текст — Anteproyecto de Ley de Ciberseguridad |
Кого задължаваWould transpose NIS2 in Spain. Real Decreto-ley 12/2018 (the NIS1 transposition) remains the operative law meanwhile. | ||||||
| French NIS2, CER and DORA transposition billProjet de loi relatif à la résilience des infrastructures critiques et au renforcement de la cybersécuritéКиберсигурностОперативна устойчивост | Франция | ЗаконЗадължително | Предложен | Bill, not enacted | — | Официален текст — Projet de loi résilience |
Кого задължаваWould cover French essential and important entities. Until it passes, France has no NIS2 law in force and the directive is not directly effective against private entities. Добре е да знаетеThis is why the scope check assesses France against the EU baseline and says so, rather than inventing French rules. | ||||||
| UK Cyber Security and Resilience BillКиберсигурностДокладване на инциденти | Обединеното кралство | ЗаконЗадължително | Предложен | Bill before Parliament | — | Официален текст — Cyber Security and Resilience Bill |
Кого задължаваWould extend the NIS Regulations to managed service providers, widen incident reporting and give regulators cost-recovery powers. | ||||||
| Critical Cyber Systems Protection ActКиберсигурностДокладване на инциденти | Канада | ЗаконЗадължително | Предложен | Bill before Parliament | — | Официален текст — CCSPA (Bill C-8) |
Кого задължаваWould bind designated operators in federally regulated finance, telecommunications, energy and transport, with a 72-hour incident reporting duty to the Cyber Centre. Добре е да знаетеA predecessor bill died when Parliament was prorogued in January 2025; this is the reintroduction. | ||||||
| Security of network and information systems (superseded)Directive (EU) 2016/1148Киберсигурност | Европейски съюзПроверете обхвата си | ДирективаЗадължително | Отменен | Directive (EU) 2016/1148 | — | Официален текст — NIS Directive |
Кого задължаваRepealed by NIS2 with effect from 18 October 2024. Listed because national laws made under it — and audit findings citing it — are still in circulation. | ||||||
Тази информация може да е остаряла или неточна. Проверете официалния текст, преди да разчитате на нея на практика.
Как работи
- 1Двигател на правила, а не оценка. Всяко правило е условие върху отговорите ви, ефект и позоваване. Нищо не се претегля невидимо.
- 2Липсващите данни отслабват отрицателния отговор, никога положителния. Ако не можем да определим, казваме го, вместо да съобщим, че сте извън обхвата.
- 3Отговорите ви остават в браузъра ви. Оценката се изпълнява локално; нищо не се изпраща никъде, освен ако не решите вие.
Юрисдикции
Публикуваме юрисдикция едва след като основните ѝ инструменти са идентифицирани. Държавите под този праг могат да се избират в инструмента, но ясно ви се казва, че сте оценени спрямо базовото ниво на ЕС.
- Европейски съюз (базово ниво по NIS2)ENISAМоделирана
- УкрайнаАдміністрація Держспецзв’язкуМоделирана
- ГерманияBundesamt für Sicherheit in der Informationstechnik (BSI)Моделирана
- ИталияAgenzia per la cybersicurezza nazionale (ACN)Моделирана
- ПолшаMinisterstwo Cyfryzacji (rejestr); sektorowe organy właściwe (nadzór)Моделирана
- ЧехияNárodní úřad pro kybernetickou a informační bezpečnost (NÚKIB)Моделирана
- ЕстонияRiigi Infosüsteemi Amet (RIA)Моделирана
- ФранцияAgence nationale de la sécurité des systèmes d’information (ANSSI)Само базовото ниво на ЕС
- ИспанияDepartamento de Seguridad Nacional (DSN) — punto de contacto único; autoridades sectoriales (RD 43/2021 art. 3)Само базовото ниво на ЕС
- НорвегияNasjonal sikkerhetsmyndighet (NSM) — nasjonalt kontaktpunkt; sektorvise tilsynsmyndigheterСамо базовото ниво на ЕС
За правното съдържание
Позоваванията са извлечени от официални източници — EUR-Lex за правото на ЕС, порталът на Върховната рада за украинските актове — на датата, посочена при всяко от тях. Съдържанието все още не е минало правен преглед и инструментът го казва там, където има значение.