In depth

Cybersecurity Act: a guide to the regulation on ENISA and European certification

What Regulation (EU) 2019/881 (Cybersecurity Act) provides: ENISA’s mandate and tasks, the European cybersecurity certification framework, assurance levels, EUCC and the schemes in preparation (cloud, 5G, managed security services, digital identity wallets), links with the CRA, NIS 2 and the AI Act, implementation in Italy and the proposed Cybersecurity Act 2, with references to the articles.

Checked against the official text on 5 November 2026 · How we work

In short for businesses

Who it concerns
It places no obligations on companies: it sets up ENISA and the European cybersecurity certificates. It concerns you if you want to certify an IT product, service or process, or if a customer or a law asks you for a certificate.
What to do
Certification is voluntary, unless another law makes it mandatory. Today there is the EUCC for IT products: the certificate is valid in all Member States and can help show compliance with the CRA. Whoever obtains a certificate must handle vulnerability reports and publish security information for users.
When
The EUCC applies from 27 February 2025. The Commission has proposed a Cybersecurity Act 2, still under negotiation.

A simplified summary: details and exceptions are below. Terms with a dotted underline link to the glossary.

Regulation (EU) 2019/881, known as the Cybersecurity Act, has two parts: it gives ENISA, the European Union Agency for Cybersecurity, a permanent mandate with broader tasks, and it sets up the European cybersecurity certification framework for ICT products, services and processes (Art. 1(1)). It has been in force since 27 June 2019 and repealed Regulation (EU) No 526/2013 on the former ENISA (Arts. 68 and 69).

It is a regulation, so it applies directly in all Member States. The provisions on national authorities, conformity assessment bodies and penalties apply from 28 June 2021 (Art. 69(2)). Regulation (EU) 2025/37 extended it to managed security services from 4 February 2025.

The Cybersecurity Act does not impose security obligations on companies or products: certification is voluntary, unless another EU or national law makes it mandatory (Art. 56(2)). It matters because recent laws, such as the CRA, NIS 2 and the AI Act, use European certificates to demonstrate compliance.

The Cybersecurity Act is a cybersecurity law in the full sense, but unlike the others: it does not say what organisations must do (like NIS 2) or which requirements products must meet (like the CRA). Instead, it builds the common tools that the other laws use:

  • ENISA, which supports the Member States and the EU institutions, coordinates the CSIRTs network, organises exercises and runs tools set up by other acts, such as the NIS 2 European vulnerability database and the CRA single reporting platform;
  • the European certification schemes, which replace national schemes and make it possible to certify an ICT product, service or process once, with a certificate recognised in all Member States (Art. 56(10)).

The aim of certification is to protect the availability, authenticity, integrity and confidentiality of the data and functions offered by certified products and services throughout their life cycle (Art. 46(2)).

Back to contents

Key dates

Date What happens
17 April 2019 Adoption of the Regulation
7 June 2019 Publication in the Official Journal of the EU
27 June 2019 Entry into force; ENISA has a mandate of indefinite duration and Regulation (EU) No 526/2013 is repealed (Arts. 68 and 69)
28 June 2021 The rules on national certification authorities, conformity assessment bodies, notification, complaints, remedies and penalties apply (Arts. 58, 60, 61, 63, 64 and 65)
31 January 2024 The Commission adopts EUCC, the first European certification scheme; on 7 February 2024 it publishes the first Union rolling work programme
4 February 2025 Regulation (EU) 2025/37 on managed security services enters into force
27 February 2025 EUCC applies; national certification schemes for the same products cease
20 January 2026 The Commission publishes its evaluation of the Regulation and proposes the Cybersecurity Act 2, which would repeal it
31 December 2027 Last day to issue EUCC certificates under the old versions of the Common Criteria
28 June 2029 Next Commission evaluation of ENISA and the certification framework, repeated every five years (Art. 67)

The dates are also in the document record.

Back to contents

ENISA: mandate and tasks

ENISA works towards a high common level of cybersecurity across the Union: it is the reference point for cybersecurity advice and expertise for the EU institutions and other stakeholders, and acts independently, avoiding duplication of Member State activities (Art. 3). It also carries out tasks assigned to it by other EU cybersecurity laws (Art. 3(2)).

