Skip to content

ci: stamp SBOM creator and sign build provenance attestations - #29

Merged
opensource-SantanderAI merged 1 commit into
mainfrom
security/sbom-provenance
Jul 10, 2026
Merged

ci: stamp SBOM creator and sign build provenance attestations#29
opensource-SantanderAI merged 1 commit into
mainfrom
security/sbom-provenance

Conversation

@opensource-SantanderAI

Copy link
Copy Markdown
Contributor

What

  1. Stamps Santander Group as SBOM document creator (SPDX creationInfo.creators) and Open Source Santander AI as CycloneDX metadata.authors, keeping the generating-tool attribution.
  2. Signs a build provenance attestation (Sigstore) for both SBOM files via actions/attest-build-provenance — anyone can verify origin repo, commit and workflow with gh attestation verify <file> -R SantanderAI/gen-fraud-graph.
  3. Release assets are now uploaded after stamping/attesting (least-privilege scopes at job level only).

Why

Artifact traceability: SBOMs become tamper-evident and correctly attributed. First step of the org-wide provenance rollout.

Verification

Manual dispatch produces stamped SBOMs as artifacts; gh attestation verify passes against them.

- SPDX creators now include 'Organization: Santander Group' and the
  CycloneDX metadata.authors identify Open Source Santander AI (the
  generating tool attribution is kept, as the spec recommends).
- Every SBOM is now attested with actions/attest-build-provenance
  (Sigstore): consumers can verify origin, commit and workflow with
  'gh attestation verify <file> -R SantanderAI/<repo>'.
- Release assets are uploaded after stamping (previously the action
  uploaded them at generation time).
@opensource-SantanderAI
opensource-SantanderAI requested review from a team as code owners July 10, 2026 08:49
@opensource-SantanderAI
opensource-SantanderAI merged commit 1ab6a90 into main Jul 10, 2026
11 checks passed
@opensource-SantanderAI
opensource-SantanderAI deleted the security/sbom-provenance branch July 10, 2026 08:51
@github-actions github-actions Bot locked and limited conversation to collaborators Jul 10, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant