Regulation (EU) 2024/2847 — Cyber Resilience Act
The CRA establishes horizontal cybersecurity requirements for products with digital elements, including design, vulnerability handling, economic-operator, conformity, reporting, and market-surveillance provisions.
What the authority record establishes
The CRA establishes horizontal cybersecurity requirements for products with digital elements, including design, vulnerability handling, economic-operator, conformity, reporting, and market-surveillance provisions.
Binding within scope; exclusions, roles, classifications, and dates require the controlling text
The exact official title, issuing body, jurisdiction, version or application record, and linked source define the scope of this page. Readers should not transfer the authority's status to a commercial product or infer transaction-, patient-, system-, site-, or organization-specific applicability from this summary.
Why it matters to this market
Industrial product and device providers need exact role, scope, support-period, vulnerability-handling, technical-documentation, conformity, and reporting evidence rather than a generic CRA-ready claim.
Affected operating stages
- Product Design
- Development
- Conformity
- Market Placement
- Vulnerability Handling
- Reporting
- Support
Capabilities to examine
Firmware, SBOM, And Component Intelligence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for firmware, SBOM, and component intelligence.
Configuration, Baseline, And Change Monitoring
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for configuration, baseline, and change monitoring.
Compliance Mapping And Control Evidence
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for compliance mapping and control evidence.
Device And Product Software-Supply-Chain Risk
Ask how the system or service identifies the controlling source and version, applies customer-specific interpretation, handles exceptions, preserves human judgment, and retains evidence for device and product software-supply-chain risk.
Affected buyer audiences
- industrial product manufacturers
- importers and distributors
- product-security teams
- buyers
- market surveillance authorities
Implementation questions
- Which entities, products, populations, transactions, systems, sites, or jurisdictions are actually within scope?
- What is binding, what is guidance, and what is a technical or consensus standard?
- Which publication, adoption, effective, application, transition, and enforcement dates differ?
- Who owns legal, clinical, quality, regulatory, policy, or operational interpretation?
- How will a source revision affect open work and historical decisions?
Interpretation boundary
Only the controlling EU text and applicable facts determine role, classification, obligation, date, and conformity.