Its tasks (Arts. 5-12):

Area What ENISA does
EU policy and law (Art. 5) Advises the Commission on new laws, helps Member States apply rules on cybersecurity, digital identity, electronic communications and data protection consistently
Capacity building (Art. 6) Helps Member States build CSIRTs, national strategies and vulnerability disclosure policies, provides training, organises EU-level exercises at least every two years
Operational cooperation (Art. 7) Secretariat of the CSIRTs network, assistance to Member States in significant incidents, analysis of vulnerabilities and incidents, regular report on the technical situation of cybersecurity in the EU
Certification and standardisation (Art. 8) Prepares candidate European certification schemes, evaluates them at least every five years, follows standardisation and publishes guidelines
Knowledge and information (Art. 9) Strategic analyses of threats and incidents, analyses of emerging technologies, a public cybersecurity information portal
Awareness and education (Art. 10) Campaigns on cyber hygiene and digital literacy for citizens and businesses
Research and innovation (Art. 11) Advice on research priorities and input to the Union’s strategic research agenda on cybersecurity
International cooperation (Art. 12) Works with third countries and international organisations

Other acts have added tasks: under NIS 2, ENISA runs the European vulnerability database (Art. 12 NIS 2), the registry of digital service providers (Art. 27 NIS 2) and the biennial report on the state of cybersecurity in the Union (Art. 18 NIS 2); under the CRA it runs the single reporting platform for actively exploited vulnerabilities and severe incidents (Art. 16 CRA).

Organisation. ENISA has a Management Board with one member per Member State and two from the Commission, an Executive Board, an Executive Director, an Advisory Group and a network of National Liaison Officers (Arts. 13-23). The Stakeholder Cybersecurity Certification Group advises the Commission and ENISA on certification priorities (Art. 22).

Back to contents

The European certification framework

In practice: European certification is voluntary unless another law makes it mandatory, but a certificate is valid across the EU and some laws, such as the CRA, accept it as proof of conformity.

A European cybersecurity certification scheme is a set of rules, technical requirements, standards and procedures laid down at EU level for certifying specific ICT products, services or processes or managed security services (Art. 2(9)). The Regulation does not certify anything by itself: it sets out how schemes are created and what they must contain.

What can be certified (Art. 2(12)-(14a)):

  • ICT products: elements of a network or information system, hardware or software;
  • ICT services: services consisting mainly in transmitting, storing or processing information, such as cloud;
  • ICT processes: the activities to design, develop, deliver or maintain an ICT product or service;
  • managed security services, since 2025: incident handling, penetration testing, security audits and consultancy.

Security objectives. Each scheme must protect data against unauthorised access, processing, loss and alteration, restrict access to those entitled to it, record who did what and when, identify and document known vulnerabilities and dependencies, ensure products that are secure by design and by default, up to date and with secure update mechanisms, and restore data and services in a timely manner after an incident (Art. 51). For managed security services, the competence and integrity of staff and the quality of internal procedures also count (Art. 51a).

Content of a scheme. Each scheme sets out at least its scope, the reference standards, the assurance levels, whether self-assessment is allowed, the evaluation criteria, the rules on marks and labels, on handling vulnerabilities found after certification, on the maximum validity of certificates and on mutual recognition with third countries (Art. 54).

Information for users. Holders of certified products or services must publish guidance on secure configuration and use, the security support period and availability of updates, contact details for reporting vulnerabilities and a reference to repositories of known vulnerabilities (Art. 55).

End of national schemes. Once a European scheme covers certain products or services, national schemes for the same products or services cease to produce effects from the date set in the European scheme, and Member States may not create new ones; national certificates already issued remain valid until they expire (Art. 57).

Back to contents

Assurance levels and self-assessment

In practice: the level says how thorough the evaluation was, not how secure the product is: it is chosen according to the risk of the intended use, and self-assessment is allowed only at basic level, where the scheme provides for it.

A scheme may specify one or more assurance levels, chosen according to the risk associated with the intended use of the product or service (Art. 52). The level shows how thorough the evaluation was, not how secure the product is in absolute terms (Art. 2(21)).

