A company which manufactures ASICs for use in an IDS wants to ensure that the ASICs' code is not prone to buffer and integer overflows. The ASIC technology is copyrighted and the confidentiality of…

Question

Options

• ARegression testing by the manufacturer and integration testing by the third party
• BUser acceptance testing by the manufacturer and black box testing by the third party
• CDefect testing by the manufacturer and user acceptance testing by the third party
• DWhite box unit testing by the manufacturer and black box testing by the third party

• A
  8% (2)
• B
  23% (6)
• C
  8% (2)
• D
  62% (16)

Explanation

White box unit testing by the manufacturer and black box testing by the third party (D) satisfies both requirements. White box testing requires full access to the source code, allowing the internal team to directly inspect and test for buffer overflows, integer overflows, and other code-level vulnerabilities - which is appropriate since the manufacturer owns the code. Black box testing by the third party means the third-party tester receives no access to the proprietary source code, preserving confidentiality while still allowing independent verification of the application's external behavior. User acceptance testing (B, C) is designed to validate business requirements, not security vulnerabilities. Regression and integration testing (A) do not specifically address the code-level vulnerability testing required here.

No community discussion yet for this question.