Auditvault Pro.
Compliance

Does NIS2 Apply to You If You're Outside the EU? Scope, Costs and Timelines for Suppliers

Most non-EU firms aren't directly regulated by NIS2. Digital providers selling into the EU may need an EU representative, though, and almost every supplier to an EU operator will have to accept its clauses. This guide explains how to tell which path you're on and what each one costs.

Auditvault Pro editorial team · November 2026 · 11 min read

Two Ways NIS2 Reaches a Business Outside the EU

If you sell into the EU from London, Zurich, Bengaluru, Dubai or Toronto, NIS2 raises two separate questions. Many firms treat them as one. First, does the directive bind you directly, so that an EU authority can register you, supervise you and fine you? Second, if it doesn't, will your EU customers write its obligations into your contracts anyway? For most non-EU companies the first answer is no. The second answer is more and more often yes.

The difference shows up in your budget. Direct scope brings legal registration, sometimes an appointed EU representative, accountability for the management body and incident reporting to a national authority on a 24-hour clock. Indirect scope means security questionnaires, audit and notification clauses, and evidence of controls, usually at a level close to ISO/IEC 27001. On paper, the NIS2 requirements for non-EU companies look much the same on both paths. What differs is the cost, who you answer to and what happens when you get it wrong.

Advertisement

Run this triage before you pay for legal advice:

  • Do you have an EU subsidiary or branch? That entity may be in scope on its own, and linked-company rules can count group headcount and turnover toward the size threshold.
  • Do you offer digital infrastructure or digital services in the EU? That covers cloud, data center, content delivery, DNS, managed IT or managed security services, online marketplaces, search engines and social networks. If you offer any of these and have no EU establishment, you probably need an EU representative.
  • Neither, but you supply EU firms in energy, health, transport, finance, manufacturing, food, water, digital infrastructure or public administration? Then you're on the indirect path. Your obligations will come through supplier clauses, not from regulators.

Direct Scope: Sector, Size and the EU Representative Rule

NIS2 (Directive (EU) 2022/2555) covers entities in the sectors listed in Annex I (high criticality) and Annex II (other critical sectors). As a general rule it applies only to organizations above the small-enterprise threshold: roughly 50 or more employees, or annual turnover and balance sheet both above €10 million. A few categories are covered regardless of size, including DNS service providers, top-level domain registries and qualified trust service providers.

NIS2 is a directive, so each member state writes it into national law. Those national laws have arrived at different speeds and differ in detail. You comply with the law of the member state that has jurisdiction over you, not with the directive text alone.

Non-EU firms should pay most attention to the jurisdiction rule. Most entities are regulated in the member state where they're established. An Indian machinery maker that exports to Germany but has no EU entity isn't directly supervised under NIS2 just because it sells there. Article 26 makes an exception for a defined group of digital providers, which are regulated where their main establishment is. If one of these providers has no EU establishment but offers services in the EU, it must designate a representative in a member state where it operates, and that state takes jurisdiction. Without a representative, any member state where the company provides services can take enforcement action.

"Offering services in the EU" means more than having a website that people in the EU can reach. The recitals point to signs such as using an EU language or currency and actively targeting EU customers. This is the same logic GDPR uses.

Type of non-EU providerHow direct scope arisesEU representative needed with no EU establishment?
Cloud computing (which can include SaaS, depending on how the service is classified), data center, CDN, managed service provider, managed security service providerOffering services in the EU and meeting the size thresholdYes. The detailed technical measures in Implementing Regulation (EU) 2024/2690 also apply
DNS, TLD registry, domain registration servicesOffering services in the EU (DNS and TLD apply regardless of size)Yes. Regulation 2024/2690 also applies
Online marketplace, search engine, social networkOffering services in the EU and meeting the size thresholdYes. Regulation 2024/2690 also applies
Manufacturer, energy, logistics, food, chemicals, health supplierOnly through an EU subsidiary or branch that meets the thresholdsNo representative rule. Otherwise, pressure comes only through contracts

Direct scope carries real obligations. Article 21 requires risk-management measures covering incident handling, business continuity, supply chain security, secure development and vulnerability handling, cryptography, access control and multi-factor authentication. Article 23 sets the reporting timetable for significant incidents: an early warning within 24 hours, a notification within 72 hours and a final report within one month. Article 20 requires the management body to approve and oversee these measures and to complete training. Maximum fines must be at least €10 million or 2% of worldwide annual turnover, whichever is higher, for essential entities. For important entities the figures are €7 million or 1.4%. National laws can set them higher.