Level What it ensures Who can issue the certificate
Basic Evaluated at least through a review of technical documentation, to minimise the known basic risks of incidents and cyberattacks (Art. 52(5)) Accredited conformity assessment body; the scheme may allow the manufacturer’s EU statement of conformity (Art. 53)
Substantial Evaluated at least through a review showing the absence of publicly known vulnerabilities and testing that security functionalities are correctly implemented, to minimise known risks and attacks by actors with limited skills and resources (Art. 52(6)) Accredited conformity assessment body (Art. 56(4))
High As substantial, with state-of-the-art security functionalities and penetration testing, to minimise the risk of state-of-the-art attacks by actors with significant skills and resources (Art. 52(7)) National certification authority, or a body with its approval case by case or under a general delegation (Art. 56(6))

Self-assessment of conformity is only possible for low-risk products and services at basic level, and only if the scheme allows it: the manufacturer issues an EU statement of conformity, is responsible for it and keeps it available to the national authority with the technical documentation (Art. 53). Like certificates, statements are recognised in all Member States.

Back to contents

How a certification scheme is made

  1. The Commission publishes the Union rolling work programme, with strategic priorities and the list of products and services that could benefit from a European scheme, updated at least every three years (Art. 47). The first was published on 7 February 2024 and lists as priorities digital identity wallets, managed security services, industrial automation and control systems, secure life-cycle development linked to the CRA, and cryptographic mechanisms.
  2. The Commission, or in justified cases the European Cybersecurity Certification Group (ECCG), asks ENISA to prepare a candidate scheme (Art. 48).
  3. ENISA prepares the candidate scheme with an ad hoc working group, consults stakeholders and asks for the ECCG’s non-binding opinion (Art. 49(3)-(6)).
  4. The Commission adopts the scheme by an implementing regulation (Art. 49(7)).
  5. ENISA evaluates each scheme at least every five years and may prepare a revision (Art. 49(8)).

The ECCG brings together the national certification authorities, is chaired by the Commission and advises it on the work programme and schemes (Art. 62). The European Parliament and the Council may ask for quarterly information on candidate schemes in preparation (Art. 49a, added in 2025).

Back to contents

The schemes: EUCC and those in preparation

The Commission has asked ENISA for five schemes. As of November 2026 only one has been adopted, EUCC: in its 2026 evaluation the Commission itself acknowledges that the framework has suffered major delays and that work on cloud and 5G has been held back by political and technical issues, such as debates on data sovereignty.

Scheme What it covers Status
EUCC ICT products and protection profiles, based on the Common Criteria Adopted by Implementing Regulation (EU) 2024/482, applicable from 27 February 2025
EUCS Cloud services In preparation, not adopted
EU5G 5G networks In preparation, not adopted
EUDIW European digital identity wallets In preparation, not adopted
EUMSS Managed security services Requested on 25 April 2025; first ENISA draft on incident response services, under consultation until 13 September 2026; not adopted

The list of requests is on the Commission page on the certification framework (opens in a new tab); certificates issued are published on ENISA’s certification website (opens in a new tab) (Art. 50).

Back to contents

EUCC in practice

In practice: an EUCC certificate requires an accredited laboratory and a Common Criteria evaluation: no self-assessment, validity of up to five years and a duty to handle reported vulnerabilities.

EUCC (European Common Criteria-based cybersecurity certification scheme) builds on the Common Criteria (ISO/IEC 15408) and the common evaluation methodology ISO/IEC 18045, used in Europe for almost thirty years under the SOG-IS agreement (Art. 3 of Implementing Regulation 2024/482). It applies to ICT products such as smart cards, secure elements, firewalls, routers or operating systems, and to protection profiles, i.e. the security requirements common to a category of products.

  • Levels: “substantial” (AVA_VAN 1 or 2) or “high” (AVA_VAN 3, 4 or 5); there is no basic level and self-assessment is not allowed (Arts. 4 and 6).
  • Who evaluates: accredited and notified evaluation laboratories (ITSEFs) and certification bodies; for the high level they must also be authorised by the national authority, which checks additional competences and the protection of confidential information (Arts. 21-24).
  • Validity: at most five years, unless approved by the national authority (Art. 12).
  • Vulnerabilities: the certificate holder must have procedures to receive and analyse reports, following ISO/IEC 30111 where needed; if a vulnerability affects the certificate it proposes a remedy and the body reviews the certificate, which may be suspended or withdrawn (Arts. 33-36 and 30).
  • Transition: national schemes for the same products ceased to produce effects on 27 February 2025; national certifications started by that date had to be completed by 27 February 2026 (Art. 49).

