Uploaded May 2026 | Updated September 2026, 1 hour ago
Przemyslaw "Rogue" Roguski (Red Hat, PL)
Software Bills of Materials (SBOMs) are fundamental to modern software transparency, providing a component inventory vital for vulnerability management programs. However, in complex, modern build environments, especially those involving multistage builds, traditional analyzed SBOMs fail to provide the necessary detail, often grouping content from various build stages and layers into a single component. This session delves into the critical need for and implementation of Contextual SBOMs. A Contextual SBOM is an advanced form of the SBOM that captures origin of the content sourced from base image or build stages of the multistage builds. By precisely identifying content that is COPY-ied from builders in multistage builds , the Contextual SBOM enables a significant "shift-left" in security. This intelligence is essential for precise vulnerability management, allowing security teams to differentiate between transient build tools and actual product dependencies, thereby ensuring a verifiable, trusted software supply chain and proactively managing vulnerabilities during the build phase. Key Topics The Foundational Role of SBOMs: An overview of why SBOMs are critical for software transparency and establishing an effective organizational vulnerability program. The Challenge of “Legacy” SBOMs: Discussing the limitations of non-contextual SBOMs in modern containerized and multistage build environments, where content origin and dependencies are obscured. Defining Contextual SBOMs: An in-depth look at what a Contextual SBOM is and how it delivers the granular data required for precise vulnerability management. Establishing Content Relationships: The use of relationships (e.g., CONTAINS, DESCENDANT_OF) within the Contextual SBOM to accurately define how content is sourced from specific build layers. Identifying Build-Time Dependencies: Technical methods for parsing information from build layers, identifying and contextualizing content copied from different build steps. Examples of Contextual SBOMs effective usage.
---
Przemysław “Rogue” Roguski is a Security Architect at Red Hat who specializes in shift-left security initiatives focusing on embedding security best practices and attestation into the earliest stages of the SDLC. He contributes security analysis work on Red Hat OpenShift and other OpenShift-related products. He also designs security solutions and processes across Red Hat.
Przemysław “Rogue” Roguski is a Security Architect at Red Hat who specializes in shift-left security initiatives focusing on embedding security best practices and attestation into the earliest stages of the SDLC. He contributes security analysis work on Red Hat OpenShift and other OpenShift-related products. He also designs security solutions and processes across Red Hat.
He contributes to the security ecosystem as a member of the various SBOM/VEX working groups, an OASIS OpenEoX Technical Committee member and a key contributor to the CWE program.
Przemyslaw "Rogue" Roguski (Red Hat, PL)
Software Bills of Materials (SBOMs) are fundamental to modern software transparency, providing a component inventory vital for vulnerability management programs. However, in complex, modern build environments, especially those involving multistage builds, traditional analyzed SBOMs fail to provide the necessary detail, often grouping content from various build stages and layers into a single component. This session delves into the critical need for and implementation of Contextual SBOMs. A Contextual SBOM is an advanced form of the SBOM that captures origin of the content sourced from base image or build stages of the multistage builds. By precisely identifying content that is COPY-ied from builders in multistage builds , the Contextual SBOM enables a significant "shift-left" in security. This intelligence is essential for precise vulnerability management, allowing security teams to differentiate between transient build tools and actual product dependencies, thereby ensuring a verifiable, trusted software supply chain and proactively managing vulnerabilities during the build phase. Key Topics The Foundational Role of SBOMs: An overview of why SBOMs are critical for software transparency and establishing an effective organizational vulnerability program. The Challenge of “Legacy” SBOMs: Discussing the limitations of non-contextual SBOMs in modern containerized and multistage build environments, where content origin and dependencies are obscured. Defining Contextual SBOMs: An in-depth look at what a Contextual SBOM is and how it delivers the granular data required for precise vulnerability management. Establishing Content Relationships: The use of relationships (e.g., CONTAINS, DESCENDANT_OF) within the Contextual SBOM to accurately define how content is sourced from specific build layers. Identifying Build-Time Dependencies: Technical methods for parsing information from build layers, identifying and contextualizing content copied from different build steps. Examples of Contextual SBOMs effective usage.
---
Przemysław “Rogue” Roguski is a Security Architect at Red Hat who specializes in shift-left security initiatives focusing on embedding security best practices and attestation into the earliest stages of the SDLC. He contributes security analysis work on Red Hat OpenShift and other OpenShift-related products. He also designs security solutions and processes across Red Hat.
Przemysław “Rogue” Roguski is a Security Architect at Red Hat who specializes in shift-left security initiatives focusing on embedding security best practices and attestation into the earliest stages of the SDLC. He contributes security analysis work on Red Hat OpenShift and other OpenShift-related products. He also designs security solutions and processes across Red Hat.
He contributes to the security ecosystem as a member of the various SBOM/VEX working groups, an OASIS OpenEoX Technical Committee member and a key contributor to the CWE program.
