Uh oh!
There was an error while loading. Please reload this page.
Fix remaining Identity and Access Management reference issues - #83
Merged
wurstbrot merged 1 commit intoAug 21, 2026
Merged
Conversation
Follow-up to devsecopsmaturitymodel#82: removes the duplicate MFA UUIDs left in InfrastructureHardening.yaml (reintroduced by a main merge, already moved to IdentityAndAccessManagement.yaml), moves architecture/technology decisions (IdP, fine-grained access, policy-as-code, MFA, workload identity) off the generic O-EM-A SAMM2 code onto D-SA, fixes an Account inventory ISO 2013/2022 control mismatch, and adds verified MITRE D3FEND mappings where a real technique applies.
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 freeto 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.
Follow-up to #82 — after that PR merged with just the applied review suggestions, a few more things I'd found in review were still outstanding:
InfrastructureHardening.yaml— same UUIDs as their new home inIdentityAndAccessManagement.yaml, reintroduced by amainmerge on the old branch after they'd already been moved.O-EM-ASAMM2 code ontoD-SA(checked against the SAMM v2 model): central IdP, fine-grained access controls, policy-as-code, MFA (both), workload identity. Left JIT and risk-adaptive access onO-EM-Asince those are runtime/operational controls, not design decisions.9.2.1was paired with8.2, which actually comes from9.2.3, and isn't semantically about inventory anyway).9.4.1→9.2.3control on Continuous/risk-adaptive access so it actually pairs with the8.2already listed.d3f) mappings where a real technique applies (verified against d3fend.mitre.org): password auth, token-based auth, access modeling, certificate-based auth, user behavior analysis.No duplicate UUIDs remain in
Implementation/*.yamland both files validate as YAML.