Essential requirements

Essential requirements is the regulation’s name for the Annex I security requirements every product must meet before it carries the CE marking. They describe security objectives, not specific techniques.

Definition

Essential requirements: definition

§

Annex I of Regulation (EU) 2024/2847 has two parts. Part I requires an appropriate level of cybersecurity based on the risks and then lists 13 specific requirements, including:

  • no known exploitable vulnerabilities when made available
  • a secure-by-default configuration with the option to reset
  • security updates, where applicable installed automatically by default, with an opt-out
  • protection against unauthorised access, and confidentiality and integrity of data
  • data minimisation and availability of essential functions, including resilience to denial-of-service attacks
  • a limited attack surface and logging of security-relevant events
  • secure and permanent removal of data and settings

Part II sets eight requirements for vulnerability handling, meaning the manufacturer’s processes.

Essential requirements under the Cyber Resilience Act: how COMPLYD implements it

In practice

Essential requirements in practice

Not every requirement fits every product. A sensor without user accounts needs no password management. Article 13(3) therefore requires the risk assessment to state whether and how each Part I requirement applies. Anyone ruling a requirement out has to give reasons.

How to implement them in detail will be described by harmonised standards. Applying them gives a presumption of conformity under Article 27.

Example

A weather station sends readings by radio to a base station. Secure defaults, integrity protection for the data and an update mechanism are relevant. User management is not, because there are no accounts. The risk assessment records this with reasons.

What to do

  • Assess every Annex I Part I requirement: applicable or not, with reasons
  • Describe and test the technical implementation of the applicable ones
  • File the evidence in the technical documentation
  • Track the status of harmonised standards for your product category
Set straight

Common misconceptions

Myth

“Annex I is a checklist with fixed specifications.”

In fact

It sets objectives, not key lengths or protocols. How an objective is met depends on the risk and the state of the art.

Myth

“Part II only matters after the sale.”

In fact

The processes for vulnerabilities, SBOM and updates must be in place before placing on the market and are reviewed in conformity assessment.

More in the glossary

Related terms

Annex I Part II

Vulnerability handling

Part II of Annex I, the requirements for processes.

Read the entry
Article 13(2) to (4)

Risk assessment

Explains which Part I requirements apply.

Read the entry
Article 3(27), Article 32

Conformity assessment

Demonstrates that the requirements are met.

Read the entry
Stephan Hutterer
About the author

Stephan Hutterer

Founder & CEO, COMPLYD

Product-security specialist with 20+ years protecting critical OT systems and deep IEC 62443 expertise. He founded COMPLYD to turn the EU Cyber Resilience Act into a workable process for product teams.

LinkedIn profile

Next step

Where does your product stand on the Cyber Resilience Act?

The free Product Check shows within minutes which of your products are in scope. The Readiness Check shows how well your company is prepared for the obligations.

Free, no login, no email. See who is in scope or go straight to the compliance software.