The scheme has been updated twice: Implementing Regulation (EU) 2024/3144 adopts the 2022 versions of the Common Criteria and allows the previous versions until 31 December 2027; Implementing Regulation (EU) 2025/2462 introduces certification of product series, assurance continuity and updates the state-of-the-art documents.

Back to contents

National authorities, bodies and penalties

National certification authorities. Each Member State designates one or more authorities, independent of the entities they supervise (Art. 58). They supervise certificate holders, conformity assessment bodies and manufacturers issuing EU statements of conformity, handle complaints, can carry out investigations and audits, withdraw certificates and impose penalties (Art. 58(7) and (8)). If they issue certificates themselves, these activities must be kept separate from supervision (Art. 58(4)).

Peer review. National authorities are reviewed by at least two authorities from other Member States and the Commission at least every five years (Art. 59). Implementing Regulation (EU) 2025/2540 sets the timetable: for Italy by 31 December 2027, together with Hungary, Greece, Estonia, Slovenia and the Netherlands.

Conformity assessment bodies. They are accredited by national accreditation bodies for at most five years, must be independent third parties (Art. 60 and Annex) and are notified to the Commission, which publishes the list in the Official Journal (Art. 61; procedures in Implementing Regulation (EU) 2024/3143).

Complaints and remedies. Anyone may lodge a complaint with the issuer of a certificate or the national authority, and has the right to an effective judicial remedy (Arts. 63 and 64).

Penalties. Member States lay them down for infringements of Title III and of the European schemes: they must be effective, proportionate and dissuasive (Art. 65). The Regulation sets no amounts.

Back to contents

Cybersecurity Act, CRA, NIS 2 and other acts

The Cybersecurity Act allows a certificate or an EU statement of conformity to create a presumption of conformity with the obligations of another EU law, if that law provides for it (Art. 54(3)). Recent laws do:

Act Role of European certification
CRA (EU) 2024/2847 Certified products are presumed to comply with the essential requirements covered by the certificate (Art. 27(8)). The Commission may specify by delegated acts which schemes can be used: for the requirements covered, a certificate at least at substantial level exempts important products from third-party assessment (Art. 27(9)). For critical products in Annex IV (security boxes, smart meter gateways, smartcards and secure elements) the Commission may require a European certificate at least at substantial level by delegated act (Art. 8(1)); until then, the procedures for class II important products apply
NIS 2 (EU) 2022/2555 Member States may require essential and important entities to use certified ICT products, services and processes; the Commission may do so by delegated acts for categories of entities where cybersecurity levels are insufficient (Art. 24)
AI Act (EU) 2024/1689 Certified high-risk AI systems are presumed to comply with the cybersecurity requirements of Art. 15, within the limits of the certificate (Art. 42(2))
Machinery Regulation (EU) 2023/1230 Certified machinery is presumed to comply with the requirements on protection against corruption and safety of control systems (Art. 20(9))

As of November 2026 the Commission has not yet adopted the CRA delegated acts on critical products (Art. 8) and on usable schemes (Art. 27(9)), nor any delegated act under NIS 2 (Art. 24). The presumption of conformity in Art. 27(8) CRA will, however, already apply to EUCC certificates, within the requirements they cover, once the CRA applies from 11 December 2027. The Commission first assessed by 2023 whether to make some schemes mandatory, and does so again at least every two years (Art. 56(3)).

Back to contents

In Italy

Legislative Decree No 123 of 3 August 2022 adapts Italian law to the Cybersecurity Act:

  • the National Cybersecurity Agency (ACN) is the national cybersecurity certification authority: it supervises conformity assessment bodies, certificate holders and manufacturers issuing EU statements of conformity;
  • ACN issues high-level certificates through OCSI (the Information Technology Security Certification Body) and cooperates with the national accreditation body;
  • in the absence of harmonised European rules, ACN may make a certification or statement of conformity mandatory;
  • administrative penalties reach up to EUR 5 million, with withdrawal of non-compliant products and services from the market.

