Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Developer’s Nightmare: How To Survive Compl...

The Developer’s Nightmare: How To Survive Compliance Checklists (and Still Ship Fast)

You did it! The new feature you’ve been implementing is now ready and you can’t wait to ship it.

“Not so fast”. Oh no, it’s them: the guardians of compliance! You know what’s about to happen. You’ve been there before.

- Are you using any license that is not approved?
- Is there any CVE reported for the new dependencies you added?
- Can you guarantee the artifact running in production has not been tampered with?

Several checklists, paperwork, and meetings later, you’re finally approved for release. Not fun. Where did the developer joy go?

In this session, Alexandra and Thomas explore how to break the compliance barriers for developers, even in highly-regulated industries. The goal is to enhance the developer experience while letting the platform automate and enforce compliance and security checks.

You'll follow the mishaps of a developer and learn how to deal with compliance, using practical solutions based on OSS tools like Backstage, Dependency-Track, Sigstore and Buildpacks.

Avatar for Thomas Vitale

Thomas Vitale

March 26, 2026
Tweet

More Decks by Thomas Vitale

Other Decks in Technology

Transcript

  1. Alexandra Aldershaab & Thomas Vitale KubeCon+CloudNativeCon Europe 24th Mar 2026

    The Developer’s Nightmare How To Survive Compliance Checklists (and Still Ship Fast) @thomasvitale.com linkedin.com/in/housa
  2. SBOM “A Software Bill of Materials (SBOM) is a nested

    inventory for software, a list of ingredients that make up software components.” NTIA https://ntia.gov/SBOM linkedin.com/in/housa @thomasvitale.com
  3. SBOM as part of the build lifecycle Using the CycloneDX

    Gradle plugin for Java CycloneDX Gradle Plugin https://github.com/CycloneDX/cyclonedx-gradle-plugin linkedin.com/in/housa @thomasvitale.com
  4. SBOMs What can we use them for? Inventory of all

    software components Validate the licenses for each component Check for security vulnerabilities Find outdated components Verify integrity for each component linkedin.com/in/housa @thomasvitale.com
  5. VEX “Vulnerability Exploitability eXchange (VEX) is a vulnerability document designed

    to complement a Software Bill of Materials (SBOM) that informs users of a software product about the applicability of one or more vulnerability findings.” OpenVEX http://openvex.dev @vitalethomas
  6. The Developer’s Nightmare How To Survive Compliance Checklists (and Still

    Ship Fast) https://github.com/ThomasVitale/developers-nightmare https://github.com/ThomasVitale/kubecon-eu-2026-gitops Alexandra Aldershaab linkedin.com/in/housa Thomas Vitale @thomasvitale.com thomasvitale.com