Indirect Pressure: What NIS2 Supply Chain Security Clauses Ask of Suppliers

Article 21 requires in-scope entities to manage the security of their direct suppliers and service providers. That includes each supplier's specific vulnerabilities and secure development practices. In practice, that duty becomes your contract. Supply chain security is how NIS2 reaches thousands of companies outside the EU that no regulator will ever contact.

Requests from EU customers tend to follow a familiar pattern:

  • A security questionnaire, often with a hundred or more questions, mapped to Article 21 or ISO 27001 Annex A
  • Evidence such as an ISO 27001 certificate, a SOC 2 Type II report or a recent penetration test summary
  • Notice of incidents that affect the customer, typically within 24 hours, so the customer can meet its own early-warning deadline
  • Multi-factor authentication on all access to customer systems and data, with privileged accounts named and logged
  • A vulnerability-handling commitment with patch windows by severity, and sometimes a software bill of materials
  • Audit rights, plus a requirement to pass the same terms down to your own subcontractors

Accept most of these. Push back on four:

  • Notification clocks with no trigger threshold, such as "within two hours of any suspected event." Offer 24 hours from confirming an incident that affects the customer's services or data.
  • Uncapped indemnity for the customer's regulatory fines. The fine is for the customer's own compliance failure. Offer a liability cap tied to fees, or a separate, higher cap for data and security breaches.
  • Unlimited on-site audits. Offer one audit a year with notice and let third-party certifications cover the rest.
  • Blanket obligations to "comply with NIS2." You can't comply with a law that doesn't apply to you. Commit to a specific schedule of controls instead.

Read your cyber insurance policy before you sign. Many policies exclude liability you take on by contract that you wouldn't otherwise have, so a broad indemnity can leave you uninsured. If the customer is a bank or insurer, expect terms driven by DORA instead. For financial entities DORA takes precedence over NIS2, and it sets its own contractual requirements for ICT providers.

Scenarios for UK, Swiss, Indian, Gulf and North American Firms

United Kingdom

Since Brexit, NIS2 is a cross-border question for UK companies. At home, UK firms remain under the NIS Regulations 2018. The Cyber Security and Resilience Bill, introduced in Parliament in late 2025, would extend that regime to managed service providers and data centers, so check how far it has progressed. Hypothetical example: a 120-person UK managed service provider has clients in Ireland and the Netherlands and no EU entity. It's a strong candidate for an EU representative in one of those two countries. It would then follow that country's NIS2 law and Regulation 2024/2690, and its UK obligations would still apply on top.

Switzerland

Since April 2025, Swiss critical infrastructure operators have had to report cyberattacks to the Federal Office for Cybersecurity within 24 hours. That overlaps with NIS2 but doesn't replace it. Swiss exposure usually comes through EU subsidiaries. Hypothetical example: a Swiss medical device maker has a 40-person German sales company. Group figures may push that company over the size threshold. Whether it counts as "manufacturing" depends on what it actually does, though, and a sales-only subsidiary may fall outside the sector. A local scoping opinion is worth paying for on a question like this.

India

Indian IT services and managed service exporters have the most direct exposure. Many run EU subsidiaries that likely qualify as managed service providers, and large ones may be classed as essential entities. Expect the subsidiary's obligations to extend to services it delivers from offshore delivery centers. CERT-In's six-hour reporting rule is stricter than NIS2's 24 hours, so build a single incident runbook around the shorter deadline.

Gulf states

Firms in the UAE and Saudi Arabia usually already work under national frameworks, such as the Saudi National Cybersecurity Authority's Essential Cybersecurity Controls. Gulf cloud and data center operators that actively serve EU customers fall under the representative rule. Logistics, energy services and engineering firms are mostly on the indirect path, through contracts with EU ports, utilities and manufacturers.

North America

US and Canadian SaaS companies may fall within the definition of a cloud computing service. Hypothetical example: a 300-person Canadian SaaS vendor with EU customers and no EU entity needs a representative. Add a 15-person Irish sales office and the analysis changes. If security decisions aren't taken in the EU, the main-establishment test looks to where security operations are carried out, and then to the EU establishment with the most employees. Ireland could become the vendor's home regulator even though the security team sits in Toronto.

Indicative Costs and Timelines for Each Path

These figures are typical 2026 market ranges in USD. They vary by contract, company size and country. Consulting rates in India, for instance, are well below those in Switzerland or the UK. Confirm with vendors before you budget.

