[SM2.2: 42] Enforce gates with measurements and track exceptions.
SDLC security gates are enforced for every software project: to pass a gate, a project must either meet an established measure or obtain a waiver. Even recalcitrant project teams must now play along. The SSG tracks exceptions. A gate could require a project to undergo code review and remediate any critical findings before release. In some cases, gates are directly associated with controls required by regulations, contractual agreements, and other business obligations, and exceptions are tracked as required by statutory or regulatory drivers. In other cases, gate measures yield key performance indicators that are used to govern the process. A revolving door or a rubber stamp exception process does not count. If some projects are automatically passed, that defeats the purpose of enforcing gates. Even seemingly innocuous development projects, such as a new mobile client for an existing back-end or an application ported to a cloud environment from an internal data center, must successfully pass the prescribed security gates in order to progress. Similarly, APIs, frameworks, libraries, COTS, microservices, container configurations, and so on are all software that must traverse the security gates.