Skip to content

alirezarezvani/claude-skills / ra-qm-team/skills/cra-readiness

cra-readiness

Verified

Use when a company that sells software, connected devices or firmware in the EU asks whether the Cyber Resilience Act (CRA, Regulation 2024/2847) applies, has to report an actively exploited vulnerability or security incident under Article 14 (24h/72h deadlines, ENISA Single Reporting Platform), must classify products as important or critical, pick a conformity route or support period, check an SBOM, or get to CE marking by December 2027. Four deterministic scripts with cited articles.

references/reporting_article14.md

View on GitHub
# Article 14 reporting: what is live since 11 September 2026

Reporting is the only CRA duty already in force for most manufacturers, and it
reaches products shipped years before the CRA existed. Everything here is from
Regulation (EU) 2024/2847 unless marked otherwise.

Confidence: 🟒 regulation text Β· 🟑 Commission guidance or ENISA (non-binding, official) Β· πŸ”΄ our reading, check with counsel

## Dates

| Date | What applies | Source |
|---|---|---|
| 10 Dec 2024 | Regulation in force | 🟒 Art 71(1); OJ L 2024/2847 of 20.11.2024 |
| 11 Jun 2026 | Notified bodies regime (Chapter IV, Arts 35-51) | 🟒 Art 71(2) |
| **11 Sep 2026** | **Article 14 reporting** | 🟒 Art 71(2) |
| 11 Dec 2027 | Everything else, incl. Annex I, conformity, CE marking, Art 24 stewards | 🟒 Art 71(2) |
| 11 Jun 2028 | End of validity for certificates issued under other cybersecurity acts | 🟒 Art 69(1) |

ENISA launched the Single Reporting Platform (SRP) on 11 September 2026 at
`portal.cra-srp.enisa.europa.eu` 🟑 (ENISA news item of that date). At launch it
had no API, an English-only interface and no voluntary-report flow πŸ”΄ (third-party
onboarding reports; verify on the portal).

## What must be reported

| Event | Trigger | Recipient | Source |
|---|---|---|---|
| Actively exploited vulnerability | "reliable evidence that a malicious actor has exploited" it in a system without permission | CSIRT designated as coordinator + ENISA, simultaneously, via the SRP | 🟒 Art 3(42), Art 14(1) |
| Severe incident having an impact on the security of the product | affects or could affect protection of sensitive or important data or functions, or led or could lead to malicious code in the product or the user's network | same | 🟒 Art 14(3), 14(5) |

Not reportable: a vulnerability found by good-faith testing, or a component
flaw with no evidence of exploitation in your product 🟒 (Art 3(42); recital 67)
🟑 (guidance: a third-party component flaw is reportable only if exploited in the
manufacturer's product). Handle those under Annex I Part II and, for components,
tell the maintainer (Art 13(6)). Voluntary reporting covers near misses and
non-exploited vulnerabilities 🟒 (Art 15).

## The three clocks

| Report | Vulnerability (Art 14(2)) | Severe incident (Art 14(4)) |
|---|---|---|
| Early warning | 24 h from awareness; Member States where the product is available | 24 h; plus whether unlawful or malicious acts are suspected |
| Notification | 72 h from awareness; product, nature of the exploit, corrective and user measures, sensitivity | 72 h; nature, initial assessment, measures, sensitivity |
| Final report | **14 days after a corrective or mitigating measure is available**; description, severity, impact, malicious actor info, update details | **one month after the incident notification**; detailed description, severity, impact, threat type or root cause, mitigation |

Users: after awareness, inform impacted users, and where appropriate all users,
of the event and the measures they can take, in a structured machine-readable
format where appropriate. If you don't, the CSIRT may 🟒 (Art 14(8)).

**When does "aware" start?** 🟑 The Commission guidance (Annex to C(2026) 5252,
27 July 2026) treats a manufacturer as aware once a prompt initial assessment
gives a reasonable degree of certainty. The SRP does not record that moment, so
your triage log is the evidence. πŸ”΄ A market surveillance authority could argue
from first detection if the triage was slow or undocumented; `art14_report_clock.py`
runs from detection when no awareness time is logged for that reason.

## Where reports go (Art 14(7))

The SRP endpoint of the CSIRT coordinator in the Member State of your **main
establishment** in the Union. Without one: the Member State of the authorised
representative, then the importer, then the distributor, then the one with most
users 🟒. Later reports may go to the same CSIRT as the first 🟒. πŸ”΄ The SRP's
"Assigned Representative" account role is not the Art 18 authorised representative.

## Legacy products

Products placed on the market before 11 December 2027 owe nothing else under
the CRA unless substantially modified, **but Article 14 applies to them** 🟒
(Art 69(2)-(3)). 🟑 Per the guidance the duty is not retroactive: exploitation
known before 11 September 2026 is not reportable, and it continues after the
support period ends. πŸ”΄ That last point surprises teams with end-of-life fleets.
Keep a contact route and triage for every product still in the field.

## Penalties and the SME carve-out

Breaching Art 13 or 14: up to EUR 15 000 000 or 2.5 % of worldwide annual
turnover, whichever is higher 🟒 (Art 64(2)). Micro and small enterprises cannot
be fined for missing the **24-hour early warning** (Art 14(2)(a), 14(4)(a)), and
open-source stewards cannot be fined at all 🟒 (Art 64(10)). The early warning is
still owed; only the fine is excluded.

## Pending changes to watch

- The **Digital Omnibus** (proposed 19 Nov 2025) would create one incident
  reporting entry point across GDPR, NIS2, DORA and CER. It is a proposal and,
  per the Commission's own summary, does not amend the CRA deadlines 🟑.
- Delegated act on delaying dissemination for cybersecurity reasons (due by
  11 Dec 2025, Art 14(9)) and implementing acts on format (Art 14(10)) 🟒. Check
  the OJ for adoption before relying on a template.

## Sources

1. Regulation (EU) 2024/2847, OJ L 2024/2847, 20.11.2024 β€” https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng (Arts 3, 14, 15, 16, 64, 69, 71)
2. European Commission, *Commission guidance on the application of the CRA*, Annex to C(2026) 5252, 27 July 2026 β€” https://digital-strategy.ec.europa.eu/en/library/commission-publishes-new-guidance-support-timely-cyber-resilience-act-implementation
3. ENISA, *The CRA Single Reporting Platform is launched*, 11 September 2026 β€” https://www.enisa.europa.eu/news/the-cra-single-reporting-platform-is-launched
4. ENISA, SRP FAQ β€” https://www.enisa.europa.eu/topics/product-security/vulnerability-services/eu-incident-response-and-cyber-crisis-management/single-reporting-platform-srp/frequently-asked-questions
5. Directive (EU) 2022/2555 (NIS2), Arts 6 and 12 β€” definitions of incident and near miss, CSIRT coordinators
6. European Commission, Digital Omnibus proposal, 19 November 2025 (status per EU Transition Pathways summary)
7. cyberresilienceact.eu, *CRA reporting: 24h, 72h & 14-day deadlines* β€” SRP field limits and launch constraints (independent, verify)
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall