Which of the following allows an auditor to test proprietary-software compiled code for security flaws?

Fuzzing dynamically tests compiled software by injecting a high volume of invalid, malformed, or unexpected data as inputs into the program or its APIs. This process is designed to uncover hidden security vulnerabilities, such as buffer overflows, memory leaks, or denial-of-service conditions, within the executable code without requiring access to the original source code, making it ideal for proprietary applications.

Static review analyzes source code for vulnerabilities without executing the program, which is not feasible for an auditor testing proprietary compiled code where source code is typically unavailable.

Code signing verifies the authenticity and integrity of software using digital signatures, assuring that it hasn't been tampered with, but it does not actively test the code for intrinsic security flaws.

Regression testing ensures that new changes have not introduced new defects or reintroduced old ones, focusing on maintaining existing functionality rather than primarily discovering new security vulnerabilities in compiled code.