During an inspection of recent changes, the team notices that a library update may reduce reliability for certain operations. Which action best addresses these findings to maintain secure development?
Conduct extensive scenario-based tests aligned to defined guidelines and integrate improvements in a subsequent update
Rely on manual checks from the original contributor and proceed if no concerns appear
Enable detailed error logging, review production data, and address recurring issues promptly
Remove the library to mitigate the identified risk associated with the newly discovered weakness
Conducting wide-ranging tests and mapping them to documented standards pinpoints any undiscovered issues before release. This comprehensive approach goes beyond smaller checks or relying on user reports, and mitigates potential risks without discarding important functionality. Other options either involve minimal review, remove useful features outright, or wait until complaints appear in production, which can leave unseen gaps and conflict with secure development priorities.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is scenario-based testing in the context of secure development?
Open an interactive chat with Bash
Why is it important to follow documented standards during software testing?
Open an interactive chat with Bash
How does removing a library to mitigate risk impact secure development?