A team discovers several weaknesses in an application that is widely used across multiple departments. They want to address these issues using a structured process and reduce the chance of repeated findings in future evaluations. Which measure is most appropriate for this situation?
Set up manual scans once each year to limit inaccurate readings
Use a single filtering device that stops all inbound activity on the entire network
Remove the application from production and wait for new hardware before reactivating
Develop a structured remediation process with scheduled patch cycles and track the results
Developing a process with scheduled patch cycles and monitoring results targets weaknesses in a planned way. This maintains operational continuity and lowers the recurrence of the same weaknesses in the future. Removing the application from production until new hardware arrives disrupts business. Blocking all inbound connections is too broad and affects legitimate access. Conducting manual scans yearly is not frequent enough to track and address weaknesses consistently.
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 a structured remediation process?
Open an interactive chat with Bash
Why are scheduled patch cycles important?
Open an interactive chat with Bash
How does tracking remediation results help reduce future weaknesses?