Fix conformance rule inconsistency, compliance matrix accuracy, citations, and structural defects#62
Merged
jinsonvarghese merged 35 commits intoJun 11, 2026
Conversation
jinsonvarghese
changed the title
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
1 participant
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.
The standard currently gives two conflicting definitions of tier conformance. The Introduction and Glossary require 100% of MUST and SHOULD requirements with no deviation, while every domain Conformance section requires only the MUST requirements, with SHOULDs interpreted per RFC 2119.
This PR resolves the conflict as follows: a tier claim requires every MUST requirement implemented with no deviation, and every SHOULD requirement either implemented or covered by a documented justification recorded in the conformance claim (see the SHOULD Deviations section of the Conformance Claim Template). An undocumented SHOULD deviation is a conformance gap.
This reading follows the Frontispiece's existing RFC 2119 definition of SHOULD ("deviation requires documented justification") and mirrors the documented-exception pattern used in ISO/IEC 27001 Statements of Applicability. No requirement IDs, tiers, or MUST/SHOULD classifications change. The PR also corrects factual errors in the Compliance Matrix, citation inaccuracies, and structural defects; see the file changes.
Per GOVERNANCE.md, the conformance clarification in this PR is being treated as a decision affecting tier definitions and carries approval from both project leads. All other changes are defect corrections (citations, compliance mapping accuracy, structural repairs) handled as day-to-day fixes.