ItemTypical 2026 range (USD)Realistic timelineWho needs it
Legal scoping opinion (sector, size, jurisdiction)$5,000–$30,0002–6 weeksAnyone with an EU entity or digital services sold into the EU
EU representative service$5,000–$30,000 per year2–6 weeks to appointNon-EU digital providers without an EU establishment
Registration with the national authorityMostly internal effortA few weeks, depending on the national portalDirectly in-scope entities
Gap assessment against Article 21 or Regulation 2024/2690$15,000–$75,0004–10 weeksDirect scope; also useful on the indirect path
Incident reporting runbook plus tabletop exercise$8,000–$40,0004–8 weeksBoth paths
First ISO 27001 certification, mid-size firm$40,000–$150,000 including consulting and audit6–12 monthsThe strongest evidence on the indirect path; supports direct scope
24/7 managed detection and response$40,000–$250,000 per year1–3 months to onboardAnyone who must meet a 24-hour clock
Management body training$3,000–$15,000 per yearAbout a day, repeatedDirect scope

Two hypothetical examples show how far apart the paths are. Say an 80-person supplier in Pune already holds ISO 27001 and is only on the indirect path. Its first-year spend goes mostly on questionnaire handling, contract review and a reporting runbook: roughly $20,000–$60,000, plus a quarter to half of one person's time answering customers.

Now say a 150-person non-EU managed service provider is directly in scope, has no certification and needs a representative. Scoping, the representative, a gap assessment, remediation, managed detection and training could total $150,000–$500,000 in year one. Remediation is likely to take 9–18 months. Supervisors won't accept that timeline unless they can see a documented plan.

A 90-Day NIS2 Compliance Checklist for Non-EU Suppliers

This checklist assumes you're starting from scratch. The order makes sure you don't spend on remediation until you know which path you're on.

  1. Days 1–10: List every EU entity, EU customer and service line. Map each service against the Annex I and II categories and the Article 26 digital-provider list.
  2. Days 10–30: Get a scoping opinion from counsel licensed in a relevant member state. Ask three questions: is any entity directly in scope, which state has jurisdiction, and are you essential or important?
  3. Days 20–40: If you need a representative, compare at least three providers. Confirm which member state they'd act in, that they'll handle correspondence with the authority, and how they escalate during an incident. Then register with the competent authority.
  4. Days 30–60: Run a gap assessment against Article 21, and against Regulation 2024/2690 if you're a digital provider. Fix MFA, backups and incident logging first. They cost little, and assessors usually check them first.
  5. Days 45–75: Write one incident reporting runbook built around your shortest legal deadline. That might be CERT-In's six hours, Switzerland's 24 hours or NIS2's 24/72-hour sequence. Test it with a tabletop exercise.
  6. Days 60–90: Build a standard security pack and contract position for EU customers: certifications, a controls schedule, a 24-hour notification commitment and liability caps. Brief your management body and record their approval.
  7. Day 90: Ask your broker whether your cyber policy covers regulatory investigations, contractual indemnities and fines in places where the law allows fines to be insured.

The decision rule: if you're a digital provider with EU customers and 50 or more staff, treat yourself as directly in scope until a lawyer tells you otherwise. Everyone else should put money into evidence, meaning ISO 27001 and a tested incident process, before building regulatory machinery they may never need.

Questions buyers ask

Can our GDPR Article 27 representative also act as our NIS2 EU representative?

They're separate legal appointments under different laws, so having a GDPR representative doesn't satisfy NIS2. Some providers offer both services. If you use one provider for both, make sure the contract names the NIS2 role explicitly and that the representative is based in a member state where you actually offer the relevant services.

Is there an official NIS2 certification we can show customers?

No single NIS2 certificate exists. ISO/IEC 27001 maps closely to Article 21 and is the evidence EU buyers most often accept. SOC 2 Type II is common for SaaS. Member states can require specific EU cybersecurity certification schemes for certain products or services, so check the national law that applies to you.

What happens if a non-EU provider that needs a representative never appoints one?

Any member state where you provide services can take enforcement action, so you lose the ability to deal with a single regulator of your choosing. Maximum fines for essential entities must be at least €10 million or 2% of worldwide annual turnover, whichever is higher. Authorities can also issue binding instructions, and in serious cases essential entities can face measures aimed at management. Get advice from counsel licensed in a relevant member state on your specific exposure.

Will our cyber insurance pay NIS2 fines?

That depends on the policy wording and on whether fines can legally be insured in the relevant country, which varies across jurisdictions. Many policies cover regulatory fines only "where insurable by law," and they tend to cover investigation costs more reliably than the fines themselves. Have a licensed broker confirm both points before you rely on that cover.

Written by the Auditvault Pro editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.