Eu Cra

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 7a840ef8562c · 14 Oct 2026Report an issue or request a re-scan

• PublisherSushegaad GitHub userOwner of the repository this skill is read from
• Source folderSushegaad/Claude-Skills-Governance-Risk-and-Compliance/plugins/eu-cra/skills/eu-craThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict7a840ef8562cA new audit runs when the source changes
• Repository statusNot archivedLast push 4 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: 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…

---
name: eu-cra
description: "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."
---

# EU Cyber Resilience Act (CRA) Skill

> **Last verified:** 2026-09-14

## 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:

| Milestone | Date |
|---|---|
| Entry into force | 10 December 2024 |
| Vulnerability & incident reporting obligations | **11 September 2026 — NOW IN FORCE** |
| Notified body obligations | 11 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

| Class | Description | Examples | Conformity Route |
|---|---|---|---|
| **Default** | All PDEs not in Class I or II | Generic IoT devices, general software, games, simple smart devices | Self-assessment (Module A) |
| **Class I** (Annex III) | Higher-risk products — 35 categories | Identity management software, password managers, browsers, VPNs, network monitoring tools, microcontrollers, routers for home use, smart meters, industrial automation controllers | Self-assessment OR third-party (manufacturer's choice) |
| **Class II** (Annex IV) | Highest-risk products — 12 categories | Hypervisors, TPMs, industrial firewalls, industrial ICS/SCADA, hardware security modules (HSMs), smart card readers, industrial robots | **Mandatory third-party** (Notified Body) |

### Roles and Responsibilities

| Role | Definition | Key Obligations |
|---|---|---|
| **Manufacturer** | Designs, develops, produces, or has PDEs designed/developed/produced under their name | All Annex I requirements; vulnerability handling; incident reporting; DoC; CE marking; 10-year record-keeping |
| **Authorised Representative** | EU-based entity acting for a non-EU manufacturer | Holds DoC and technical documentation for authorities |
| **Importer** | Brings PDEs from outside the EU into the EU market | Verify manufacturer compliance; affix own name/address; notify authorities of risk; 10-year records |
| **Distributor** | Makes PDEs available on EU market other than manufacturer/importer | Verify CE marking and DoC; not knowingly distribute non-compliant products |
| **Open-Source Software Steward** | Entity that supports open-source software placed on the market commercially | Light-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 (Class I) exhaustive list of 35 product categories — does the product fit any?
4. Check Annex IV (Class II) exhaustive list of 12 product 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

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
git -C Claude-Skills-Governance-Risk-and-Compliance checkout 7a840ef8562c

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 7a840ef8562c

Questions about Eu Cra

• github.com/Sushegaad/Claude-Skills-Governance-Risk-and-Complianc — the audited source at commit 7a840ef8562c and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology