Add CRA Evidence Kit for customer SBOM integration#574
Open
sameehj wants to merge 1 commit into
Open
Conversation
wolfSSL-Fenrir-bot
left a comment
There was a problem hiding this comment.
Fenrir Automated Review — PR #574
Scan targets checked: wolfssl-examples-bugs, wolfssl-examples-src
No new issues found in the changed files. ✅
Self-contained cra-evidence/ with glossary, Evidence Map, fictional auditor packet, autotools/embedded SBOM scripts, and CI validation. Signed-off-by: Sameeh Jubran <sameeh@wolfssl.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a self-contained CRA Evidence Kit under
cra-evidence/for customers who ship products containing wolfSSL and need EU CRA–style software transparency (SBOM inventory and optional build provenance).This is not a compliance product: it shows how to obtain, validate, and nest wolfSSL component SBOMs inside a customer-owned product SBOM. Legal obligations remain with the manufacturer.
What’s included
EVIDENCE-MAP.md) — one-page handout: who owns what, Friday path, bomsh Linux-onlyCRA-Supply-Chain-Glossary.md) — customer terminology (self-contained in this repo)auditor-packet/) — fictional Acme Connect Gateway product SBOM referencing wolfSSL component SBOMs (SPDX + CycloneDX)wolfssl-component/— pinned autotools /make sbomsamples (what the product stub references)wolfssl-component-embedded/— pinned embedded /user_settings.h+gen-sbomdemo (different hash /source-merkleproperties)validate.sh— JSON sanity + product SPDX checksum sync (no wolfSSL build required)refresh-samples.sh— regen autotools samples + update product stub checksumgenerate-wolfssl-sbom.sh/generate-embedded-sbom.sh— regen component SBOMs whenWOLFSSL_DIRis set.github/workflows/cra-evidence.ymlrunsvalidate.shon changes undercra-evidence/Customer paths covered
make sbom→ nest in product SBOM; see autotools samplesuser_settings.hgen-sbomdemo with kituser_settings.h; see embedded samplesmake bomshdocumented as Linux build host only, not shipped in packetUpstream dependency
Regenerating component SBOMs requires a wolfSSL tree with SBOM support (
scripts/gen-sbom,make sbom). Pinned samples target wolfSSL 5.9.1 (seeVERSION).Related wolfSSL work: [link your wolfSSL SBOM/bomsh PR or branch here, e.g.
feat/sbom-bomsh]Integration guide (implementation detail | PR pending): https://github.com/MarkAtwood/wolfssl/blob/578fbee8902b98f48798c1fc2cec2a0e75dcb1f3/doc/CRA.md
Glossary note
cra-evidence/CRA-Supply-Chain-Glossary.mdis the customer-facing copy in this kit.wolfssl/doc/CRA-Supply-Chain-Glossary.mdshould stay in sync when both repos ship (see wolfSSLdoc/CRA.md).Test plan
CRA Evidence Kitworkflow passes on this PRcd cra-evidence && ./scripts/validate.sh(no wolfSSL build)WOLFSSL_DIRset,./scripts/refresh-samples.shand re-runvalidate.shexternalDocumentRefs/ CycloneDXbomref point atwolfssl-component/fileshashesandwolfssl:sbom:hash-kindReviewer focus