An email apparently sent by a member of CECCAR, the Romanian body of chartered accountants, an attachment opened by an employee, a laptop encrypted with BitLocker. That is one of the ransomware cases described by Romania’s National Cyber Security Directorate (DNSC) in its 2025 report, at a Romanian electrical installation company. The attackers asked for 12,000 lei, then 15,000. The company did not pay and rebuilt its system from backup. But the backup was about two months old.
For most small companies, cybersecurity is not about sophisticated technology but about a few basics done on time and checked. This guide to cybersecurity for SMEs puts them in one place: whether NIS2 applies to you, the 10 minimum measures you apply anyway, with measurable thresholds, what funding exists right now, and a 25-point checklist.
Why cybersecurity matters for an SME
- DNSC annual report for 2025: reported phishing incidents rose by 70.6%, from 2,917 to 4,975, and account compromises by 353%, from 248 to 1,125. Ransomware grew by more than 153% compared with 2024 and hit, among others, 119 legal entities that DNSC supported.
- ENISA Threat Landscape 2025, based on 4,875 incidents from July 2024 to June 2025: phishing is the leading intrusion vector, at about 60% of cases, followed by vulnerability exploitation, at 21.3%.
- Eurostat: in 2023, 21.54% of EU enterprises covered by the survey suffered consequences of ICT security incidents. In 2024, only 35.50% had documents setting out ICT security measures, practices or procedures.
The figures call for care: DNSC notes that part of the rise in fraud comes from better reporting, and Eurostat also counts unavailability caused by hardware or software failures (18.0%), not only attacks. The practical conclusion stands: roughly one company in five had an ICT security problem with real consequences in a single year, and almost two in three had nothing written down about how they defend themselves. The mechanism is always mundane: an email account without a second factor, a reused password, an unpatched server, a backup that was never test-restored.
Does NIS2 apply to you? A three-step check
In Romania, the NIS2 Directive (Directive (EU) 2022/2555) was transposed by Government Emergency Ordinance (OUG) 155/2024, approved with amendments by Law 124/2025, in force since 10 July 2025. The ordinance covers entities in the sectors listed in annexes 1 and 2, established in Romania, that pass a size threshold or fall under an exception. Companies in other EU countries should apply the same logic to their own national transposition.
Step 1: the size threshold
Article 8 of OUG 155/2024 refers to Law 346/2004, article 4, which follows the definition in Recommendation 2003/361/EC. Amounts are in euro, or the equivalent in lei.
| Category | Employees | Net turnover | Total assets | NIS2 |
|---|---|---|---|---|
| Micro-enterprise | up to 9 | up to €2m | or up to €2m | Generally not, except for step 3 |
| Small enterprise | 10–49 | up to €10m | or up to €10m | Generally not, except for step 3 |
| Medium-sized enterprise | 50–249 | up to €50m | or up to €43m | Important, in the sectors of annexes 1 and 2 |
| Large enterprise | above the medium criteria | above the medium criteria | above the medium criteria | Essential in annex 1, important in annex 2 |
Note: the ordinance explicitly excludes only art. 4^5 of Law 346/2004, on companies controlled by public bodies. If your company belongs to a group, also check that law’s rules on partner and linked enterprises.
Step 2: the sector
Annex 1: energy, transport, banking, financial market infrastructure, health, drinking water, waste water, digital infrastructure, ICT service management (business-to-business), public administration, space. Annex 2: postal and courier services, waste management, chemicals, food, manufacturing, digital providers, research. Each sector has subsectors and entity types, which you check in the text of the law.
Step 3: the exceptions that catch small companies too
- Essential regardless of size: DNS service providers, TLD name registries, qualified trust service providers, central public administration, critical entities (art. 5(1)).
- Important regardless of size: providers of public electronic communications networks and services, and trust service providers (art. 6(2)).
- Medium-sized companies that provide managed security services or public electronic communications are essential (art. 5(3) and (4)).
- DNSC can designate a company of any size, for instance if it is the sole provider of an essential service (art. 9).
- You can also register voluntarily (art. 18(17)). And entities in scope must take into account the security of their direct suppliers (art. 11(8)), so NIS2 reaches small companies through contracts.
Essential or important: what changes
| Criterion | Essential entity | Important entity |
|---|---|---|
| Who, as a rule | large companies in annex 1, plus the exceptions in art. 5 | large and medium companies in annexes 1 and 2 not classed as essential |
| DNSC registration decision | within 60 days of notification | within 150 days of notification |
| Remediation plan after self-assessment | mandatory, within 30 days | not required by art. 12(5) |
| Maximum fine for measures, audit, reporting | €10m or 2% of worldwide turnover | €7m or 1.4% of worldwide turnover |
Your obligations, with deadlines
| Obligation | Deadline | Legal basis in OUG 155/2024 |
|---|---|---|
| Notifying DNSC for entry in the register (name, contacts, sector, public IP ranges, etc.) | at most 30 days from the date the ordinance applies to you | art. 18(2) and (3) |
| Appointing the person responsible for network and information system security | 30 days from notice of the DNSC decision | art. 14(3) |
| Risk level assessment, under DNSC Order 2/2025 | 60 days from notice of the decision | art. 18(6) |
| Self-assessment of the maturity of measures | 60 days after the risk assessment, then yearly | art. 18(7), art. 12(4) |
| Remediation plan (essential entities only) | 30 days after the self-assessment | art. 12(5) |
| Technical and organisational measures approved by management; training for management and staff | ongoing | art. 11, 13 and 14 |
| Reporting significant incidents through the PNRISC platform: early warning, notification, final report | 24 hours, 72 hours, at most one month after notification | art. 15(2) and (7) |
| Cybersecurity audit, only by DNSC-certified auditors | conditions and frequency set by DNSC order, based on risk level | art. 11(5), art. 58 |
For a company that comes into scope now, for example because it passed 50 employees, the 30 days run from the date the provisions start to apply to it. DNSC has not yet published an audit frequency. At the end of 2025 it supervised 644 essential and 34 important entities. The preparation steps are covered in the NIS2 compliance guide for SMEs and the DNSC audit readiness check.
Minimum measures do not depend on NIS2
This is the most expensive misconception: if the law does not cover me, I have no obligations, so I have no risks either. But the DNSC cases cited here, the email “from CECCAR” and the €20,148 transferred to attackers, have nothing to do with the register of entities. Phishing, stolen passwords and untested backups hit a company of 8 people and one of 800 in the same way.
The attacker does not check whether your company is in the DNSC register. They check whether your email opens without a second factor.
Article 13 of OUG 155/2024 lists ten minimum areas of measures. Implementing Regulation (EU) 2024/2690 details them for digital providers (DNS, cloud, data centres, managed services and others), and CIS Controls group 56 essential cyber hygiene safeguards in IG1, designed for small and medium organisations with limited IT expertise. The ten measures below are their common core. The measurable thresholds are our recommendations for an SME, not legal requirements: the law says what must exist, usually without numbers (“within a reasonable time”).
The 10 minimum cybersecurity measures for any SME
1. Multi-factor authentication (MFA)
Account compromises reported to DNSC grew more than fourfold in a year. For the electrical installation company, DNSC’s first recommendation was MFA.
- What you do: MFA on email, VPN and any remote access, on administrator accounts and on cloud applications holding business data. An authenticator app or a hardware key, not SMS.
- Threshold: 100% of administrator accounts and remote access; 95% of email accounts within 30 days, 100% within 90 days.
- Framework: OUG art. 13(j); Regulation 2024/2690, points 11.7 and 11.3; CIS Control 6.
2. 3-2-1 backup, tested by restoring
The backup in the opening case avoided a ransom payment, not the loss of two months of work. According to Eurostat, 77.09% of small EU enterprises back up to a separate location or the cloud; more than one in five do not.
- What you do: three copies, on two types of media, one outside the network, offline or immutable, which a compromised domain account cannot delete. Details in the 3-2-1-0 backup guide.
- Threshold: critical data at most 24 hours old (RPO); a full restore tested and timed (RTO) at least every three months.
- Framework: OUG art. 13(h); Regulation 2024/2690, point 4.2 (copies outside the system’s network, integrity checks, restore tests); CIS Control 11.
3. Security updates with a fixed deadline
Vulnerability exploitation is the second way in at ENISA, at 21.3%. What matters most is what can be seen from the internet: VPN, firewall, email, website.
- What you do: automatic updates on workstations, a monthly window for servers, priority for exposed systems, replacing those out of support. For Linux servers exposed to the internet, Sentinel, our product, provides real-time protection and prioritises what to fix first.
- Threshold: critical fixes on exposed systems within 14 days at most, the rest within 30 days; zero unsupported systems, or isolated and recorded in the risk register.
- Framework: OUG art. 13(e); Regulation 2024/2690, point 6.6 (patches applied “within a reasonable time”, tested, from trusted sources); CIS Control 7.
4. Inventory of equipment and services
Almost every assessment finds something forgotten: a test server, a cloud account of a former employee, a router manageable from the internet.
- What you do: a list of equipment, software, cloud services and everything that answers from the internet, each with a named owner.
- Threshold: 100% of devices accessing company data are on the list; quarterly review.
- Framework: OUG art. 11(7) and art. 13(f); Regulation 2024/2690, point 12.4; CIS Controls 1 and 2.
5. Minimal accounts and rights
An administrator who reads email with the administrator account turns any wrong click into a network-wide incident. DNSC explicitly recommended limiting privileged accounts.
- What you do: separate administrator accounts, used only for administration; no shared accounts; leavers’ accounts closed the same day, including in the cloud.
- Threshold: deactivation within 24 hours of departure; quarterly review of rights; every domain administrator account justified by name.
- Framework: OUG art. 13(f); Regulation 2024/2690, point 11.3 (dedicated accounts, restricted privileges); CIS Controls 5 and 6.
6. Email: SPF, DKIM, DMARC and forwarding
At an industrial company with 375 employees, attackers compromised two email addresses, set up forwarding and altered documents in conversations. The result, according to DNSC: unauthorised transfers of €20,148.
- What you do: SPF and DKIM on every domain that sends email; DMARC started at p=none with aggregate reports, then p=quarantine and p=reject. Automatic forwarding to outside addresses blocked or alerted. Any bank account change received by email is confirmed by phone.
- Threshold: SPF and DKIM on 100% of domains; DMARC at least at p=quarantine within 90 days; zero unapproved external forwarding rules.
- Framework: RFC 9989, the IETF standard for DMARC; CIS Control 9.
7. Protection on workstations and servers
In the €20,148 case, DNSC found numerous spyware and infostealer programs on the systems. An antivirus installed and forgotten is not enough: alerts must reach a person.
- What you do: centrally managed endpoint protection, disk encryption on laptops, macros blocked in documents from outside.
- Threshold: 100% of devices reporting to the console in the last 7 days; critical alerts analysed the same working day; 100% of laptops encrypted.
- Framework: OUG art. 13(c) and (i); CIS Control 10.
8. Anti-phishing training, measured
According to DNSC, phishing remained the main attack vector in 2025, with messages written in correct Romanian and the branding of legitimate organisations.
- What you do: short training at hiring, a yearly refresher, phishing simulations and a simple way to report suspicious messages.
- Threshold: 100% of new hires trained in their first week; one simulation per quarter; the reporting rate tracked, not just the click rate.
- Framework: OUG art. 13(i) and art. 14(2); CIS Control 14.
9. Incident response plan
Most is lost in the first hours: deleted logs, rebooted systems, decisions made in a hurry.
- What you do: 1–2 pages, also kept on paper: who decides, who isolates systems, whom you call (IT provider, bank, insurer, DNSC), what you keep as evidence. If NIS2 applies, include the 24-hour, 72-hour and one-month deadlines; otherwise, you can report voluntarily.
- Threshold: one 60–90 minute tabletop exercise a year; contacts checked quarterly; plan updated within 30 days after each incident.
- Framework: OUG art. 13(g), art. 15 and 16; Regulation 2024/2690, point 3 (including testing of procedures); CIS Control 17.
10. Suppliers with access to your systems
The external IT firm, the ERP vendor, the agency running the website all have access, often through a shared account without MFA. And for your clients in scope of NIS2, you are such a supplier.
- What you do: a list of suppliers with access; named accounts with MFA; clauses on incident notification and on revoking access at the end of the contract.
- Threshold: 100% of suppliers with remote access on the list, with named accounts; the notification clause in all new contracts; yearly review.
- Framework: OUG art. 11(8) and art. 13(d); Regulation 2024/2690, point 5.1; CIS Control 15.
An outside assessment of these ten points, with a gap report and a remediation plan, is what we do in our cybersecurity service. For companies in scope of OUG 155/2024 there is preparation for the NIS2 / DNSC audit, and for backup and tested restores, backup and continuity. Our founder holds the DNSC specialisation for cybersecurity auditors; DNSC certification is in progress, so the official audit report is signed by a certified auditor.
Cybersecurity grants and funding in 2026
As of 8 November 2026, the public funding calls for SME cybersecurity in Romania that we found are tied to the Cyber Resilience Act (CRA, Regulation (EU) 2024/2847), meaning products with digital elements. If your company has no hardware or software product of its own on the market, the calls below probably do not fit.
NCC-RO, Call 1 “Financial support for CRA compliance”
| Item | What the applicant guide of 30.10.2026 says |
|---|---|
| Status on 8.11.2026 | final guide published; the call is not open yet |
| Submission | 30.11.2026, 10:00 – 01.02.2027, 16:59:59, on the NCC-RO platform; times confirmed at launch |
| Budget | €2,000,000: half EU funds (Digital Europe Programme), half state budget |
| Funding | up to 75%, at most €45,000 per SME; own contribution at least 25%, plus VAT |
| Who applies | a specialised cybersecurity provider, leading a consortium with 3–5 SMEs |
| What it funds | initial assessment and preparation for CRA compliance: gap analysis, vulnerability assessment, penetration tests where applicable, training |
| What it does not fund | remediation, certification, licences, equipment |
| Duration and form | at most 6 months; de minimis aid, granted to the SME as services |
SECURE, the European call for SMEs and the CRA
The European SECURE project, funded through the Digital Europe Programme, has its second call open from 1 October to 11 December 2026: €11.5 million in total, at most €30,000 per grant, 50% co-funding, for SMEs improving their CRA compliance. According to annex 1 of the application guidelines, SMEs established in EU or EEA member states can apply, Romania included; the Romanian Authority for Digitalisation, which houses NCC-RO, is a consortium partner, and the national coordination centre checks the company’s eligibility.
Amounts and deadlines are those published on the date of this article. Check the current call on the official NCC-RO page and on the SECURE website. We found no open programme right now that funds the general measures in this guide for any SME.
NIS2 penalties and the cost of doing nothing
| Offence (OUG 155/2024, art. 60) | Important entity | Essential entity |
|---|---|---|
| Missing risk management measures (letter a), not submitting to the audit (b), management not supervising or not training (g, h), not reporting incidents (l) | 5,000 lei – €7m or 1.4% of worldwide turnover | 10,000 lei – €10m or 2% of worldwide turnover |
| Not notifying DNSC for registration on time (letter o) | 1,000 – 300,000 lei | 1,500 – 500,000 lei |
There is no official Romanian statistic on the average cost of an incident at an SME, so we do not make one up. The DNSC 2025 report does describe cases with amounts.
| What happened | Documented cost | Measures that address the scenario |
|---|---|---|
| Electrical installation company: attachment from an email “from CECCAR”, device encrypted | ransom demanded of 12,000, then 15,000 lei; not paid, restore from a backup about two months old | 1, 2, 5, 8 |
| Industrial company with 375 employees: compromised mailboxes, forwarding, altered documents | unauthorised transfers of €20,148 | 1, 6, 7 |
| Essential or important entity that does not notify DNSC | fine of up to 300,000 lei (important) or 500,000 lei (essential) | the three-step NIS2 check |
Checklist: 25 points
The list below is also available as a one-page printable PDF, for the meeting with management or with your IT provider.
Tick what is true today, not what is planned. Every unticked point becomes a task with an owner and a deadline.
Governance and NIS2
- We have checked in writing whether the company falls under OUG 155/2024: size, sector in the annexes, exceptions.
- If we are in scope, we have notified DNSC and we know the notification date.
- Management has approved the security measures in writing and appointed an internal owner.
- We know the reporting deadlines: 24 hours, 72 hours, one month.
Identities and access
- MFA active on all email accounts.
- MFA active on VPN, remote access and administrator accounts.
- Administrator accounts are separate and used only for administration.
- Leavers’ accounts are closed within 24 hours at most.
- We review every quarter who has access to what.
Data and backup
- Critical data has three copies, on two types of media, one outside the network.
- The offline or immutable copy cannot be deleted with a domain account.
- We have tested a full restore in the last three months and timed it.
- We know how old restored data can be (RPO) and how fast we recover (RTO).
Systems
- We have a complete inventory of equipment, software and internet-exposed services.
- Critical fixes on internet-exposed systems are installed within 14 days at most.
- We have no systems without vendor security support, or they are isolated and documented.
- All laptops, workstations and servers have active, monitored endpoint protection.
- All laptop disks are encrypted.
Email and people
- SPF, DKIM and DMARC are configured, with DMARC at least at p=quarantine.
- Automatic forwarding to external addresses is blocked or raises an alert.
- Payments and bank account changes requested by email are confirmed by phone.
- Every new employee completes anti-phishing training in their first week.
Incidents and suppliers
- We have a 1–2 page incident response plan, printed and tested yearly.
- Emergency contacts (IT provider, bank, insurer, DNSC) are also kept offline.
- We have a list of suppliers with access to our systems, with named accounts and incident notification clauses.
Conclusion
An SME’s cybersecurity does not start with the question “does NIS2 cover us?” but with “what happens tomorrow if someone steals one of our email accounts?”. The law decides who reports to DNSC; attackers make no such distinction. Ten measures, each with a threshold you can check, cover the scenarios that appear most often in official reports. If you want to go through the checklist together and find out what to do first, let us talk for 30 minutes.
Sources
- Government Emergency Ordinance (OUG) no. 155/2024 establishing a framework for the cybersecurity of networks and information systems in the national civil cyberspace, Government of Romania, 30.12.2024, consolidated text: art. 5, 6, 8, 9, 11–16, 18, 58, 60 and annexes 1–2, with the amendments of Law 124/2025 (in Romanian).
- Law no. 346/2004 on stimulating the establishment and development of small and medium-sized enterprises, Parliament of Romania, updated text: art. 4(1), size thresholds (in Romanian).
- Commission Recommendation 2003/361/EC concerning the definition of micro, small and medium-sized enterprises, European Commission, 6.05.2003: annex, art. 2.
- DNSC Order no. 2/2025 on the criteria for service disruption and the methodology for assessing the risk level of entities, DNSC, 11.08.2025 (in Romanian).
- Commission Implementing Regulation (EU) 2024/2690, 17.10.2024: annex, points 3, 4.2, 5.1, 6.6, 11.3, 11.7 and 12.4.
- DNSC Annual activity report 2025, DNSC, approved by CSAT Decision no. 117/07.08.2026: pp. 5 and 7–8 (statistics), pp. 11–13 (cases), supervised entities (in Romanian).
- ENISA Threat Landscape 2025, ENISA, press release of 1.10.2025: intrusion vectors and the sample of 4,875 incidents.
- ICT security in enterprises, Eurostat, data from December 2024 and Eurostat news release of 11.02.2025.
- CIS Controls v8.1, Implementation Group 1, Center for Internet Security and the list of the 18 controls.
- RFC 9989, Domain-Based Message Authentication, Reporting, and Conformance (DMARC), IETF, 2026.
- Applicant guide for Call 1 “Financial support for CRA compliance”, NCC-RO, 30.10.2026 and Funding opportunities page, NCC-RO (in Romanian).
- SECURE Second Open Call, SECURE consortium, Digital Europe Programme, 1.10–11.12.2026.