NIS2 for online marketplaces, search engines and social networks

NIS2 covers online marketplaces, search engines and social networks as Annex II digital providers. This page explains the definitions, important status, EU-level requirements, registration and who must act.

On this page

Does NIS2 apply to our online marketplace, search engine or social network?

NIS2 covers online marketplaces, online search engines and social networking services platforms as digital providers in Annex II, and they are normally important entities unless a Member State designates them as essential. A platform team asked by a customer or regulator whether NIS2 applies should therefore start from the service definitions, not from company size or sector labels alone. The answer depends on three questions: whether the service fits one of the three definitions, which Member State is the main establishment in the Union, and how many EU users the service reaches. Confirm the first point against the legal text in Article 6 and the definitions the Directive borrows from Directive 2005/29/EC and Regulation (EU) 2019/1150, because a service that only resembles a marketplace or a social feature may fall outside the category.

For a social networking services platform, NIS2 uses a specific definition: a platform that lets end-users connect, share, discover and communicate with each other across multiple devices, in particular through chats, posts, videos and recommendations. Map each product surface against that list, including messaging, comments, group features and recommendation feeds, and record the reasoning. Ask counsel to confirm the national transposition law for the Member State where the company is established, since that law names the competent authority and may set the designation of essential status. Entities that operate across several Member States should also check where their main decisions on cybersecurity risk are taken, because that location, under Article 26, determines which national authority supervises them.

NIS2 creates no certificate of compliance. National competent authorities oversee compliance through inspections, security audits, security scans, information requests and administrative fines, so there is no document that proves compliance to a customer. Plan instead for evidence that a supervisor could test: a documented scope decision, the risk-management measures in Article 21 applied to the platform, and records showing how the organization meets the EU-level requirements in Implementing Regulation (EU) 2024/2690. An independent auditor can test controls and report on them, but only the national authority decides whether the entity complies with NIS2.

Which platform features trigger the scope question

NIS2 does not ask whether a product looks like a marketplace or a social network. It asks whether the service falls within the Annex II definitions and how many EU users rely on it. The features below are the ones that most often prompt a documented scope review, and each one needs a decision owner and a written rationale.

Third-party seller listings

Platforms where independent sellers list and sell goods or services to consumers resemble the online marketplace definition, which draws on the consumer protection and platform-to-business rules the definition cross-refers to. Check whether the platform enables contracts between traders and consumers, who sets the listing terms, and whether the platform intermediates payment or only displays offers. Legal counsel should record the reasoning, and the management body should approve it.

Ranking and search of content

A service that lets users query a large body of content and returns ranked results may fall under the online search engine definition, which takes its meaning from Regulation (EU) 2019/1150. Check whether the core function is searching across third-party sites or content, and whether the service is only an internal search box on a product that falls under another category. The answer depends on how the service is described in the legal definition, so confirm it with counsel rather than assume.

User-to-user sharing and messaging

The NIS2 definition of a social networking services platform centers on enabling end users to connect, share, discover and communicate with each other, in particular through chats, posts, videos and recommendations. Review each feature separately, since direct messaging, public posts and group channels may be assessed differently. Record which features are in the product, which are roadmap items, and how they are weighted in the scope decision.

Recommendation feeds

Personalized feeds that suggest content or connections to users are a strong signal that a service is built around the social networking model. Recommendation logic is also a point where a product team may change the service without a compliance review. Check whether feeds are generated from user activity, whether they surface other users' content, and whether any change to ranking is routed through the same scope review as new features.

Multi-device access

The definition refers to users connecting across multiple devices, so web, mobile and desktop access to the same user-facing service is a relevant fact in the analysis. Multi-device use alone does not settle scope, but it confirms that the service reaches users in the way the definition describes. Document which clients exist, which sign-in methods they use, and how the service is offered to users in each Member State.

EU user base and main establishment

Two counts drive the next steps: the number of EU users, which sets the significance thresholds for unavailability, and the Member State of main establishment, which sets the supervisor and registration duty. Confirm how EU users are counted, over what period, and whether the figures are reported internally. Where the company has no EU establishment, check the representative duty before the first service is offered in the Union.

Important or essential status and the Member State that supervises

