Why US incorporation does not decide the question
NIS2 identifies entity types and services rather than simply listing countries of incorporation. A US provider can have EU subsidiaries or offer certain covered services into the Union without establishing a subsidiary there. Each arrangement needs a structured review under Articles 2 and 26. A US headquarters does not automatically exclude the relevant entity, but an EU customer list by itself also does not establish applicability.
Begin with services, contracting entities and the systems used to provide them. Map them to the Directive’s annexes and consider special inclusion provisions before assessing classification.
EU subsidiaries and related-company calculations
When a US corporate group has EU operating subsidiaries, the services of those subsidiaries require an entity-by-entity review. The EU SME definition may aggregate partner or linked-enterprise information, making it unsafe to use only an EU subsidiary’s local staff count. Group ownership, voting rights and consolidated financial data need to be documented.
Separate the entity whose service is assessed from the enterprises whose data are incorporated into its size test. This helps prevent inconsistent conclusions across a complex corporate group.
Cloud and managed service provider examples
Cloud computing services, data centre services, managed services and managed security services are among the specific Article 26(1)(b) categories. Their jurisdictional treatment differs from that of many other covered entities. Under Article 26(2), a provider’s main EU establishment is based first on where cybersecurity risk-management decisions are predominantly taken, followed by statutory fallback criteria.
A US business that merely uses cloud software for its own operations is not automatically a cloud computing service provider under NIS2. The provider definition and actual customer-facing activity matter.
Representative obligations without EU establishment
For an entity covered by Article 26(1)(b) that is not established in the Union but offers services there, Article 26(3) calls for appointment of a representative in a Member State where services are offered. The appointed country provides a jurisdictional link for that rule. Failing to appoint a required representative does not guarantee immunity from enforcement actions.
Evaluate the relevant national implementing law and registration processes before deciding how a representative relationship should be documented.
Evidence, controls and reporting
A US company’s EU assessment should retain an entity-service matrix, sector and scope reasoning, staff and financial data, organisational chart, decision-making locations, applicable Member State laws and any representative appointment. If covered, connect the resulting classification to management responsibilities, proportionate cybersecurity risk measures and significant-incident notification procedures.
National law and guidance may develop over time. Review official sources periodically and keep proposed EU changes clearly separate from enacted obligations.
Questions on the text
Does operating a US website accessible in Europe automatically trigger NIS2?
No. Accessibility alone is not a general scope test. The defined service and relevant legal provisions must be examined.
Can a US provider be subject to NIS2 without an EU office?
Yes, for relevant provider types and conditions, including the Article 26(3) representative framework.
Are all US technology companies treated identically?
No. Services, entity structure, applicable exceptions and jurisdiction rules produce different outcomes.