Distinguish a marketplace from an ordinary online shop
The NIS2 definition refers to an online marketplace as defined in EU consumer legislation, generally a service using software that allows consumers to conclude distance contracts with traders or other consumers. The distinction matters when an online retailer sells its own inventory but does not operate a marketplace for third parties. Analyse the actual service, transaction model, provider entity and EU users instead of relying on an e-commerce label.
Protect marketplace transactions and accounts
The regulation's Annex requires an organised approach to cybersecurity risk management, secure system development, access control, incident handling and supplier dependencies. Marketplaces depend on merchant onboarding, customer accounts, payment integrations, APIs and order processing, which can create different paths for service compromise. A risk assessment should identify how failures in these functions affect the marketplace service and what controls can prevent or contain them.
Plan continuity across commercial dependencies
Marketplace service delivery may rely on hosting, fraud prevention, identity tools, fulfilment interfaces and external payment processors. Document which dependencies are critical to transactions and how failures are detected and communicated. Test recovery of platform functions and procedures for malicious changes to account or transaction data. Customers and traders may require different communications, but their commercial complaints are not themselves a substitute for assessing NIS2 incident criteria.
Assess Article 11 without inventing a duration test
Article 11 includes complete or limited availability affecting more than five percent of marketplace users in the Union, or more than one million such users, whichever is smaller. Unlike the managed-services threshold in Article 10, its marketplace availability criteria do not state a minimum outage duration. It also addresses suspectedly malicious compromises to data integrity, confidentiality or authenticity, and specified user-impact compromises. Apply common Article 3 criteria and Article 4 where relevant.
Maintain service-specific evidence
Keep the covered entity's marketplace definition, user-impact measurement method, Annex control mapping and incident-response playbooks together. Record who can change platform configuration, who oversees critical suppliers and how reportability is decided. Escalate material security weaknesses to management, with clear action owners and dates. Review the scope and user base when the marketplace expands or changes its contracting model.
Points of clarification
Is every e-commerce website an online marketplace?
No. Determine whether the service meets the relevant online-marketplace definition, rather than classifying a site solely because it sells goods.
Does Article 11 include a 30-minute outage threshold?
No. Its availability criteria use affected EU-user thresholds without that specified duration.
Are data integrity incidents included?
Yes. Article 11 includes qualifying integrity, confidentiality or authenticity compromises.