Carry out threat modelling, which is the work of finding and dealing with security design flaws in an application's design before any code is written. It is done by people with specific training who review the design and judge the security risk at every access level and every point of entry. The aim is to lay out the application, its architecture and its infrastructure in an orderly way so its weak points are understood.
Maintained by Gerard Blokdyk·Verified against the published standard ·Control text last updated
What else in your programme already covers this
This control maps to 48 controls across 20 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
NIST-CSF-ID.RA-03 Internal and external threats to the organization are identified and recorded
NIST-CSF-PR.PS-06 Secure software development practices are integrated, and their performance is monitored throughout the software development life cycle
You are reading one control. How much of CIS Controls v8 have you already done?
CIS Controls v8 CIS-16.14 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of CIS Controls v8 your existing evidence covers. Hold ISO 27001:2022 and 102 of 153 CIS Controls v8 controls already carry evidence.
Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 240 were rejected on the ISO 27001:2022 pair alone.