Courseiva

CSSLP · domain

Secure Software Testing

Secure Software Testing on the CSSLP exam covers how verification activities are planned, designed, and executed across the lifecycle: unit, integration, system, and acceptance testing, plus fuzzing, static and dynamic analysis, code review, and regression testing. Questions are scenario-based, asking you to select test coverage, design test cases for authentication and API security, and choose tooling inputs that maximize defect discovery.

17 questions4 easy8 medium5 hard

Focused practice

Practice Secure Software Testing questions

Scored sessions drawing only from this domain — pick a length below.

What this domain covers

What to know about Secure Software Testing

You must be able to design and select tests that prove security controls work, not just that features function. The single most important thing is choosing inputs and coverage criteria that reach the vulnerable code path, especially for authentication, session, and API token handling.

Selecting fuzzing inputs and harnesses that maximize code coverage for compiled applications

Designing test cases for authentication bypass, including credential handling, session state, and access control checks

Building API authentication tests covering token issuance, transport protection, and authorization enforcement

Configuring fuzzers to supply valid JSON Web Tokens and session artifacts to REST endpoints

Watch out for

Common Secure Software Testing exam traps

  • ▸Treating fuzzing as random input generation and ignoring seed corpora, dictionaries, and coverage feedback that drive real path discovery.
  • ▸Testing only the happy-path login and omitting negative cases such as missing, malformed, expired, or replayed credentials and tokens.
  • ▸Fuzzing authenticated APIs without valid tokens, so requests are rejected early and deeper business logic is never exercised.

Question index

All Secure Software Testing questions (17)

Click any question to see the full explanation, or start a practice session above.

1

Which THREE factors should be considered when prioritizing findings from a DAST scan?

Hard
2

When designing a test case for secure API authentication, which THREE elements should be included?

Hard
3

Which TWO of the following represent common output formats for security testing reports?

Easy
4

A developer wants to ensure that a web application is resistant to SQL injection. Which test case should be included in the automated test suite?

Medium
5

Which TWO of the following practices are recommended when performing fuzz testing on a web service?

Medium
6

You are performing a fuzzing campaign on a REST API. The API uses JSON Web Tokens (JWT). What is the most effective way to include these tokens in the fuzzer input?

Hard
7

Which TWO of the following are primary benefits of integrating SAST into the early stages of the SDLC?

Medium
8

A security analyst is reviewing the results of a dynamic application security testing (DAST) scan against a REST API. The scan report includes several findings, but the analyst must prioritize remediation. Which two factors are most important to consider when triaging DAST findings for an API? (Choose two.)

Hard
9

When designing a test case for a secure authentication bypass, which THREE areas should be covered?

Medium
10

A security engineer is configuring SonarQube for a Java project. Which configuration step ensures that the SAST scan accurately identifies injection vulnerabilities by analyzing data flow paths?

Medium
11

When configuring a DAST scanner to test for Cross-Site Request Forgery (CSRF), what must the scanner be able to do?

Medium
12

A developer is using AFL (American Fuzzy Lop) for fuzzing a C++ application. What is the primary requirement for achieving high coverage?

Medium
13

During a manual penetration test, you discover an insecure direct object reference (IDOR). What is the most appropriate next step in the test case design for this finding?

Easy
14

Which TWO of the following are common challenges when implementing IAST?

Medium
15

A software development team is adopting a secure software testing strategy. They want to ensure that security testing is performed continuously and that feedback is provided to developers as early as possible. Which testing approach best aligns with this goal?

Easy
16

A security tester is performing interactive application security testing (IAST) on a Java web application. The IAST agent is deployed in the test environment and instruments the application during automated functional tests. The tester notices that the IAST tool reports a high number of false positives for SQL injection. What is the most likely cause of these false positives?

Hard
17

When performing automated security testing, which of the following is considered a 'false positive'?

Easy

Frequently asked questions

What does the Secure Software Testing domain cover on the CSSLP exam?
You must be able to design and select tests that prove security controls work, not just that features function. The single most important thing is choosing inputs and coverage criteria that reach the vulnerable code path, especially for authentication, session, and API token handling.
How many questions are in this domain?
This page lists all 17 Secure Software Testing questions in the CSSLP question bank. The actual exam draws from this domain proportionally to its weighting in the official exam blueprint.
What is the best way to practise this domain?
Start with a short focused session (10 questions) to identify gaps, then work through explanations. Repeat with a longer session once the weak areas feel solid.
Can I practise only Secure Software Testing questions?
Yes — the session launcher on this page filters questions to this domain only. Choose any session length for inline explanations and scoring.
(ISC)2 Certified Secure Software Lifecycle Professional (CSSLP) (CSSLP) Secure Software Testing Practice Questions