7 docs tagged with "fuzzing"

How to use AI/GenAI to accelerate security testing (planning, triage, regressions, fuzzing and validation) without degrading evidence, confidentiality or human control

Strategies and practices for continuously validating application security through automated, manual and offensive testing.

Organisational policy that defines the requirements, execution criteria, findings management and responsibilities for dynamic security testing (DAST) and fuzzing, proportional to the application's risk level.

Testing with unexpected or malformed data to discover flaws in parsers, APIs and internal logic.

Strategies and practices for continuously validating application security through automated, manual and offensive testing

Canonical catalogue of requirements for the security testing programme (TST-001 to TST-010), with applicability by risk level and acceptance criteria for testing strategy, SAST, DAST, findings management, regression, pentesting and auditable evidence.

Organisational policy that defines the requirements for the security testing strategy throughout the application lifecycle, including SAST, DAST, SCA, IAST, fuzzing and manual testing, with mandatory gates, finding triage SLAs and centralised management of results, proportional to the criticality level (L1, L2, L3).