SY0-301 · Question #829
When integrating source material from an open source project into a highly secure environment, which of the following precautions should prevent hidden threats?
The correct answer is B. Code review. Code review is the most direct method to detect hidden malicious logic, backdoors, or vulnerabilities embedded in open source source code before integration.
Question
When integrating source material from an open source project into a highly secure environment, which of the following precautions should prevent hidden threats?
Options
- ADesign review
- BCode review
- CRisk assessment
- DVulnerability scan
How the community answered
(32 responses)- A6% (2)
- B75% (24)
- C3% (1)
- D16% (5)
Why each option
Code review is the most direct method to detect hidden malicious logic, backdoors, or vulnerabilities embedded in open source source code before integration.
A design review evaluates the architectural approach of a system but does not inspect actual source code for hidden malicious logic.
When integrating open source code into a secure environment, a thorough code review allows security personnel to manually inspect every line for logic bombs, backdoors, obfuscated malicious functions, or insecure coding practices that automated tools may miss. This directly addresses hidden threats that could be intentionally embedded by a malicious contributor.
A risk assessment identifies and evaluates potential risks at a high level but does not involve direct inspection of source code for embedded threats.
A vulnerability scan identifies known, publicly documented vulnerabilities using signatures, but will not detect novel or custom-written malicious code hidden in the source.
Concept tested: Code review for detecting malicious open source code
Source: https://owasp.org/www-project-code-review-guide/
Topics
Community Discussion
No community discussion yet for this question.