Workshops: Secure Agentic Coding & Governance

EU Cyber Resilience Act for Developers: Agentic Coding Workshop

The EU Cyber Resilience Act makes cybersecurity a condition for placing products with digital elements on the EU market, standalone software included. For development teams that means secure defaults, a documented vulnerability handling process, SBOMs and security updates throughout a defined support period. This advanced workshop translates the requirements into engineering work and shows where coding agents such as Claude Code, OpenAI Codex or GitHub Copilot speed it up, and where they add obligations of their own.

Who is this workshop for?

  • Product security teams and PSIRTs at software and device manufacturers
  • Software architects and tech leads of products sold in the EU
  • Embedded and IoT firmware teams
  • Product owners responsible for support periods and update policies
  • Compliance and regulatory managers working with engineering
  • Open source program offices

What you will take away

  • Explain which products the CRA covers, what its essential requirements expect from engineering and how obligations differ by product category.
  • Generate machine-readable SBOMs in your pipeline and keep them accurate when agents add dependencies.
  • Set up a vulnerability handling process with triage, fixes, backports and coordinated disclosure, with agents doing the groundwork.
  • Have agents draft risk assessments and parts of the technical documentation that your engineers then verify.
  • Identify the gaps between your current development practice and the CRA requirements, and prioritise them.

Agenda

  1. Module 1

    The CRA from an engineering perspective

    • Scope: products with digital elements, standalone software, open-source and SaaS boundaries
    • Essential requirements for product properties and vulnerability handling
    • Product categories, conformity assessment and CE marking in overview
  2. Module 2

    Secure by design and by default

    • The cybersecurity risk assessment as a living artefact
    • Exercise: an agent-assisted risk assessment for a sample feature
    • Secure default configuration, attack surface, update mechanisms
  3. Module 3

    SBOM and component management

    • SBOM formats such as CycloneDX and SPDX, generated in CI
    • Due diligence for third-party and open-source components
    • Dependencies added by agents: rules and automatic checks
  4. Module 4

    Vulnerability handling

    • Intake, triage and VEX statements on exploitability
    • Exercise: agents backporting a security fix to several supported versions
    • Coordinated disclosure and reporting duties for actively exploited vulnerabilities
  5. Module 5

    Documentation and roadmap

    • Agents drafting technical documentation, people verifying it
    • Evidence from pipelines instead of manual reports
    • Gap analysis and prioritised roadmap

Where agents help, and where they create work

Much of what the CRA demands is diligent, repetitive engineering: keeping SBOMs current, checking whether a dependency vulnerability actually affects your product, backporting fixes and documenting decisions. Coding agents can do much of this groundwork quickly, provided their results are reviewed.

At the same time agents change your product: they add dependencies, generate configuration and write code paths that must meet the same requirements. A CRA-ready process treats agent output like any other contribution, with the same checks and the same evidence.

Accurate, not alarmist

The CRA applies in stages, its reporting obligations apply earlier than most other requirements, and the supporting harmonised standards and guidance continue to evolve. We explain the regulation as it stands and point to official sources; the legal classification of your products stays with your legal and compliance team.

The workshop is led by neooutput AI Solutions Architects and AI Code Engineers. jocapps is ISO 27001 certified, and vulnerability processes are part of our own practice. We adapt the content to your product type, whether embedded, desktop, mobile or B2B software, remotely or on-site.

Frequently asked questions

Does the CRA apply to our SaaS product?

Pure software-as-a-service is generally covered by other rules such as NIS2 rather than the CRA. Remote data processing that a product needs to perform its functions can, however, fall within scope. We review your portfolio together; the legal classification stays with your legal team.

Does the CRA require an SBOM?

Yes. Manufacturers must identify and document the components of their products, including an SBOM in a commonly used, machine-readable format that covers at least the top-level dependencies. It is part of the technical documentation and does not necessarily have to be published.

Can we use AI-generated code in CRA-relevant products?

The CRA does not prohibit it. What matters is that the product meets the essential requirements and that you can demonstrate it. Agent-generated code therefore needs the same reviews, tests and evidence as code written by people.

Workshop

Get in touch

Where does your product stand against the Cyber Resilience Act, and what could agents take off your team's plate?

Tell us roughly how many people will join and pick dates that work – we will get back to you within 24 hours with a proposal for content, format and schedule.

Prefer to talk first?

15 minutes, free and without obligation – with our AI Trainers and AI Code Engineers.

Book a call for free (opens in new tab) +49 761 519 751 50 (24/7)

Request a training / workshop

Workshop: EU Cyber Resilience Act for Developers: Agentic Coding Workshop · 1 day

Dates that work for you (optional)

Suggestions about 2 weeks ahead – pick as many as you like

Reply usually within 24 hours · jocapps is ISO 27001 certified · Privacy