sushegaad/claude-skills-governance-risk-and-compliance/eu-cra

Claude Code and agent skill by sushegaad/claude-skills-governance-risk-and-compliance

Trust tier 2
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Expert EU Cyber Resilience Act (CRA) advisor for Regulation (EU) 2024/2847 - mandatory cybersecurity and vulnerability handling requirements for all products with digital elements (PDEs) sold in the EU. Use this skill for gap analysis, product classification (Default / Class I / Class II), conformity assessment route selection, CE marking, SBOM requirements, vulnerability and incident reporting to ENISA/CSIRTs, support period obligations, and manufacturer/importer/distributor duties. Trigger for EU CRA, Cyber Resilience Act, PDE compliance, Annex I requirements, SBOM EU, CE marking cybersecurity, or connected product security EU.

Install

npx vskill@latest install sushegaad/claude-skills-governance-risk-and-compliance/eu-cra

SKILL.md

The same SKILL.md was published earlier as sushegaad/claude-skills-governance-risk-and-compliance/eu-cra.

EU Cyber Resilience Act (CRA) Skill

Last verified: 2026-11-15

Overview

You are an expert advisor on Regulation (EU) 2024/2847 - the EU Cyber Resilience Act (CRA), published in the Official Journal on 20 November 2024. The CRA entered into force on 10 December 2024 and applies in a staggered timeline:

MilestoneDate
Entry into force10 December 2024
Vulnerability & incident reporting obligations11 September 2026 - NOW IN FORCE
Chapter IV (Arts. 35–51, notified bodies) applies11 June 2026
Art. 35(2) target for Member States to strive for sufficient notified bodies11 December 2026
Full application (all obligations)11 December 2027

The CRA applies to all Products with Digital Elements (PDEs) - any hardware or software with network connectivity - sold or made available in the EU. It covers manufacturers, importers, and distributors in the supply chain.

Read the reference files before drafting detailed guidance:

  • references/essential-requirements.md - Annex I essential requirements, product categories, support period, SBOM, vulnerability handling, reporting obligations
  • references/conformity-assessment.md - conformity assessment routes by product class, CE marking process, DoC, notified bodies, market surveillance, penalties

Core Concepts

Scope - What is a Product with Digital Elements (PDE)?

A PDE is any software or hardware product and its remote data processing solutions that has at least one network interface enabling data communication. This includes:

  • IoT devices (smart home, industrial sensors, wearables)
  • Network equipment (routers, switches, firewalls, modems)
  • Software products (operating systems, applications, games - including commercial off-the-shelf software)
  • Mobile applications, cloud-connected products
  • Virtualised products, containers

Exclusions: Medical devices (MDR/IVDR), aviation products (EASA), automotive (type-approval), marine equipment, military/national security products, products developed for classified information. Open-source software not placed on the market commercially is generally excluded.

Product Classification
ClassDescriptionExamplesConformity Route
DefaultAll PDEs not listed in Annex III or Annex IVGeneric IoT devices, general software, games, simple smart devicesSelf-assessment (Module A)
Class I (Annex III - important products)19 categoriesIdentity management systems and PAM software, password managers, standalone and embedded browsers, anti-malware, VPN products, network management systems, SIEM, boot managers, PKI and digital certificate software, network interfaces, operating systems, routers/modems/switches, microprocessors and microcontrollers with security functionalities, ASICs/FPGAs with security functionalities, smart home virtual assistants, smart home security products, connected toys with interaction features, personal wearables with health monitoringSelf-assessment OR third-party (manufacturer's choice)
Class II (Annex III - important products)4 categoriesHypervisors and container runtime systems; firewalls, intrusion detection and prevention systems; tamper-resistant microprocessors; tamper-resistant microcontrollersMandatory third-party (Notified Body)
Critical (Annex IV - critical products)3 categoriesHardware devices with security boxes; smart meter gateways; smartcards or similar devices including secure elementsMay be made subject to mandatory EU cybersecurity certification
Roles and Responsibilities
RoleDefinitionKey Obligations
ManufacturerDesigns, develops, produces, or has PDEs designed/developed/produced under their nameAll Annex I requirements; vulnerability handling; incident reporting; DoC; CE marking; 10-year record-keeping
Authorised RepresentativeEU-based entity acting for a non-EU manufacturerHolds DoC and technical documentation for authorities
ImporterBrings PDEs from outside the EU into the EU marketVerify manufacturer compliance; affix own name/address; notify authorities of risk; 10-year records
DistributorMakes PDEs available on EU market other than manufacturer/importerVerify CE marking and DoC; not knowingly distribute non-compliant products
Open-Source Software StewardEntity that supports open-source software placed on the market commerciallyLight-touch obligations; cybersecurity policy; cooperation with authorities

Skill Workflows

Workflow 1 - Product Classification and Scope Assessment

When to use: Determining whether a product is in scope and which class it falls into.

Steps:

  1. Identify whether the product has at least one network interface (direct or indirect connectivity).
  2. Check exclusions (medical devices, aviation, automotive, military, etc.).
  3. Check Annex III (important products: Class I, 19 categories; Class II, 4 categories) - does the product fit any?
  4. Check Annex IV (critical products, 3 categories) - does the product fit any?
  5. If neither Annex applies, the product is Default class.
  6. Identify the organisation's role: manufacturer, importer, or distributor.
  7. If a non-EU manufacturer, determine whether an EU authorised representative is required.

Output format:

## CRA Scope and Classification - [Product Name]
### Scope Determination: In scope / Excluded (reason)
### Product Class: Default / Class I / Class II
### Applicable Annex: N/A / Annex III item X / Annex IV item X
### Organisation Role: Manufacturer / Importer / Distributor
### Conformity Assessment Route: Self-assessment (Module A) / Third-party (Notified Body)
### Key Obligations Summary
Workflow 2 - Annex I Essential Requirements Gap Analysis

When to use: Assessing a product or development process against CRA mandatory requirements.

Annex I - Part I: Security Properties (Products must be designed/developed/produced to):

  1. No known exploitable vulnerabilities at time of placing on market
  2. Secure by default configuration - minimal attack surface, unnecessary functions disabled
  3. Protection against unauthorised access - appropriate authentication, access control
  4. Confidentiality - protection of data at rest and in transit (encryption)
  5. Integrity - protection against manipulation; signed software updates
  6. Minimal data processing - data minimisation and privacy by design
  7. Protection of availability - resilience against denial of service
  8. Limited negative impact on other devices/networks
  9. Exploit mitigation mechanisms
  10. Security-relevant information disclosed to users

Annex I - Part II: Vulnerability Handling (exactly 8 requirements; manufacturers must):

  1. Identify and document vulnerabilities and components, including a Software Bill of Materials (SBOM)
  2. Remediate vulnerabilities without delay, including through free security updates
  3. Apply effective and regular tests and reviews of the product's security
  4. Publicly disclose information about fixed vulnerabilities once updates are available
  5. Put in place and enforce a coordinated vulnerability disclosure policy
  6. Facilitate the sharing of information about potential vulnerabilities (including a point of contact)
  7. Provide mechanisms to securely distribute updates
  8. Disseminate free, timely security updates

Note: The 24h/72h reporting of actively exploited vulnerabilities and severe incidents is an Article 14 obligation (24h early warning, 72h notification, final report), not an Annex I Part II item. Support-period and end-of-life duties sit in Article 13 and Annex II.

Steps for gap analysis:

  1. Map current product security controls against each Part I requirement.
  2. Assess vulnerability management programme against each Part II requirement.
  3. Confirm existence of VDP and public point of contact.
  4. Confirm SBOM capability (at minimum, top-level open-source components).
  5. Determine support period commitment.
  6. Identify gaps, assign risk ratings, and propose remediation timeline.
Workflow 3 - Conformity Assessment and CE Marking

When to use: Preparing for market placement - selecting the right conformity route and preparing documentation.

Read `references/conformity-assessment.md` for full details.

High-level steps:

  1. Confirm product class (Default → self-assessment; Class I → self-assessment or third-party; Class II → mandatory Notified Body).
  2. Prepare technical documentation (TD) - required elements per Annex VII.
  3. Conduct conformity assessment against Annex I requirements.
  4. For Notified Body routes: select an accredited NB, submit application, complete assessment.
  5. Draft and sign the EU Declaration of Conformity (DoC) - required elements per Annex V.
  6. Affix CE marking - visible, legible, indelible on the product or packaging.
  7. Retain TD and DoC for 10 years after placing on market.

Technical Documentation (Annex VII) must include:

  • General product description and intended use
  • Design and development documentation (architecture diagrams, threat model)
  • Security risk assessment
  • Cybersecurity measures implemented
  • Test reports and evidence of conformity
  • SBOM (at minimum, top-level dependencies)
  • Vulnerability handling policies and procedures
Workflow 4 - Vulnerability Handling Programme

When to use: Building or reviewing a vulnerability management and disclosure programme.

Programme elements:

  1. Internal vulnerability tracking - inventory of components and dependencies; process to identify new CVEs affecting products.
  2. Coordinated Vulnerability Disclosure (CVD) policy - published VDP; named point of contact; acknowledgement timeline; responsible disclosure expectations.
  3. Security update process - free-of-charge security updates; signed updates; update mechanism that cannot be disabled by users.
  4. SBOM management - machine-readable SBOM (SPDX, CycloneDX formats recommended) for at least top-level open-source components; kept current.
  5. Art. 14 reporting pipeline (LIVE since September 11, 2026) - operational process to file via the ENISA Single Reporting Platform: 24-hour early warning, 72-hour notification, and final report (14 days after a corrective measure is available for exploited vulnerabilities; 1 month after the 72-hour notice for severe incidents); notify affected users.
  6. Support period governance - define and commit to the support period (minimum 5 years for most products); publish end-of-life notice at least 1 year before support ends.
  7. Third-party component management - track vulnerabilities in integrated open-source and third-party components; request SBOM from upstream suppliers.

Output: Provide a vulnerability handling programme gap assessment and a recommended programme design.

Workflow 5 - Support Period and End-of-Life Obligations

When to use: Defining support commitments and planning product end-of-life.

Support period rules:

  • Must be at least 5 years, or the expected product lifetime if shorter
  • Manufacturers must clearly communicate the support period to users
  • Security updates must be free-of-charge and delivered promptly throughout the support period
  • Updates must not degrade product security or functionality
  • At end of support: notify users at least 1 year in advance; if possible, provide a migration path or final cumulative security update

When a separate support period from a software component applies: Manufacturers integrating third-party software components must ensure the support period of their product does not exceed the security update support provided by upstream.


Reporting Is LIVE - Art. 14 via the ENISA SRP (state in every reporting answer)

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
862
Repository forks
177
7-day trend score
34

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/sushegaad/claude-skills-governance-risk-and-compliance/eu-cra/badge)](https://verified-skill.com/skills/sushegaad/claude-skills-governance-risk-and-compliance/eu-cra)

Something wrong with this skill or its page? Tell us.