Testing Proprietary-Software Compiled Code for Security Flaws

A.

The correct answer is B. Static review.

Static review, also known as static code analysis, is a method used to analyze software code without actually executing the code. This technique allows auditors to test proprietary-software compiled code for security flaws by analyzing the code structure and logic to detect potential vulnerabilities or bugs. Static code analysis tools can detect issues such as buffer overflows, SQL injection, and cross-site scripting (XSS) that may lead to security breaches.

Fuzzing, also known as fuzz testing, is a dynamic testing technique that involves sending random data inputs to a system or software application to test for unexpected behavior. Fuzzing can be used to identify vulnerabilities in proprietary software but is generally not as effective as static code analysis when it comes to testing compiled code.

Code signing is a security process that involves signing software code to ensure its authenticity and integrity. It does not help auditors test for security flaws in proprietary-software compiled code.

Regression testing is a type of testing that involves retesting a software application after changes have been made to ensure that the changes did not introduce new issues. It is not used for testing security flaws in proprietary-software compiled code.