Where the test uses threat modelling, the organisation ensures a consistent and repeatable model is used that represents threats and their capabilities as they apply to the organisation and can be reapplied to future tests with comparable results. The model is anchored on the organisation's own business assets and processes (identifying primary and secondary assets, critical versus non-critical processes, and the relevant threat communities and their capabilities), drawing on the organisation's documentation and interviews. This leaf governs that the model is asset-grounded and repeatable, so results can be compared over time and support risk decisions.
This control maps to 2 controls across 2 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 2 it maps to, and the evidence behind each claim, over MCP and REST.