CSSLP · Secure Software Testing

Read knowledge points freely. Practice, saved topics, progress and personal records require sign-in.

Choose a domain or section

205 knowledge points

Develop security testing strategy and plan

The testing strategy defines objectives, scope, methods, environments, roles, evidence, entry and exit criteria, defect handling, and release decision support.

Example: The test program owner should make testing risk-based and traceable to requirements, architecture, implementation, and misuse cases, with the testing depth and evidence justified for the release assurance plan.

Counterexample: The test program owner should treat a list of tools as a testing strategy. | The test program owner should apply identical depth despite different exposure and impact. | The test program owner should set completion criteria after seeing the results while assessing release assurance strategy.

Limitations: A list of tools is not a testing strategy.

Tradeoffs: Testing should be risk-based and traceable to requirements, architecture, implementation, and misuse cases.

CSSLP · Secure Software Testing

Develop security testing strategy and plan

Testing objectives

Risk-based test prioritization

Test scope

Entry criteria

Exit criteria

Standards for security testing

International Organization for Standardization testing guidance

Open Source Security Testing Methodology Manual

Software Engineering Institute testing resources

Functional security testing

Security logic testing

Nonfunctional security testing

Reliability testing

Performance security testing

Scalability security testing

Testing techniques

Known-environment testing

Unknown-environment testing

Gray-box testing

Functional testing technique

Acceptance testing technique

Testing environment

Environment fidelity

Environment isolation

Interoperability testing environment

Test harness

Test oracle

Test independence

Tester authorization and rules of engagement

Security researcher outreach

Bug bounty programs

Vulnerability disclosure policy

Coordinated vulnerability disclosure

Test evidence plan

Retest strategy

Develop security test cases

Test-case traceability

Positive security test cases

Negative security test cases

Boundary-value security tests

Attack surface validation

Automated vulnerability testing

Dynamic application security testing

Interactive application security testing

Runtime application instrumentation

Penetration testing

Penetration-testing lifecycle

Testing security controls

Known-vulnerability penetration tests

Known-malware test scenarios

Penetration-test scope and limitations

Fuzzing

Generated fuzzing

Mutation fuzzing

Coverage-guided fuzzing

Protocol and stateful fuzzing

Fuzzing crash triage

Simulation

Production-environment simulation

Production-data simulation

Synthetic transactions

Digital twins and model-based simulation

Failure testing

Fault injection

Stress testing

Break testing

Chaos engineering for security

Cryptographic validation

Pseudorandom-number-generator testing

Entropy validation

Known-answer cryptographic tests

Certificate and TLS validation tests

Unit testing and code coverage

Statement coverage

Branch coverage

Condition and path coverage

Mutation testing

Regression tests