Repository navigation
feat(gates): the compliance mapping is gated — quality gate C3 (R16-2) - #151
Merged
Merged
Conversation
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
docs/COMPLIANCE_MAPPING.md went stale in seven places while nothing checked it, every one understating the controls. Its rows are re-verified against the tree, the stale notice is gone, and scripts/check_compliance_mapping.py derives the figures it rests on into a generated block, holds the prose's counts and scanner claims to them, refuses an undated measurement (here, in SECURITY.md and in docs/ADOPTION.md), requires one row and one verdict for each of the 22 CSF 2.0 Categories, and resolves file::symbol citations. The Checkov count was 104, not 114, and undated in three documents; most of its real findings are on the local stack, not the cloud Terraform. A new test asserts every implemented quality gate runs in a workflow, which nothing did. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
DuqueOM
force-pushed
the
docs/compliance-mapping-gate
branch
from
October 27, 2026 14:51
2031095 to
4ddaf65
Compare
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.
What and why
R16-2:
docs/COMPLIANCE_MAPPING.md, the NIST CSF 2.0 self-assessment, had gone stale in seven places while nothing checked it, and every one of them understated the controls. It said:The rows are re-verified against the tree. GV.OV, GV.SC, ID.RA, ID.IM, PR.AA, PR.PS, DE.CM, RS.MA and RC.RP are rewritten. The verdicts hold at 3 Satisfied, 14 Partial and 5 Not satisfied. The stale notice is removed, because nothing it listed is still true.
scripts/check_compliance_mapping.pyis quality gate C3, the gate the gate table had reserved since Phase 1. It:--write);SECURITY.mdanddocs/ADOPTION.md;SECURITY.md's Blocking column;file::symbolcitation.It runs in CI's fast gates,
make verify,make syncand pre-commit.The Checkov count was wrong in three documents and undated in all of them.
SECURITY.mdsaid it "currently finds 114". CI's Checkov reported 104 on 2026-10-09. Of the 91 Kubernetes findings, 58 are scan-scope artifacts, and most of the real ones are in the local stack's manifests, not the cloud Terraform.A new test asserts every implemented quality gate runs in a workflow. Nothing asserted that before: removing a gate's step from CI while leaving it in the Makefile went unnoticed.
Class
Evidence
Layer this evidence reaches:
make verify)platform/for the dated figuresDerived documents
The mapping's derived-figures block is generated by
check_compliance_mapping.py --write. Inventory, status and README checks pass.🤖 Generated with Claude Code