This website uses cookies to ensure you get the best experience.
Learn more.
A team restores service after an incident but has not identified the root cause or improved controls. What should follow recovery?
Published
- Treat recovery time as proof that the same incident cannot recur.
- Delete all evidence immediately because the application is healthy.
- Conduct a blameless review, identify control gaps, assign corrective actions, and update runbooks.
- Disable the detector that generated the incident to reduce future alerts.
Comments — 0
Sign in to comment