Join waitlist
With public launch · Q3 2026

ENISA Article 14 workflow

The full picture of how crawin moves a CVE match into a filed ENISA notification: initial 24-hour notice, 72-hour update, and final report — pre-populated, time-stamped, signed.

What this page will cover

  • Article 14.1 (24 h) initial notification template
  • Article 14.2 (72 h) incident handling update
  • Article 14.3 final report (within 14 days of patch)
  • Auto-population from SBOM + matched CVE + product registration
  • Two human-confirm fields: active exploitation, conformity route
  • Submission audit trail for market surveillance authorities

Want this section first?

Join the waitlist and we email you the moment this page goes live — and the moment the matching product surface ships.

One email when your wave opens. No newsletter, no drip. Unsubscribe is one click. We do not share with third parties. Read our privacy notice.

While you wait
The Sept 11 2026 deadline How CVEs flow into the form