Legislative Decree No 191 of 1 October 2026, in force from 6 November 2026, adapts Decree 123/2022 to Regulation (EU) 2025/37: it extends supervision and penalties to managed security services, allows ACN to issue certificates at every level through OCSI and replaces references to the former NIS decree with Legislative Decree 138/2024 transposing NIS 2.

Back to contents

The revision: Cybersecurity Act 2

On 20 January 2026 the Commission published its evaluation of ENISA and the certification framework (COM(2026) 9) and proposed a new regulation, the Cybersecurity Act 2 (COM(2026) 11), which would repeal Regulation 2019/881. It came with a directive making targeted amendments to NIS 2 (COM(2026) 13). The proposal is not yet law.

The main changes:

  • a stronger ENISA: new tasks in operational cooperation, early warnings, cyber threat intelligence repositories, vulnerability management services, support for NIS 2 entities against ransomware, the CRA single reporting platform and attestations of cybersecurity skills, with more resources and a Deputy Executive Director;
  • faster certification: ENISA would prepare a candidate scheme within 12 months of the Commission’s request (Art. 74), with clear rules on maintaining and reviewing schemes;
  • certification of organisations’ “cybersecurity posture”, not only of products and services, to make NIS 2 compliance easier (Arts. 71-73);
  • a broader presumption of conformity: a certificate could demonstrate compliance with other EU laws that provide for it, with third-party assessment (Art. 78);
  • ICT supply chain security: coordinated EU risk assessments, identification of key ICT assets in the NIS 2 critical sectors, possible designation of third countries of concern and lists of high-risk suppliers; in mobile networks their components would have to be phased out of key assets within 36 months of publication of the list (Arts. 98-111).

Where it stands. In the European Parliament the proposal has been referred to the ITRE committee (rapporteur Markéta Gregorová, appointed on 26 February 2026): the draft report dates from 18 September 2026 and amendments were tabled on 13 October 2026, but the committee has not yet voted (procedure file 2026/0011(COD) (opens in a new tab)). In the Council the presidency presented a progress report to the Telecommunications Council of 9 June 2026 (opens in a new tab). Until the new regulation is adopted and in force, Regulation 2019/881 continues to apply.

Back to contents

Subsequent acts and guidance

Act What it adds
Implementing Regulation (EU) 2024/482 (opens in a new tab) (31 January 2024) The EUCC scheme, based on the Common Criteria, applicable from 27 February 2025
Union rolling work programme (opens in a new tab) (7 February 2024) Priorities for future European certification schemes
Implementing Regulation (EU) 2024/3143 (opens in a new tab) (18 December 2024) Circumstances, formats and procedures for notifying conformity assessment bodies, for all schemes (Art. 61(5))
Implementing Regulation (EU) 2024/3144 (opens in a new tab) (18 December 2024) Amends EUCC: 2022 versions of the Common Criteria, transition until 31 December 2027
Regulation (EU) 2025/37 (opens in a new tab) (19 December 2024) Extends the certification framework to managed security services, from 4 February 2025
Implementing Regulation (EU) 2025/2462 (opens in a new tab) (8 December 2025) Amends EUCC: product series, assurance continuity, state-of-the-art documents
Implementing Regulation (EU) 2025/2540 (opens in a new tab) (9 December 2025) Timetable for peer reviews of national certification authorities, from 2026 to 2030
Evaluation report COM(2026) 9 (opens in a new tab) (20 January 2026) Evaluation of ENISA and the certification framework required by Art. 67
Proposal COM(2026) 11 (opens in a new tab) (20 January 2026) Cybersecurity Act 2: proposal, not yet law, that would repeal Regulation 2019/881
Legislative Decree No 191 of 1 October 2026 Italian adaptation to Regulation 2025/37, in force from 6 November 2026

Back to contents

Official sources

Back to contents

This page summarises the text of the act for information only and is not legal advice. Only the text published in the Official Journal of the European Union is authentic.