Skip to main content
πŸŽ“ Claude Code Masterclass Learn AI-assisted development on Udemy β€” plus the companion book on Leanpub & Amazon. Start Learning
CRA Enforcement: Penalties, Market Surveillance, and What Happens If You Don't Comply
DevOps

CRA Enforcement: Penalties and Compliance

CRA penalties reach up to 15 million euros. How enforcement works, what market surveillance authorities will check, and how to prepare for inspections.

LB
Luca Berton
Β· 1 min read

CRA Enforcement: What Happens If You Don’t Comply

The CRA has teeth. Non-compliance means your products can be removed from the EU market, and fines can reach €15 million. Understanding enforcement helps you prioritize compliance efforts.

Penalty Structure

ViolationMaximum Fine
Essential cybersecurity requirements€15M or 2.5% global annual turnover
Other CRA obligations€10M or 2% global annual turnover
Incorrect/misleading information to authorities€5M or 1% global annual turnover

For each violation, the higher amount applies.

Market Surveillance

Member state authorities will conduct:

Reactive Surveillance

  • Respond to vulnerability reports and incidents
  • Investigate complaints from users or competitors
  • Follow up on ENISA vulnerability notifications

Proactive Surveillance

  • Random product testing and audits
  • Verification of CE marking and documentation
  • SBOM completeness checks
  • Security testing of products on the market

What Authorities Can Do

  1. Request documentation β€” technical files, SBOMs, test reports
  2. Order product testing β€” at the manufacturer’s expense
  3. Require corrective action β€” fix vulnerabilities, update documentation
  4. Issue product recalls β€” remove non-compliant products from the market
  5. Ban market access β€” prevent future sales until compliance is achieved
  6. Impose fines β€” up to the maximum amounts above

How to Prepare for Inspection

Compliance Package (ready at all times):
β”œβ”€β”€ EU Declaration of Conformity
β”œβ”€β”€ Technical Documentation
β”‚   β”œβ”€β”€ Product description
β”‚   β”œβ”€β”€ Security risk assessment
β”‚   β”œβ”€β”€ Design and development documentation
β”‚   └── Test reports
β”œβ”€β”€ Current SBOM
β”œβ”€β”€ Vulnerability handling procedures
β”œβ”€β”€ Security update policy and history
β”œβ”€β”€ Incident reports filed with ENISA
└── Evidence of security testing

Risk-Based Prioritization

Focus compliance efforts where enforcement risk is highest:

  1. Products involved in security incidents β€” these attract immediate attention
  2. Products with known unpatched vulnerabilities β€” visible in public databases
  3. Products without CE marking β€” easy to identify and enforce
  4. Class II/Critical products β€” higher scrutiny by design

Concerned about CRA enforcement? I help organizations build audit-ready compliance programs. Get in touch.

#cra #enforcement #penalties #compliance #eu-regulation
Share:
Automation Strategy Consulting

Need help with Automation Strategy Consulting?

Streamline workflows and build automation strategies that scale.

Learn more about Automation Strategy Consulting

Want to operate this yourself, in production?

Take the free AI Platform Engineer Readiness Scorecard to see which skills transfer β€” then build a production-shaped AI platform in the 4-week Bootcamp.

Take the Scorecard β†’
Luca Berton β€” AI & Cloud Advisor, Docker Captain

Luca Berton

AI & Cloud Advisor Β· Docker Captain Β· KubeCon Speaker

15+ years in enterprise infrastructure. Author of 8 technical books, creator of Ansible Pilot (1M+ YouTube views, 648K site users). Former Red Hat engineer. Speaker at KubeCon EU 2026 and Red Hat Summit 2026.

Free 30-min AI & Cloud consultation

Book Now