Q: 2
Which of the following will BEST help mitigate the risk associated with malicious functionality in
outsourced application development?
Options
Discussion
B , since test environments can catch issues that code reviews might miss, especially if the malicious code is only triggered under certain conditions. A feels like a strong pick, but sometimes dynamic analysis finds traps.
A since an in-depth code review by an expert is the strongest way to catch hidden malicious code before it goes live. Other options like SLAs or change management are important for overall process, but they won’t actually catch a developer sneaking something into the codebase. Testing environments might not trigger hidden logic either. Anyone think B could work if you had really comprehensive dynamic analysis?
Is the keyword here "BEST" referring to preventing malicious code before production, or just detecting any unwanted behavior? If it's strictly about code-level risk, I'd pick A.
Be respectful. No spam.