Fuzzing
What is Fuzzing?
An automated software testing technique that involves providing invalid, unexpected, or random data as inputs to a computer program. Fuzzing aims to discover coding errors and security vulnerabilities.
Frameworks that govern fuzzing
What the standards actually require on fuzzing
Requirements naming fuzzing across 3 standards, quoted from the control text.
Operate static analysis + fuzzing + testing per OpenSSF Scorecard checks SAST + Fuzzing + CI-Tests. Static Analysis SAST must (a) run SAST on every PR + (b) detect common security vulnerabilities (injection + authentication + authorisation + crypto + secrets +...
OSSFSC-5 · Static Analysis, Fuzzing, Testing Coverage →Operate security test + certification + conformance per O-RAN WG11 Security Test Specifications and WG11 Test Specifications including Open Test and Integration Center (OTIC) testing.
ORANWG11-6 · Security Test Specifications, Certification, and Conformance →Both passive techniques such as traffic monitoring and active techniques such as fuzzing and probing must be used to expose flaws in design, configuration, and implementation.
PTES-VA-2 · Active and Passive Testing →Questions people ask about fuzzing
What is Fuzzing?
Why is Fuzzing important for compliance?
Which compliance frameworks address Fuzzing?
Where can I learn more about Fuzzing?
See how Fuzzing applies across compliance frameworks
Our platform maps 686 frameworks with 311K cross-framework control mappings. Explore how this concept is addressed across standards.