Online marketplaces, online search engines and social networking services platforms are listed in Annex II of NIS2, the sectors of other critical importance. Under Article 3, entities in Annex II are treated as important entities by default. That means they face the same Article 21 risk-management duties and Article 23 reporting duties as essential entities, but their supervision is ex post, meaning authorities act after a problem appears rather than through routine pre-approval of the controls. The definitions for these services come from outside NIS2: online marketplaces and online search engines take their meaning from Directive 2005/29/EC and Regulation (EU) 2019/1150, while social networking services platforms are defined in Article 6(33).

  • Default status: Annex II providers are in scope as important entities unless a Member State classifies them as essential.
  • Ex post supervision: Authorities typically act on evidence after an incident, a complaint or a request for information.
  • Same duties: Important status does not lower the Article 21 measures or the Article 23 reporting clock.
  • Definitions matter: Check whether your service meets the legal definition of a marketplace, search engine or social platform before assuming it is in scope.

Confirm with your national competent authority or legal counsel whether your service falls under one of these definitions and how your Member State has transposed Article 3.

What the EU-level technical requirements ask of platform providers

For online marketplaces, search engines and social networks, the technical detail behind the Article 21 measures sits in *Commission Implementing Regulation (EU) 2024/2690*, adopted on 17 October 2024 and published on 18 October 2024. The regulation sets the technical and methodological requirements for the Article 21(2) measures and the significant incident criteria for online platforms, alongside DNS, TLD, cloud, data center, CDN, managed service and trust service providers. Your organization's obligations under NIS2 are the Article 21 duties, but this regulation is where a supervisor will look for the specific expectations that apply to a platform. Read the Annex itself, section by section, and map each requirement to a named owner, a control and a piece of evidence. Summaries, including vendor blogs and consultant decks, often compress or drop conditions that matter for a platform's architecture, so treat them as reading aids rather than sources.

The European Union Agency for Cybersecurity (ENISA) published non-binding *NIS2 Technical Implementation Guidance* on 26 June 2025. It gives examples of the evidence that can show compliance with the regulation and maps its requirements to ISO/IEC 27001:2022 and NIST CSF 2.0. Those mappings are useful for building one control set that serves both NIS2 and an existing ISO 27001 or NIST program, but they are not a substitute for the regulation text. Confirm with your national competent authority, and with your legal counsel, how the Annex is being applied in the Member State of your main establishment, because national transposition laws can add detail. Before you commit budget to a control set, ask any implementation partner to show which Annex requirements each proposed control addresses and which ENISA examples of evidence it will produce.

How a platform team gets from scope question to evidence ready

This sequence takes a marketplace, search engine or social network from an open scope question to a documented position on its NIS2 status, jurisdiction and registration, and a body of evidence a national authority can test. Each phase closes with a named output that the next phase depends on.

  1. Confirm the service definitions with counsel

    Counsel compares each service against the NIS2 definitions for social networking services platforms and against the definitions for online marketplaces and online search engines, which the Directive takes from existing EU consumer and platform-to-business law. The team supplies a feature inventory covering chats, posts, recommendations, seller listings and search indexing, so counsel can say which offerings fall inside Annex II point 6. The output is a short written scope memo that names each service in or out and records the reasoning. Done means the product, legal and security leads have signed off on the same list of services.

  2. Confirm the entity type and important status

    Once the service list is fixed, the team confirms that the company is an Annex II digital provider and checks whether any Member State has identified it as essential under the exceptions in Article 3. In most cases these entities are important entities, which carry ex post supervision, but the national transposition law of each relevant Member State decides the final classification. The output is a classification note that records the assumed status and the national law it relies on, to be reconfirmed when that law changes. Done means the note is reviewed by counsel and held with the governance records.

  3. Establish the main establishment and Member State

    The team determines where decisions on cybersecurity risk management are taken in the Union, and where operations are carried out, because Article 26 assigns jurisdiction to the Member State of main establishment for these providers. Where the company has no establishment in the Union but offers services there, it must identify the Member States where it offers services. The output is a jurisdiction memo that names the competent Member State and the reasoning, plus a list of other Member States where services are offered. Done means management has approved the memo, since it determines which national authority receives the registration and reports.

  4. Complete registration and appoint the EU representative

    The company submits the registration information the competent Member State requires under Article 27, which applies to these providers from the date set in the Directive. If the company is listed in Article 26 but is not established in the Union, it designates a representative in a Member State where it offers services, and the team confirms the representative's mandate and contact details with that person in writing. The output is the registration confirmation and a signed representative mandate, stored with the entity records. Done means both are on file and the team has a named owner who checks them when contact details or services change.

  5. Map Article 21 measures and Annex requirements to controls

    The team maps each of the ten Article 21(2) measures and the technical requirements of Implementing Regulation (EU) 2024/2690 that apply to online platforms to existing policies, technical controls and owners. Gaps are logged with an owner and a planned remediation, and the team reads ENISA's June 2025 technical guidance for the examples of evidence it gives for each requirement. The output is a control register that links each requirement to a control, an owner, a test method and an evidence location. Done means each in-scope requirement has at least one mapped control and the open gaps are approved by management.

  6. Test significance thresholds and incident procedures

    The team sets up the monitoring and counting needed to apply the significance criteria in the implementing regulation, including the user-based unavailability threshold for marketplaces, search engines and social networks and the rule that suspected malicious compromise of data integrity, confidentiality or authenticity is significant for online platforms regardless of user count. Engineers run a tabletop exercise against a worked example, labeled as illustrative, to confirm that the 24-hour, 72-hour and one-month reporting steps can be met. The output is an incident decision procedure and a tabletop record. Done means the on-call team can decide significance and start a report without waiting for the legal review.

  7. Assemble evidence for national authorities

    The team packages the control register, policies, configuration records, logs, test results, incident records and management approvals into an evidence library organized by requirement. Owners check that each item is current, dated and traceable to the system it describes, and counsel reviews the library for personal data before it is shared. Because NIS2 creates no certificate, the library is the record that a national authority inspects, scans or requests during supervision. The output is an evidence index that the compliance lead can produce on request. Done means an internal reviewer can locate the evidence for every mapped control within a short session.

