Menu

Individual skill

cra-vulnerability-obligations

0upvotes

Meet EU Cyber Resilience Act vulnerability duties — coordinated disclosure, SBOMs, and lifecycle security for digital products.

skills/cra-vulnerability-obligations/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

The EU Cyber Resilience Act (CRA) sets binding cybersecurity requirements for products with digital elements sold in the EU: secure-by-design development, vulnerability handling with coordinated disclosure, SBOM provision, and security support for the product lifecycle. It shifts product security from best practice to legal obligation, with significant penalties.

This skill is a defensive compliance guide for product teams: understanding the obligations, building the vulnerability-handling machinery, and evidencing conformity. It is practical guidance, not legal advice — involve counsel for applicability and interpretation.

Start from the product lifecycle, not the legal text: the CRA rewards what good product-security teams already do — threat modeling, secure development, vulnerability disclosure programs, SBOMs, and timely patching. Map your existing practices to the obligations first; the gaps you find are the actual work program.

## When to use

- Determining CRA applicability for your products (scope, timelines, product categories).
- Building coordinated vulnerability disclosure (CVD) processes to meet CRA duties.
- Producing SBOMs and security documentation for products.
- Defining security support periods and update policies.
Back to top