Bulgaria

Bulgaria Ordinance on Minimum Requirements for Network and Information Security (2019)

51 controls. 3 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

51 controls 3 frameworks share controls with it Bulgaria verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
1Scope: administrative authorities, operators of essential services, digital service providers and other bodies delivering administrative services electronically; what the ordinance0
10Contract network and information security requirements with every third-party supplier (access controls, proof of their own measures, supply chain transparency, consequences, liabi1
11Manage changes to critical information assets under internal rules: assess risk first, plan with deadlines and responsibilities, coordinate with affected process owners, obtain app1
12Build security into projects and technical requirements for new or changed systems on the basis of risk assessment, and introduce new systems only in a planned way after documented1
13Separate systems with different functions physically or logically from each other and from third-party systems, and separate subsystems at the final physical or logical level so an1
14Filter traffic between systems and subsystems on approved rules by address, protocol and port, review the rules for unauthorised change and update them against new threats, and blo1
15Set clear policies, written into internal rules with matching measures, on personal devices inside the entity's network and on portable storage devices1
16Set policies and internal rules for cryptographic mechanisms that protect the confidentiality and integrity of sensitive information according to its classification, matched to the1
17(1)Protect administrative accounts: change vendor defaults before deployment, make them personal, use them only for administration, grant them only to administrators within their peri1
17(2)-(4)Rotate administrator passwords at least yearly, on departure of anyone who knew them and after a breach; log every privileged operation per administrator profile under Articles 5 a1
18Administer systems only from a separate, secured administration environment isolated from other systems and from the internet and used for nothing else, or else protect the adminis1
19(1)-(3)Grant access to systems only where strictly necessary: define role-based access rights and request, change and termination procedures in internal rules, enforce authentication, aut1
19(4)-(6)Review all access at least yearly through the persons authorised to grant it, using administrator-provided lists of accounts and levels and recording confirmations or changes; limi1
2Principles: organisational, technological and technical measures proportionate to risk, protecting availability, integrity and confidentiality across the information lifecycle, div0
20Protect remote access and teleworking under the Article 19 rules with at least two-factor authentication, only high-protection channels such as VPN, and no FTP or Remote Desktop Co1
21Protect hardware against technical failure and unauthorised access: maintain and monitor the manufacturer's environmental and mechanical conditions, run planned maintenance under t1
22(1)-(4)Run only supplier-supported, security-current software and firmware approved by the head of the entity, keep a distribution library for fast recovery, and prevent the installation 1
22(5)-(8)Through internal rules keep the distribution library current and access-controlled, track newly published vulnerabilities and fixes for the software and firmware in use, verify the1
23Deploy anti-intrusion and anti-malware measures on every component where possible, keep them current, run full scans at least weekly where applicable, scan email, downloads and por1
24(1)-(3)Secure web servers with a unique certificate from a trusted certification authority (SHA-2 or stronger, current, expired certificates revoked), HTTPS only over TLS 1.2 or 1.3 or ne1
24(4)-(8)Protect web applications with a web application firewall against CSRF, XSS, file inclusion and SQL injection, accept user input only at designated points, validate all client-suppl1
24(9)-(15)Harden web services against denial of service and brute force (request and header limits, timeouts, failed-logon limits), suppress directory listings, set Secure and HttpOnly cooki1
25Protect DNS: place multiple DNS servers in different networks, deploy DNSSEC, minimise queries per RFC 7816, forbid zone transfers, and publish DMARC and SPF records1
26Provide physical protection for information assets against unauthorised access and against fire, flooding and chemical or physical changes in the air, proportionate to the assets, 1
27Where industrial control systems underpin the essential services provided, protect them with appropriate measures in line with the regulations that apply to them0
28Operate automated event detection on critical systems by analysing flows, protocols and files at key points, positioned to see all traffic between the entity's systems and third pa1
29(1)-(3)Log on application servers for critical activities, infrastructure and security devices, ICS engineering stations, network equipment and administrator workstations at least authent1
29(4)-(6)Restrict log access, read-only, to monitoring and incident staff and to lawful investigators of serious and computer crimes, archive logs for at least twelve months under the Artic1
3(1)Senior accountability for network and information security: the head of the entity carries direct responsibility, establishes a management system aligned with BDS ISO/IEC 27001, re2
3(2)-(3)Appoint a staff member or unit responsible for network and information security reporting directly to the head of the entity, with a counterpart in every territorial structure runn1
30(1)-(2)Regulate incident handling through internal rules covering reporting, the incident log and its keepers, logging, verification, classification and prioritisation of signals with fee1
30(3)-(4)Maintain current response plans for the incidents with the gravest impact (incident lead, notifications, measures and owners, consultation, monitoring during the incident, evidence1
31Notify the sectoral CSIRT of incidents within the Cybersecurity Act deadlines through the security officer, using the Annex 7 form (initial data within two hours, full report withi1
32(1)-(3)Set backup and archiving rules aligned to the security policy that fix what is backed up, the technology, backup type, frequency, number of copies, retention per copy, storage loca1
32(4)Execute backups to the risk of loss and rate of change, label copies with content, system, method, date and time, encrypt or at least password-protect copies of sensitive informati1
33Provide redundancy proportionate to risk to sustain in-scope services: backup systems, backup devices, load balancing of critical devices or systems, and backup data centres1
34Hold emergency and continuity action plans for events that could disrupt services, stating the circumstances, activation thresholds, the approver of activation and the restoration 1
35Verify compliance with Chapter Two and adopted standards through internal audits at least yearly under BDS EN ISO 19011 and BDS EN ISO/IEC 17020, by qualified, impartial auditors w1
36-37Inspections by the Minister of Electronic Government and surveys by the national competent authorities: how the state checks compliance0
38-43Register of essential services: identification by designated administrative bodies, two-yearly review, TLP-RED classification, transmission to the Minister of Electronic Government0
4Adopt a network and information security policy stating strategic security objectives and the approach to reaching them, covering the topical sub-policies, reviewed at least yearly1
5(1)-(2)Maintain the prescribed documentation set (asset descriptions, network topology, information flows, cabling, system documentation, operating instructions and user rules), identifie1
5(3)-(4)Keep information that conclusively proves compliance with the ordinance, up to date and available only to staff who need it, to the national competent authority under Article 16(5)1
6Classify information through internal rules on marking, use, processing, exchange, storage and destruction, extend the classification to the resources that handle it, mark document1
7Run a documented, repeatable risk analysis and assessment at least yearly and on significant change, with an approved methodology, defined unacceptable-risk levels and named roles,1
8Govern the lifecycle of systems and components through internal rules (acquisition, deployment, maintenance, relocation, decommissioning, destruction) and keep an asset description1
9Secure human resources through internal rules on hiring, security duties on exit or role change, disciplinary procedures, documented responsibilities with deadlines, professional t1
AP-TFPAdditional, transitional and final provisions: conformity with the ISO/IEC 27000 family and the NIS Cooperation Group recommendations, the DNSSEC, DMARC and SPF definitions, the fo0
Annex-1Annex 1: the list of international standards the measures are built on, from the ISO/IEC 27000 family through risk, identity, key management, encryption, audit, evaluation and priv0
Annex-2-3Annexes 2 and 3: the recommended four-level information classification with TLP equivalents and system requirements per level, and the recommended risk analysis and assessment meth0
Annex-4-9Annexes 4 to 9: configuration requirements, response header requirements, security officer functions, the incident notification form, the quarterly statistics form and the incident0

Tell me when Bulgaria Ordinance on Minimum Requirements for Network and Information Security (2019) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for Bulgaria Ordinance on Minimum Requirements for Network and Information Security (2019), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition