Article 25 empowers the Commission to adopt delegated acts that establish voluntary security attestation programmes for free and open-source software. Under such a programme, the developers or users of the software, and other third parties, can assess its conformity with all or certain essential cybersecurity requirements or other obligations of the CRA. The purpose is to support the due diligence that Article 13(5) requires from manufacturers that integrate open-source components. The power applies from 10 December 2024 under Article 61(2). A programme exists only once the Commission adopts the delegated act.
What does Article 25 do?
Article 25 gives the Commission the power to adopt delegated acts under Article 61 that establish voluntary security attestation programmes for products with digital elements that qualify as free and open-source software.
Article 25 itself sets no attestation criteria, no procedure and no certificate. All of these depend on the content of the delegated act. A page that describes an attestation process in detail describes a delegated act that has to be checked in the Official Journal first.
Who can carry out an attestation?
Article 25 names three groups. The developers of the open-source software, the users of the software, and other third parties can use an attestation programme to assess its conformity. The assessment can cover all or only certain essential cybersecurity requirements, or other obligations laid down in the CRA.
Article 25 does not give ENISA or any other body a role in running the programmes. The delegated act decides that.
Why does attestation matter for manufacturers?
Article 25 states its purpose as facilitating the due diligence obligation in Article 13(5), in particular for manufacturers that integrate free and open-source components. Article 13(5) requires manufacturers to exercise due diligence when they integrate third-party components so that the components do not compromise the cybersecurity of the product.
An attestation is voluntary. A manufacturer stays responsible for the product as a whole, and an attested component still has to be integrated securely and kept free from known exploitable vulnerabilities.
When does Article 25 apply?
Article 61(2) confers the power to adopt the Article 25 delegated acts on the Commission for five years from 10 December 2024, with tacit extension. The Commission can therefore adopt the act before the Regulation applies in full on 11 December 2027.
Until a delegated act is adopted, no Article 25 attestation programme exists. Manufacturers then document their component due diligence under Article 13(5) without one.
Work through Article 25 for each product in one CRA workspace.
Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Is Article 25 attestation mandatory for any open-source component?+
No. Article 25 provides for voluntary programmes. Manufacturers that integrate open-source components meet the due diligence obligation in Article 13(5) with or without an attestation, and document it in the technical documentation.
Does ENISA run the Article 25 attestation programme?+
Article 25 gives no body that role. It empowers the Commission to establish the programmes by delegated act, and the delegated act decides how they work and who runs them.
Can a manufacturer seek attestation for a component it uses?+
Article 25 allows the users of open-source software and other third parties, as well as its developers, to assess its conformity under a programme. A manufacturer that uses a component is one of those users. The procedure depends on the delegated act.
Need a CVD policy for Article 25?
Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.