Search the courses, subjects, tracks, games and features, or jump straight to a page.
2 cards from this section. Quick, good the night before a test.
What does DAST stand for?
Think about how it tests applications.
Give an example of a runtime issue DAST may find.
Consider what happens when users interact with the application.
What is the primary focus of DAST?
Consider what makes DAST different from static testing methods.
True or False: DAST can identify vulnerabilities that occur only when the application is running.
Think about the nature of runtime issues.
Design a simple workflow to integrate DAST into an existing software development lifecycle that includes code reviews and deployment.
Think about where in the SDLC DAST will be most effective.
You encounter multiple false positives after running a DAST tool. Discuss approaches to handle these effectively.
Consider how integrating manual validation could improve the testing process.
4 more questions in this section. Enroll free to practise them all.
Enroll free