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

Building a Secure Java Supply Chain in the Era ...

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

Building a Secure Java Supply Chain in the Era of the Cyber Resilience Act

Modern Java applications ship with many dependencies, making CVE tracking and remediation a continuous challenge. While many tools exist to detect vulnerabilities, managing them effectively across the full software lifecycle remains difficult. This talk describes how to build a secure Java supply chain using existing open-source tools.

We start by understanding what is inside our applications and how to detect CVE vulnerabilities. We then extend this into automated detection and remediation workflows. We end up exploring various real-life cases of treating vulnerabilities, from simple component upgrades to backporting patches if we cannot upgrade a component. Finally, we connect these practices to the EU Cyber Resilience Act, which introduces formal requirements for vulnerability management and software transparency.

You will understand how these legal requirements affect software producers and how the presented process maps directly to them. A live demo demonstrates CVE detection, fixing, SBOM generation, and redeployment in a Java application pipeline, showing how to turn security into a continuous part of delivery rather than an occasional audit.

OmniFish Presentations

November 09, 2026

Transcript

17 slides
  1. Building a Secure Java Supply Chain in the Era of

    the Cyber Resilience Act How do we keep our apps secure after we ship them? Ondro Mihályi, OmniFish @ONDROMIH
  2. What did we ship? Your application code you own Direct

    dependencies library A: you declare it Transitive dependencies library B: it brings it in library B arrives through library A, even if nobody added it directly. An SBOM records the components of one release. A Maven SBOM describes the Maven dependency view. Check it against what actually ships: app server, JDK, OS packages.
  3. How do we find vulnerable components? Maven dependencies Packaged artifacts

    OWASP Maven plugin (NVD, OSS Index), OSV scanner (CLI) Scanner component + version Finding release R1 · library B An SBOM Shading, missing metadata and backported fixes can confuse matching.
  4. What is vulnerable? Find it in public databases NVD: https://nvd.nist.gov

    GitHub Advisory Database: https://github.com/advisories Mitre: https://www.cve.org Sonatype OSS Index: https://guide.sonatype.com OSV: https://osv.dev • • • • Severity info Component identifier Affected & Fixed versions References to reports and patches
  5. Does this finding affect our release? 01 02 03 04

    Is the component actually present? Is there a fix, workaround or backport? Is the vulnerable code exposed or used? Record the decision and a review date A version match is a finding, not a verdict.
  6. Can we upgrade the component? Jackson Databind DEMO 2:00 CVE-2026-59889

    · CVE-2026-54515 › Find the dependency coordinates › Upgrade to a fixed release › Build and rescan ON SCREEN 1 The scan finding 2 Dependency and resolved version 3 The upgrade pull request 4 Build or test result
  7. What if we cannot easily upgrade? OUR APPLICATION WHERE THE

    FIX IS we run this today a major jump from 2.3.7 JAXB RI 2.3.7 4.0.x › No fix in the 2.3.x line ON SCREEN 1 Resolved 2.3.7 dependency › Moving to 4.0.x is not easy 2 Where the fix landed DEMO 2:00
  8. How can we fix the older version? Maintained older branch

    The project still ships security releases Supported vendor build Someone else maintains the patch for you DEMO 2:00 Your own backport You adapt the fix and own it from now on Test it · record the patch · track the fixed build Scanners don’t recognize the new patched version ↣ suppress the vulnerability
  9. How do we build this into delivery? Build Scan One

    decision per finding fix now, or approve an exception A gate needs a deliberate threshold. Assess Fix Test Exceptions stay visible owner, reason, review date OWASP Dependency-Check defaults to failBuildOnCVSS 11, so nothing fails. Set your own, e.g. 7.0 Deploy
  10. Where does the scan run? · BEFORE CHANGES REACH PRODUCTION

    Build Vulnerability scan WHEN THE SCAN FAILS New task · temporary suppression Test Vulnerability scan FINAL CHECK Deploy to prod Avoid deploying vulnerabilities
  11. What happens after release? New advisory Check released versions ›Scan

    without a new build ›Keep exceptions visible ›Show production risk to managers A suppression is not a fix. Create a task Fix and redeploy
  12. Where does the scan run? · ON A SCHEDULE, AGAINST

    PRODUCTION VERSIONS Download binary, pom.xml or SBOM Vulnerability scan WHEN THE SCAN FAILS No new build, no new commit. Build fails · new task Temporary suppression · notification sent
  13. Who is responsible under the CRA? The manufacturer is responsible

    for the product, including integrated components. 10 Dec 2024 11 Sep 2026 11 Dec 2027 Entry into force Reporting incidents (ENISA) Most other duties (risk assessments, vulnerabilityhandling policies, conformity assessment, ...) Support period: generally at least five years, unless expected use is shorter.
  14. How does our process support CRA duties? OUR PRACTICE THE

    CRA DUTY Inventory every release SBOM, machine-readable Assess and monitor Vulnerability handling Fix and test Security updates in support Keep evidence Conformity assessment Report when required Authorities and users Tools support these duties. On their own they do not prove compliance.
  15. What changed in the new release? BEFORE NEW SBOM AFTER

    The finding Component and version Scan scope Linked to the build Scope stated Kept with the release Finding resolved Version confirmed Tests passed An SBOM describes what you built, not everything the server ends up running. DEMO 2:00
  16. How do we keep the release secure? Know what you

    ship an inventory for every release Monitor what runs Continuous scanning, track temporary suppressions Assess, fix, verify Master the process Keep the decisions and the evidence. Or you risk loosing track of what was fixed.
  17. Thank You! Questions? GlassFish Server Support Security Patches for Payara

    Server https://omnifish.ee Jakarta EE Consultancy Jakarta EE Training OmniFish - Jakarta EE Consulting & Support

More Decks by OmniFish Presentations

Other Decks in Technology