To reduce accidental security errors while prioritizing release speed and agility, which two actions should you take?

To reduce accidental security errors while maintaining release speed, integrate security checks directly into the CI/CD pipeline. Running source-code security analyzers (Static Application Security Testing - SAST) identifies vulnerabilities early in the development cycle, as code is written. Running a vulnerability scanner (Dynamic Application Security Testing - DAST) against deployed applications in non-production environments catches issues that SAST might miss, like configuration errors or runtime flaws. Both are automated and fast, supporting agility. Requiring every check-in to be peer-reviewed by a security SME is too slow and creates a bottleneck. Stubs for unit testing focus on functional correctness, not security. Code signing and a trusted binary repository ensure integrity of artifacts but don't actively find security flaws in the code or deployed application.