Who owns the controls, who prepares evidence and who issues conclusions

The online marketplace, search engine or social networking service provider remains the entity bound by NIS2. Its management body approves and oversees the Article 21 risk-management measures, and the organization carries the legal responsibility for compliance, for its risk decisions and for every report it files with the competent authority. No outside firm can take those duties over.

  • Controls and policies: The organization decides which measures apply to its services, adopts the written policies and accepts residual risk.
  • Decisions and accountability: Management signs off on risk treatment, budgets, supplier choices and the scope of the Article 21 program.
  • Incident reporting: The organization makes the early warning, notification and final report under Article 23 and informs affected service recipients when required.
  • Registration and representation: It handles the registry entry and, where it is established outside the Union, designates its EU representative.
  • Evidence ownership: Its staff can explain how each control works and keep the records that show it.

Before engaging anyone, confirm which of these duties sit with named people in your organization and which you intend to delegate in writing.

Questions platform teams ask about NIS2 scope and readiness

Is an online marketplace with third-party sellers in scope of NIS2?

Yes, if the marketplace is an online marketplace as NIS2 defines it, because Annex II, point 6 lists online marketplaces among digital providers. NIS2 takes its definition of an online marketplace from Directive 2005/29/EC and Regulation (EU) 2019/1150, so the question is whether the service lets consumers or traders conclude distance contracts with other traders or consumers through the platform. The presence of third-party sellers is typical of that model rather than a separate test. Scope then turns on the size thresholds and the Member State where the platform is established. Confirm the classification with national counsel or the competent authority, because the answer shapes which obligations apply and how incidents are counted.

Does a social network with a small EU user base still fall under NIS2?

A small EU user base does not remove a social networking services platform from the Annex II category by itself, but it affects how incidents are judged. NIS2 defines a social networking services platform as one that lets end users connect, share, discover and communicate with each other across devices, in particular through chats, posts, videos and recommendations. For these providers, an outage is significant when it affects more than 5% or more than 1 million EU users, whichever is smaller. A smaller user base therefore lowers the absolute number at which an incident becomes reportable. Ask your national competent authority how it applies the size thresholds to your user counts.

What must the EU representative do for a platform established outside the EU?

The representative is the contact point that a Member State can reach when a non-EU platform offers services in the Union without an EU establishment. Under Article 26(3), the provider must designate a representative in a Member State where it offers services, and without one, any Member State where the provider offers services may take legal action. In practice, the representative should be able to receive regulator correspondence, support registration information and help the organization respond to information requests. The appointment is a legal decision for the organization. Confirm the written mandate, the contract terms and how the representative will receive and route supervisory communications before relying on it.

Does NIS2 issue a certificate that proves compliance?

No. NIS2 creates no certificate of compliance. National competent authorities oversee compliance through inspections, security audits, security scans, information requests and administrative fines, as set out in Articles 32 to 34. An independent auditor or certification body can assess your controls against a recognized framework, but that report is not a NIS2 certificate issued by the EU. DeployOpen prepares systems, controls and evidence for assessment and does not issue audit reports, attestations or certifications. Ask any provider which evidence they will deliver to your regulator and how it maps to the Implementing Regulation (EU) 2024/2690 requirements that apply to platforms.

