ISTQB CT-SEC study guide
ISTQB CT-SEC · Work through your exam, one topic at a time.
The ISTQB® Certified Tester Security Tester (CT-SEC) is a Specialist-level qualification in the ISTQB® portfolio. Per the official ISTQB® site, the certification "focuses on planning, performing, and evaluating security tests from multiple perspectives including risk, requirements, vulnerability, and human factors," and "also covers security testing tools and standards." It sits alongside other specialist certifications such as CT-STE, CT-MAT and CT-PT, and the site describes the security test engineer release as "an important extension within ISTQB's portfolio," tracing the first security testing syllabus back to 2016. The ISTQB CT-SEC study guide has 4 sections and about 1,453 words.
01Security Testing Planning
Planning is where the exam expects you to show that security testing is risk-driven and traceable, not a generic scan bolted onto the end of a project. The plan must state what will be tested, against which threats, with which techniques, and when testing is complete.
398 words, about 2 min02Security Test Performance
This domain tests execution: choosing an approach, staying inside the rules of engagement, finding real weaknesses, and producing evidence a developer can act on. Knowledge level drives technique.
343 words, about 2 min03Evaluating Security Tests from Risk, Requirements, Vulnerability and Human-Factors Perspectives
Evaluation questions dominate the exam: given results, is the system acceptable, and what evidence supports that judgement? You need four lenses, not a single count of findings.
359 words, about 2 min04Security Testing Tools and Standards
The exam checks that you know what each tool family can and cannot do, and how standards turn vague security expectations into testable, reportable criteria. Tool families: SAST analyses source or bytecode without executing it (early, white-box, prone to false positives); DAST probes a running application (black-box, runtime, cannot see code paths); IAST uses runtime instrumentation; SCA inventories dependencies against known-vulnerability databases; fuzzers feed malformed input to find crashes and input-handling defects; interception proxies, network scanners and log/SIEM analysis support manual work.
353 words, about 2 min