RC.CO-04.363

Has your organization documented an incident recovery plan that includes steps for both remediation and prevention of future similar incidents?

Explanation

An effective incident recovery plan should outline specific actions to restore normal operations after a security incident and implement measures to prevent recurrence. This includes root cause analysis, system restoration procedures, and specific security improvements to address identified vulnerabilities. Evidence could include a formal incident recovery document or playbook that details both immediate recovery actions and longer-term preventive measures, post-incident reports showing implemented improvements, or documentation of lessons learned sessions that resulted in specific security enhancements.

Implementation Example

Explain the steps being taken to recover from the incident and to prevent a recurrence

ID: RC.CO-04.363

Context

Function: RC: RECOVER
Category: RC.CO: Incident Recovery Communication
Sub-Category: Public updates on incident recovery are shared using approved methods and messaging

ResponseHub is the product I wish I had when I was a CTO

Previously I was co-founder and CTO of Progression, a VC backed HR-tech startup used by some of the biggest names in tech.

As our sales grew, security questionnaires quickly became one of my biggest pain-points. They were confusing, hard to delegate and arrived like London busses - 3 at a time!

I'm building ResponseHub so that other teams don't have to go through this. Leave the security questionnaires to us so you can get back to closing deals, shipping product and building your team.

Neil Cameron

Founder, ResponseHub