Framework overlap

Does ASD Strategies to Mitigate Cyber Security Incidents cover OWASP DevSecOps Maturity Model (DSOMM)?

You hold ASD Strategies to Mitigate Cyber Security Incidents and have been told to do OWASP DevSecOps Maturity Model (DSOMM). Here is how much overlaps, control by control.

100% of OWASP DevSecOps Maturity Model (DSOMM) you already have

ASD Strategies to Mitigate Cyber Security Incidents already covers about 100% of OWASP DevSecOps Maturity Model (DSOMM), leaving 0 of 6 controls as genuinely new work.

Already covered 4 Likely covered 2 New work 0

What is genuinely new work

Nothing in ASD Strategies to Mitigate Cyber Security Incidents reaches these. This is the list to scope.

Nothing. Every control is reached.

Show the 6 you already have
DSOMM-1
Culture, Organization, Education, and Governance
DSOMM-3
Build, Deployment, Infrastructure Hardening, and Secrets Management
DSOMM-4
Test and Verification - SAST, DAST, IAST, SCA, Penetration Testing
DSOMM-5
Information Gathering, Logging, Monitoring, and Incident Response
DSOMM-2
Implementation Practices, Secure Coding, and Threat Modelling
DSOMM-6
Metrics, Maturity Measurement, and Continuous Improvement

How this is calculated

Already covered means a mapping runs from a control in ASD Strategies to Mitigate Cyber Security Incidents to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition