Skip to content

docs(compliance): withdraw sbom cronjob claim and close poam-221 - #769

Merged
lahlfors merged 1 commit into
mainfrom
docs/qualify-sbom-claims
Nov 16, 2026
Merged

lahlfors merged 1 commit into
mainfrom
docs/qualify-sbom-claims

Conversation

@lahlfors

Copy link
Copy Markdown
Collaborator

Summary

Standalone compliance and documentation correction closing the remaining prose assertions identified by the repository-wide sbom / cyclonedx / grype / CronJob sweep (POAM-2026-010, POAM-2026-221):

  1. Withdraw Non-Existent Kubernetes SBOM CronJob & 24h Container-Scan Claims (compliance/risk_acceptance/THRESHOLD_TRACEABILITY_MATRIX.md, POAM-2026-010):

    • Terraform (infra/**) deploys only CronJob/lula-audit (module.lula_cron) — zero SBOM or vulnerability-scanning CronJob exists (de5534ac:deployment/k8s/sbom-cronjob.yaml was an unmanaged pre-Terraform manifest retired in #686, tracked under Open POAM-2026-010).
    • .github/workflows/sbom.yml builds and Trivy-scans the 4 shipped container images on PR/push only (no 0 2 * * * cron schedule), while .github/workflows/security-scan.yml runs daily at 02:00 UTC + PR/push against locked Python dependencies and the repository filesystem only, and no cage.sbom.last_generated_age_hours runtime gauge exists in src/.
    • Correct THR-AUD-003 (§2.1), CM-8 and RA-5 (§3), and RA-003 (§5.3) to state the actual CI schedules and open in-cluster scanning gap (POAM-2026-010) accurately, alongside the 2026-11-15 POAM-2026-221 qualification on Compensating Control (1) (security-scan.yml::sbom-generation vacuous across 1902c92c..9b2b745d, restored in #768 at b92a1719).
  2. Dated Addendum to Q2 2026 ISO 42001 Management Review (docs/compliance/universal/ISO42001_MANAGEMENT_REVIEW.md):

    • Preserve the 2026-06-23 §2.1 bullet (POAM-010 (RA-5): pip-audit / Trivy / Grype CI pipeline operational) verbatim as an auditable review record and append a dated 2026-11-15 addendum (> **Note (2026-11-15):**) recording that Python CVE coverage on 2026-06-23 rested on pip-audit and Trivy/Syft filesystem scanning rather than the vacuous Python Grype leg (POAM-2026-221, restored at b92a1719), and that periodic in-cluster scanning remains open under POAM-2026-010.
  3. Qualify P2-4 in docs/compliance/us_fed/NIST_RMF_CHUNK5_MONITOR_ROADMAP.md & Close POAM-2026-221 in docs/POAM.md:

    • Add a dated 2026-11-15 qualification on P2-4 (POAM-2026-221 / POAM-2026-010).
    • Record mainline squash SHA b92a1719 (#768, green mainline build run 43776695940 and Security Scanning run 43776695949), the full 209-row census + 33-Lula + US_FED SSP sbom/cyclonedx/grype sweep (0 HOLDS or implemented claims affected), and the repository-wide <sha>:/<sha>^: pin check (0 external pins to the retired 8-package SBOM) in POAM-2026-221, closing POAM-2026-221 (2026-11-15) and updating Open POAM-2026-010.

Verification

  • CAGE_ENV=ci CAGE_DEPLOYMENT_REGION={US_FED,EU_ECB,APAC_MAS} uv run python -m src.gateway.governance.oscal_ssp_exporter export --check -> all 3 regional SSPs current
  • uv run python scripts/check_doc_references.py -> 69 docs audited, 0 errors
  • uv run python scripts/check_poam_lula_divergence.py -> 258 rows (153 closed, 105 open), 0 divergences
  • uv run python scripts/check_oscal_claim_census.py -> 209 census entries validated against 208 OSCAL claims (0 errors)
  • uv run bandit -r src/ scripts/ -c pyproject.toml -ll -ii -> 0 High / 0 Medium issues
  • uv run pytest tests/test_oscal_ssp_exporter.py tests/test_check_poam_lula_divergence.py -q -> 125 passed, 3 skipped

@lahlfors lahlfors changed the title docs(compliance): withdraw nonexistent sbom cronjob claim and qualify poam-2026-221 docs(compliance): withdraw sbom cronjob claim and close poam-221 Nov 16, 2026
@lahlfors
lahlfors merged commit eca0c55 into main Nov 16, 2026
49 checks passed
@lahlfors
lahlfors deleted the docs/qualify-sbom-claims branch November 16, 2026 00:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant