White-Box Security Test Tools CT-STE Practice Questions (Page 2)

Questions 6–10

1. 6expert · hard

   A SAST tool is analyzing a web application and reports a stored XSS vulnerability. The data flow is: user input → database → HTML output. The tool also reports that the input is sanitized before being stored in the database. What is the most accurate interpretation of these findings?

   • AThe tool may be reporting a false positive because sanitization before storage may not prevent XSS if the output context is different.
   • BThe tool is reporting a false negative because it found the vulnerability but also reported sanitization.
   • CThe tool is definitely reporting a false positive because the input is sanitized.
   • DThe tool is definitely reporting a true positive because the data flows from user input to HTML output.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which of the following is a category of white-box security test tools?

   • AStatic Application Security Testing (SAST) tools
   • BPenetration testing tools
   • CInteractive Application Security Testing (IAST) tools
   • DDynamic Application Security Testing (DAST) tools
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What is a common way to integrate SAST tools into a CI/CD pipeline?

   • ARunning SAST only on the final release build.
   • BAdding a SAST scan as a step in the pipeline that runs on every code commit.
   • CRunning the SAST tool manually once a year.
   • DReplacing unit tests with SAST scans.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Which organizational factor should influence the selection of a white-box security test tool?

   • AThe color of the tool's logo.
   • BThe tool's ability to run on a specific operating system only.
   • CThe team's familiarity with the tool and its learning curve.
   • DThe tool's popularity on social media.
   Reveal Solution Discussion Select an answer first
6. 10application · medium

   A startup with a small team and a limited budget wants to add SAST to their CI pipeline. They use GitHub and GitHub Actions. Which approach is most cost-effective and practical for their context?

   • AUse a commercial SAST tool with a full-featured license and dedicated security team to manage it.
   • BUse a free or open-source SAST tool integrated into GitHub Actions, with findings reported as pull request comments.
   • COutsource SAST to a third-party service that runs scans monthly.
   • DRun SAST manually on a developer's laptop before each release.
   Reveal Solution Discussion Select an answer first