A development team is using CI/CD during application development. During the latest releases runtime vulnerabilities have been indicated to address these vulnerabilities. A complete redesign o?the aff

Source code analysis tools (Static Application Security Testing - SAST) analyze an application's source code, bytecode, or binary code to detect security vulnerabilities early in the development lifecycle. By integrating SAST into a CI/CD pipeline, runtime vulnerabilities can be identified and remediated *before* deployment, significantly reducing the need for costly redesigns and preventing them from reaching production, aligning with a shift-left security approach.

Dynamic Application Security Testing (DAST) performs black box testing against a running application to find vulnerabilities, which is useful for runtime issues but typically occurs later in the pipeline and might still lead to redesigns if issues are found too late.

Threat modeling is a design-phase activity to identify potential threats and vulnerabilities, not an automated testing tool within a CI/CD pipeline.

Vulnerability management is a broader process of identifying, assessing, and remediating vulnerabilities, encompassing various tools and strategies, not a specific automated testing tool itself for a CI/CD pipeline.