How long does readiness work take, and what drives the effort?

Duration and cost follow from the written scope and the platform's existing controls, and no figure is given here because none has been researched for this topic. The main drivers are the number of services and jurisdictions in scope, how far the current logging, access control, change management and incident processes already match the Article 21 measures and the platform requirements in Implementing Regulation (EU) 2024/2690, the number of systems that must be documented, and whether the organization has an established risk assessment. Platforms with mature security programs usually need less preparation. Ask for a fixed-scope proposal that lists deliverables, assumptions and the evidence each deliverable produces.

Can our own team prepare the NIS2 evidence in-house?

Often yes, in part, and the split depends on skills and capacity. Your team owns the controls, the management body approvals and the decisions about risk, while an implementation partner can prepare systems, configuration, logging, backups and the documentation that shows them working. Internal staff usually handle policy ownership and daily operations, and the gaps tend to appear in evidence collection, consistent records of testing and incident exercises. DeployOpen implements, hardens and documents self-hosted open-source platforms inside your own infrastructure and runs security testing, but it does not issue reports. Decide which pieces to keep in-house before requesting a quote.

What to confirm with counsel and the national authority before you commit

Start by confirming with counsel and the national competent authority which Member State has jurisdiction over your platform. Under Article 26(1)(b), online marketplaces, search engines and social networks fall under the Member State of their main establishment in the Union, so the answer decides which national transposition law, supervisor and registration process apply. Ask the authority in writing whether your service is treated as an important entity, since Annex II entities are important unless the Member State identifies them as essential under Article 2(2)(b) to (e). Also ask whether that Member State has set any stricter national rules under Article 5, because a national law can add obligations on top of the directive.

Next, confirm the registration process and the representative appointment. Article 27(2) required Member States to collect registration information from these providers by 17 January 2025, but the portal, deadlines, required fields and any update obligation are set nationally, so request the current submission guidance and keep a dated record of what you filed. If your main establishment is outside the Union but you offer services there, confirm which Member State will accept your representative designation under Article 26(3), and get the appointment and its scope in a signed document. Ask counsel how the representative's contact details must be kept current and what happens if the role lapses.

Finally, treat two items as open questions rather than settled rules. The Commission's proposal COM(2026) 13 of 20 January 2026 would amend NIS2, but it still needs approval by the European Parliament and the Council, so ask counsel which provisions could change and when your planning should be revisited. The Commission must also review how NIS2 works by 17 October 2027 under Article 40, so ask the authority whether it expects guidance or national changes before that date. Record each answer, its date and the person who gave it, because those notes will matter when a supervisor asks how you determined your obligations.

How DeployOpen prepares a platform for NIS2 evidence

DeployOpen plans, implements, hardens and documents self-hosted open-source platforms inside the client's own infrastructure, and prepares the systems, controls and evidence a platform needs for NIS2 reviews. We do not issue audit reports or certifications. Independent authorities and assessors decide compliance, and the organization owns its controls.

How we scope

  • Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
  • The written scope lists which platform services, user-facing features and EU establishments are covered by the work.
  • Scoping confirms which Member State the entity expects to fall under, based on its main establishment, and what the client must verify with its national authority.
  • Scope also records which Implementing Regulation 2024/2690 requirements apply to the platform and which the client owns internally.

How we build

  • We implement and harden self-hosted open-source platform components in the client's cloud accounts, data centers or air-gapped networks.
  • Logging and monitoring are configured so that user-impact figures for incident thresholds can be measured from system data.
  • Access control, backup, patching and change records are set up so that each Article 21 measure has a working control behind it.
  • Security testing of applications, APIs and infrastructure can be scoped to check the controls before a supervisor asks for them.

How we hand over

  • Documentation covers configuration, control ownership, evidence sources and the procedure for producing each piece of evidence.
  • Handover includes a register mapping each control to the evidence that shows it operating, for review by the client's compliance lead.
  • Incident reporting runbooks are written so that the 24-hour, 72-hour and one-month steps can be executed from the documented process.
  • The client receives a clear list of items it must still decide or confirm, such as registration details and its EU representative arrangement.

How we support

  • Ongoing support, upgrades and continuous testing are available as retainers after the fixed-scope work is delivered.
  • Support covers platform upgrades, backup restore checks and periodic review of configuration against the agreed evidence register.
  • Retainers can include recurring security testing so that findings are tracked against the controls they affect.
  • Questions about legal interpretation or supervisory expectations should go to counsel or the competent authority, not to DeployOpen.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.