Lars Artmann
Menu
lars@artmann.tech

Lars Artmann · Cyber Resilience Act expert

I turn the Cyber Resilience Act into shipped compliance.

Regulation (EU) 2024/2847 gates EU market access for anything with digital elements. I read the law in the Official Journal, work out what it demands from your products, and build the classification, SBOM pipelines and reporting runbooks that keep you selling — in your repository, not in a slide deck.

Portrait of Lars Artmann

iSAQB CPSA-F certified architect
Based in Germany · working EU-wide
German & English (both C2)

  1. 10 December 2024: Regulation (EU) 2024/2847 entered into force (passed).
  2. 11 September 2026: Article 14 vulnerability reporting became applicable: 24-hour early warning and 72-hour notification via the ENISA Single Reporting Platform (passed, live now).
  3. 11 December 2026: milestone, a sufficient number of notified bodies expected.
  4. 11 December 2027: full application, Annex I essential requirements, CE marking, support periods (upcoming).

388 days until full application

Milestone between them: by 11 Dec 2026 enough notified bodies must exist — Class II and critical products should queue early. Positions from the statute’s own dates; reporting (Art 14 + Art 69(3)) already covers products shipped before full application.

Positions computed from the dates in Regulation (EU) 2024/2847 · as of 18 Nov 2026

The big picture

What the Cyber Resilience Act actually is

One law, one market

A single EU regulation — (EU) 2024/2847 — not 27 national laws. One rulebook for products with digital elements sold anywhere in the Union, from connected toys to enterprise software.

Reg (EU) 2024/2847 · in force 10 Dec 2024

If you sell it in the EU, it is in scope

Manufacturers, importers, distributors — and non-EU sellers shipping in. Substantial modification makes you a manufacturer. Products placed on the market before full application stay covered for vulnerability reporting.

Art 1 & Art 14 · scope

Security built in, not bolted on

Annex I sets 21 essential requirements: secure by design, attack-surface minimisation, vulnerability handling for the whole support period — and an SBOM in machine-readable form.

Annex I · Part I (a)–(m), Part II (1)–(8)

Prove it, then mark it CE

Classify every product against Annex III/IV (Reg (EU) 2025/2392), run the conformity route that class demands — self-assessment or notified body — and the CE mark says the evidence exists.

Art 13 · Reg (EU) 2025/2392

The reporting clock is already live

Since 11 September 2026: actively exploited vulnerabilities and severe incidents start a 24 h early warning, then a 72 h notification through ENISA’s Single Reporting Platform — for products already shipped too.

Art 14 · applicable since 11 Sep 2026

The stake is market access

Up to €15 million or 2.5% of worldwide turnover — and products can be withdrawn from the EU market entirely. Full application lands 11 December 2027; classification and documentation duties bite earlier.

Art 64 penalties · full application 11 Dec 2027

And the standards? Still coming. The harmonised standards (request M/606, 41 of them) are in draft — the delivery deadline slipped another three months on 10 Nov 2026. The requirements in Annex I apply regardless: early movers self-assess against the law itself instead of waiting.

M/606 · C(2025)618, amended C(2026)7861 · as of 18 Nov 2026

What I do

From classification to inspected evidence

CRA readiness assessment

Classify every product against Annex III and IV using Implementing Regulation (EU) 2025/2392, run the gap analysis against Annex I, and draft the Art 13(2) risk assessment. You get the conformity route for each product — self-assessment, EU-type examination, or full quality assurance — and a prioritised remediation backlog, not a 90-page PDF that dies in a drawer.

The evidence layer

SBOM generation wired into your release pipeline (Syft, Trivy, OSV-Scanner), VEX statements that kill CVE noise, support-period end dates published on every product page, security.txt intake, and an Art 14 runbook drilled against the ENISA platform: 24-hour early-warning template, a named aware-officer function, and a submission rehearsal.

The program, built to operate

Your CRA program owns change management, access management, vulnerability handling, monitoring and evidence retention — one control fabric, one build, living in your repository. Handed over so your team operates it without me; every future obligation becomes a mapping, not a rebuild.

Open source steward readiness

If you sustain open source used in commercial contexts, Art 24 makes you a steward with duties from December 2027: a public cybersecurity policy, secure development and vulnerability handling, cooperation with authorities. I set up the policy and process — scaffolded on OpenChain / ORC WG material — and the Art 32(5) self-assessment route with public technical documentation.

Audit trails that survive inspection

Append-only command and event ledgers with actor attribution and occurrence times, immutable evidence stores with provenance pointers to the originals, and correlation keys across systems — so “what happened, when, who did it, and where is the original” is one query. I run exactly this architecture in my own production systems.

Three ways in: a readiness assessment (fixed scope, 2–4 weeks), an embedded program (3–6 months, built and handed over), or a workshop for your leadership and teams. Scope and pricing per engagement: ask directly.

Ten years of shipping

Regulation-readiness is an engineering problem

Wolt · payments

Compliance-critical payments across the EU

Found the “unknown unknown” that blocked a country launch 48 hours before go-live — an accounting-standard incompatibility six months of planning had missed. Then built the centralised VAT API for 23 European markets (100K+ transactions a day) and delivered Peppol e-invoicing for Greece, with Hungary and Bulgaria prepared.

primeXchange · e-invoicing

Certified for mandated e-invoicing

Built and certified a Peppol Access Point with Service Metadata Publisher: XRechnung and ZUGFeRD live across Germany, France, Greece, Spain and Poland. Mandated formats, hard deadlines, market access — the daily business the CRA turns every product into.

HORNBACH

Real-time streams for 1 M+ products, 169 stores

Replaced 28-hour nightly batch jobs with real-time change data capture — roughly a 1000× freshness improvement on the product data platform of a DIY retail giant.

SystemNix · my own production platform

40+ services, declaratively operated

A production Linux platform I build and operate solo: declarative NixOS across the fleet, full observability, secrets management, and VM-level integration tests gating every deployment. The operational discipline CRA evidence demands, running live.

Earlier

From 1M-player game servers to NASA

Game server infrastructure with more than a million users, white-label apps for small businesses, and confidential projects for NASA. Cloud foundations for billion-dollar and S&P 500 companies.

Credentials

Certified, and honest about it

iSAQB CPSA-F certified software architect (2023), Oracle Certified Associate Java SE 8. German & English (both C2). No invented titles: everything on this page traces to a certificate, a contract, or a primary source.

“Lars consistently demonstrated a strong bias for action — he didn’t wait around but took the initiative to push things forward. His decisiveness made a real difference to the pace and outcome of our work together.”

Timo Manunen · Treasury Manager, Wolt

“I can recommend Mr. Artmann to any employer seeking a highly skilled and ambitious Software Developer and forthcoming Software Architect.”

Dr. Ralf S. Engelschall · Apache Software Foundation founder

Verbatim from written references; published with consent.

How I work

Four rules I do not bend

  1. Primary sources, not marketing

    The Official Journal text and ENISA’s own platform — read on the day, cited so you can check. When something is analyst knowledge rather than a verified page, it is labelled as such.

  2. Evidence born machine-readable

    Compliance that rests on screenshots and chat approvals is a deficiency factory. Controls should emit their own audit evidence as a byproduct of shipping: MR approvals, CI records, IdP logs, SBOMs — retained immutably.

  3. Build the fabric once

    Change, access, vulnerability handling, monitoring, evidence retention: one control fabric in your repository — so the next obligation your products face is a mapping, not a rebuild.

  4. Verified and inferred, always labelled

    Every claim I hand you carries its provenance and an as-of date. If I could not verify it, you will know before a regulator does.