An independent information publicationDirective (EU) 2022/2555 · The NIS2 DirectiveNot an official publication
The Independent NIS2 Desk
NIS2 Compliance
Independent information on the NIS2 Directive, for the organisations it covers.
HomeArticlesNIS2 Requirements for Online Search Engines
Implementing Regulation 2024 2690 / 2026-10-11

NIS2 Requirements for Online Search Engines

Providers of online search engines are specifically named in Implementing Regulation (EU) 2024/2690. Covered providers must apply the Annex's technical and methodological cybersecurity measures and evaluate significant incidents under Article 12. The category concerns a defined online search engine service, not every website with a search box or an organisation using a third-party search engine.

Identify the legally defined search engine service

NIS2 draws on the EU definition of an online search engine, a digital service enabling users to input queries to perform searches, in principle, of websites or content across websites and obtain results in a format in which requested information can be found. An internal site-search function or a database query tool does not automatically meet this category. Identify the actual provider and search service, including service availability to users and contractual arrangements.

Apply controls to crawling, indexing and delivery

The Annex requires risk assessment, incident handling, secure acquisition and development, supplier security, access management and continuity. Search engines operate complex crawling, indexing, ranking and query-serving infrastructure. Risk analysis should cover unauthorised changes to search outputs, privileged system access, abuse of indexing workflows and failure of essential query services. Select measures based on the real architecture, record accountable owners and test their operation.

Understand functional degradation as well as outage

A search engine might respond to requests while key search functions fail or response times become materially worse. Monitoring should distinguish partial service degradation, complete unavailability and integrity or confidentiality incidents. Establish baselines for user experience, query availability and affected regions before an incident, so the response team can evaluate impact without relying on anecdotal reports alone. Customer support metrics may help corroborate technical evidence but are not themselves the legal test.

Apply the Article 12 significance criteria

Article 12 includes complete or limited availability affecting more than five percent of the online search engine's users in the Union, or more than one million EU users, whichever is smaller. It also includes suspectedly malicious compromise of data integrity, confidentiality or authenticity and specified large-user-impact compromises. Its availability tests do not contain the more-than-30-minute threshold applicable to managed services. Examine Article 3 common criteria and Article 4 recurring incidents when assessing the event.

Tie measurement to legal notification duties

Preserve time-stamped impact data, estimated EU-user population, affected search functions, malicious-change evidence and the response timeline. A provider should define who decides whether Article 12 or common criteria are met and who submits any Article 23 notification through the applicable national channel. Review the approach when the search product or its delivery architecture changes.

Points of clarification

Does a website search box make its operator a search-engine provider?

Not by itself. Evaluate the legal definition of an online search engine and the service actually provided.

Does Article 12 require an outage lasting more than one hour?

No. Article 12's availability clauses do not impose that duration requirement.

What incident impacts should be recorded?

The affected EU users, service functions, availability, integrity and confidentiality consequences, with reliable timing and evidence.

Further entries on this subject

The texts relied on

General editorial guidance only: it does not determine your organisation's legal obligations. See our editorial policy for how this site works and corrects errors.