A tailored course, built for your situation
Reference of choice on SBOM governance calls across your ecosystem
Become the named authority peers turn to when software supply chain decisions need grounding
Who this is for
Senior technical practitioner influencing software supply chain governance through toolchain design and policy implementation
Who this is not for
This is not for junior analysts, entry-level compliance staff, or those without influence over software delivery or security tooling decisions.
What you walk away with
- Named reference in cross-organizational SBOM discussions
- Artefacts and narratives adopted by peers without modification
- Confident, source-backed responses to vendor and partner challenges
- Repeatable SBOM structuring that becomes team standard
- Visibility in ecosystem conversations beyond your immediate team
The 12 modules (with all 144 chapters)
- Defining SBOM beyond compliance
- Mapping stakeholders by dependency
- Identifying decision leverage points
- Aligning with software delivery rhythm
- Linking to incident response
- Connecting to vendor onboarding
- Tracking ecosystem adoption signals
- Benchmarking internal maturity
- Setting expectations with engineering
- Documenting scope boundaries
- Establishing feedback loops
- Versioning policy basics
- Choosing between SPDX and CycloneDX
- Normalising component naming
- Handling dynamic dependencies
- Including provenance metadata
- Excluding irrelevant components
- Versioning component references
- Adding relationship clarity
- Documenting toolchain source
- Adding licensing annotations
- Structuring for automation
- Optimising file size and parse speed
- Validating schema conformance
- Identifying generation triggers
- Capturing build-time context
- Scanning container layers
- Analyzing package managers
- Detecting transitive dependencies
- Integrating SCA output
- Validating against runtime profiles
- Automating format conversion
- Signing SBOM artefacts
- Storing with build artifacts
- Version linking to releases
- Handling ephemeral builds
- Checking required fields
- Confirming component hierarchy
- Validating SPDX ID uniqueness
- Cross-referencing build logs
- Matching runtime inventory
- Reviewing license accuracy
- Auditing dependency depth
- Checking for obfuscation
- Verifying timestamp integrity
- Ensuring human readability
- Testing machine parseability
- Documenting exceptions
- Mapping components to license types
- Highlighting copyleft risks
- Summarising obligations clearly
- Identifying attribution requirements
- Documenting license compatibility
- Flagging unapproved licenses
- Creating legal executive summaries
- Linking to vendor contracts
- Responding to audit requests
- Updating policy in response to change
- Archiving for future reference
- Training legal on key fields
- Signing with digital certificates
- Choosing signature scope
- Using cosign for attestations
- Verifying signature authenticity
- Logging access attempts
- Controlling distribution channels
- Encrypting sensitive metadata
- Auditing changes over time
- Integrating with PKI
- Documenting revocation process
- Storing in immutable storage
- Monitoring for anomalies
- Linking CVEs to components
- Prioritising by exploit likelihood
- Mapping SBOM to asset inventory
- Automating impact assessment
- Sharing with SOC teams
- Updating during patch cycles
- Documenting response rationale
- Creating runbooks for reuse
- Archiving for post-event review
- Improving future accuracy
- Validating fix completeness
- Reporting resolution status
- Assigning stewardship roles
- Setting update frequency
- Defining approval workflows
- Creating versioning rules
- Establishing quality gates
- Documenting change rationale
- Reviewing with cross-functional leads
- Auditing governance adherence
- Measuring improvement over time
- Adjusting for scale
- Publishing governance charter
- Training new contributors
- Requesting SBOM at procurement
- Validating third-party SBOMs
- Assessing completeness gaps
- Responding to format mismatches
- Negotiating quality improvements
- Documenting acceptance criteria
- Archiving vendor submissions
- Tracking supplier progress
- Using SBOM in due diligence
- Providing feedback loops
- Standardising templates
- Automating ingestion
- Normalising output formats
- Creating transformation pipelines
- Validating across tools
- Handling schema drift
- Using middleware layers
- Building compatibility tables
- Testing across environments
- Documenting known issues
- Sharing best practices
- Optimising for scale
- Reducing conversion overhead
- Standardising naming
- Creating onboarding materials
- Running hands-on workshops
- Developing internal documentation
- Providing templates
- Offering review support
- Celebrating improvements
- Publishing common mistakes
- Gamifying accuracy
- Sharing success stories
- Gathering feedback
- Iterating on resources
- Measuring fluency growth
- Publishing internal playbooks
- Presenting at cross-team forums
- Writing case studies
- Sharing templates externally
- Contributing to open standards
- Engaging with working groups
- Mentoring peers
- Responding to ecosystem queries
- Tracking citations
- Updating for new regulations
- Maintaining version history
- Archiving deprecated versions
How this maps to your situation
- Preparing for external audit or certification
- Rolling out new toolchain integration
- Responding to vendor due diligence request
- Leading internal software transparency initiative
Before vs. after
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3-4 hours per module, designed for integration into real-world work over 6-8 weeks.
How this compares to the alternatives
Unlike generic security certifications or tool-specific trainings, this course focuses on the cross-cutting governance and influence patterns that make SBOM work stick and scale across organisations.
Frequently asked
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.