300-910 · Question #129
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 of the
The correct answer is B. dynamic application security testing. To automate black-box testing for runtime vulnerabilities within a CI/CD pipeline, Dynamic Application Security Testing (DAST) tools must be used.
Question
Options
- Avulnerability management
- Bdynamic application security testing
- Cthreat modeling
- Dsource code analysis tools
How the community answered
(19 responses)- A5% (1)
- B68% (13)
- C11% (2)
- D16% (3)
Why each option
To automate black-box testing for runtime vulnerabilities within a CI/CD pipeline, Dynamic Application Security Testing (DAST) tools must be used.
Vulnerability management is a broader process of identifying and remediating vulnerabilities, not a specific automated black-box testing tool for CI/CD.
Dynamic Application Security Testing (DAST) tools perform 'black-box' testing by actively scanning a running application from the outside, simulating real-world attacks to identify runtime vulnerabilities that manifest during execution in a CI/CD pipeline.
Threat modeling is a design-phase activity to identify potential threats before coding, not an automated black-box testing method for a running application.
Source code analysis tools (SAST) perform 'white-box' testing by analyzing code without execution and do not identify runtime vulnerabilities through black-box testing.
Concept tested: Automating DAST in CI-CD for runtime vulnerabilities.
Source: https://learn.microsoft.com/en-us/azure/security/develop/secure-devops-best-practices-static-analysis-dynamic-analysis
Topics
Community Discussion
No community discussion yet for this question.