Skip to content

NIS2 in Bulgaria: Is Your Shop in Scope?

NIS2 in Bulgaria: Is Your Shop in Scope?
Blog 4 min read

NIS2 has applied in Bulgaria since 17 February 2026. How to judge whether your shop is in scope and what to ask your hosting provider to put in writing.

This is general information, not legal advice. Whether NIS2 applies to a business depends on its sector, size and activity, so confirm your status with counsel. What follows is a practical checklist for shop and SMB teams that host in Sofia.

The amendments to the Bulgarian Cybersecurity Act that transpose NIS2 were adopted on 5 February 2026, published in State Gazette issue 17 on 13 February and entered into force on 17 February 2026. There was no general transition period. For a shop operator the question is no longer whether the directive exists. It is whether you, or a customer you supply, fall in scope, and what your hosting contract will say when someone asks.

Scope: a shop versus an essential or important entity

NIS2 covers far more than banks and energy. Digital infrastructure, cloud and managed ICT services, postal and courier services, food production and distribution, and digital providers such as online marketplaces can all be in scope when they pass the size thresholds. Fines for essential entities can reach 2 % of worldwide turnover, and for important entities 1.4 %. A small online shop is often outside the list. Its customers may not be: B2B buyers, marketplaces, insurers and public-sector clients now send supplier questionnaires that read like NIS2 evidence requests.

Run a quick scan: employee and turnover thresholds, the sector lists in the Act, whether you sell managed ICT to others, and the security clauses in your own customer contracts. If the answer is unclear, plan for customers asking for proof rather than for an exemption.

What to ask your hosting provider to put in writing

NIS2 treats supply chain security as part of risk management, so auditors and vendor forms want commitments on paper:

  • Data location: where production data and backups are stored. EuroVDC hosts in Sofia, in the EU.
  • Processor role: GDPR Article 28 requires a written contract that sets out what the processor may do with personal data.
  • Incident notice: how quickly and through which channel you are told. NIS2 itself sets an early warning within 24 hours and a notification within 72 hours for significant incidents, so your provider’s timing has to fit inside that.
  • Access and subcontractors: who in support can reach your data, and which third parties are involved.
  • Backups and recovery: a restore you have tested, not only a number in a brochure.
  • Exit: deletion or return of data when the account closes.

The EuroVDC privacy policy is public. For contract wording beyond it, write to support@eurovdc.eu before you fill in a questionnaire, and keep the reply with your records. The residency side is covered in GDPR hosting in Sofia: a practical checklist, and the DNS evidence an auditor can query in NIS2: the DNS an auditor can query.

Steps for the shop team

  1. List which products share one account: web hosting, a VPS, corporate email.
  2. Record the nameservers. On EuroVDC they are usually ns1.eurovdc.eu and ns2.eurovdc.eu.
  3. Note who has panel access and how that is reviewed when staff leave.
  4. Write a three-name playbook: who opens the support ticket, who informs the customer, who approves a restore.
  5. Date and file every written answer from your providers.

If you are out of scope

Most small shops will not sit on the formal list, yet the same questions still arrive from buyers, insurers and marketplace onboarding teams. A clear answer on location, processor terms and incident timing removes friction from sales. Keeping hosting and mail with one EU provider also means one set of answers instead of four.

FAQ

Is this legal advice?

No. It is general information. Ask qualified counsel about scope and penalties.

Is every small shop in scope?

No. Sector, size and what you provide to others decide. Customers may still ask for evidence.

Does hosting in Sofia make me NIS2 compliant?

No. Location is one input. Risk management, incident handling, access control and written processor terms are separate duties.

What if the contract names no incident timing?

Ask in writing. A support response time and a security incident notice are different commitments.

Can mail and website sit with different providers?

Yes. Each provider then owes you its own answers on location, processor terms and incident contact. One stack keeps questionnaires shorter.

nis2 cybersecurity act bulgaria hosting contract gdpr sofia eurovdc

EuroVDC

Host Your Website with Confidence

NVMe SSD storage · Free SSL · DirectAdmin panel

View Web Hosting Plans

Was this article helpful?

– people found this helpful

Share on Social Media

NIS2 in Bulgaria: Is Your Shop in Scope?