Risk-Based Approach
Trying to create software and hardware that has no bugs or weaknesses in it at all is a difficult ask - invariably due to third-party dependencies, time pressures, or a lack of clarity of requirements, it is inevitable that things will be built in such a way that introduces security risks, that can be abused by an attacker in ways that haven’t been thought of.
These vulnerabilities need to be prioritised considering the organisation’s context, what mitigations are in place and the wider threat landscape, to enable focussed efforts on the areas that would have the biggest impact on reducing risk to the organisation or those that are actively being exploited in the wild.