This guide specifies what evidence artifacts are expected at different assurance levels (AL1–AL4).
docs/guides/assurance-levels.mdexamples/al3-evidence-bundle/ and examples/al4-evidence-bundle/Legend:
| Artifact | AL1 | AL2 | AL3 | AL4 | Notes |
|---|---|---|---|---|---|
| Conformance evidence bundle | Required | Required | Required | Required | Protocol behavior assurance |
| TSPP posture evidence bundle | Required | Required | Required | Required | Deployment posture assurance |
| Combined Assurance Manifest | Recommended | Required | Required | Required | Required from AL2 upward to prevent provenance ambiguity |
| Version tuple declaration | Recommended | Required | Required | Required | Prefer tags; else main@<sha> |
| Evidence bundle checksums | Optional | Recommended | Required | Required | Integrity verification across hops |
| CI run link or provenance attestation | Optional | Recommended | Required | Required | CI URL acceptable early; migrate to attestations over time |
| Redaction report | Optional | Recommended | Required | Required | What was removed and why |
| Operator declaration | Optional | Optional | Recommended | Required | Authority context for high consequence |
| Retention policy pointer | Optional | Recommended | Required | Required | Evidence retention/access policy |
| Control catalog reference | Optional | Recommended | Required | Required | Stable control IDs enable auditability |
| Control Satisfaction Declaration | Optional | Recommended | Required | Required | Machine-readable control coverage and evidence links |
| Lifecycle Assertion | Optional | Recommended | Required | Required | Declares lifecycle state and transition evidence |
| Recognition Assertion | Optional | Optional | Recommended | Required | Signable recognition edges with scope + evidence |
| Certification Attestation | Optional | Optional | Recommended | Required | Binds assessor, scope, validity, and evidence to the certification claim |
| Revocation bulletin / notice | Optional | Optional | Recommended | Required | Structured notice for trust-impacting revocations |
examples/al3-evidence-bundle/examples/al4-evidence-bundle/The example bundles include realistic supporting artifacts (e.g., governance policy, trust list snapshot, signed conformance declaration, independent assessment report, and AL4 operational monitoring/change evidence) that an operator can adapt for their submission.
These examples are intentionally minimal and meant to be adapted to your environment.
These repositories act as evidence producers for the artifact rows above:
| Evidence artifact row | Primary producer | Canonical files |
|---|---|---|
| Conformance evidence bundle | TRQP Conformance Suite (CTS) | bundle_descriptor.json, checksums.json, bundle.zip |
| TSPP posture evidence bundle | TRQP-TSPP | bundle_descriptor.json, checksums.json, bundle.zip, tspp_posture_report.json |
Crosswalks:
For AL3+ evaluations, the Hub recommends collecting supply chain integrity evidence for the implementation:
| Artifact kind | Example artifact | Rationale |
|---|---|---|
software_sbom |
SPDX/CycloneDX SBOM | Dependency transparency for deployed artifacts |
build_provenance |
build attestation | Verifiable build chain and provenance |
openssf_scorecard_report |
Scorecard output | Automated checks on repo security practices |
Reference: docs/reference/openssf-supply-chain.md.