An incident response plan is not a nice to have. From major weather events to cyber security hacks, occurrences of major, adverse events impacting I.T. systems are increasingly common. Businesses who have taken the time to plan the steps they'll take to respond to such an event will always come out the other side faster and in a better position, than those who must react on the fly.
An I.T. or cyber-security incident response plan is a crucial document that sets out exactly how a business will deal with a major, adverse I.T. or cyber-security event. A good incident response plan will establish a clear protocol on questions such as:
An incident response plan won't solve your problem, but it will put you in the best possible position to be able to respond to a major situation calmly, clearly and quickly. It is a crucial part of business continuity planning and governance. The development of it must be led internally by business leaders, who can then consult with external I.T. providers for technical support and knowledge when needed.
If you've been thinking about developing or updating your incident response plan, here are some key questions your business should be asking to help define what your plan will look like, and who needs to be involved.
While this might seem a bit of a no-brainer, there are good ways to be alerted to an adverse I.T. event and there are bad ways...
Good questions for leadership teams to discuss here are:
Is it an 'event' or is it an 'incident'? Is it major or minor? Having a clear definition of what constitutes an event versus an incident and whether it is major, or minor is key to determining how your business will respond and the escalation chain.
Thinking on this, your business should ask:
Having one person lead the overarching response is key to an effective and efficient response. This person should be a leader in the business who is comfortable collaborating with a wide range of stakeholders and who understands the impact of decisions being made and can make critical decisions as required.
This person should not be an I.T. leader by default - remember if a major incident occurs, it'll likely be all hands on deck for the I.T. team.
If your business is large enough then you'll want to consider building out an incident response team to support the incident response manager. Expertise this team should provide include:
Once an incident has been reported internally, it's likely you'll need to report it externally to certain stakeholders:
Resolving the incident is of course your number one priority, but while the response is underway it's crucial to keep staff and customers up to date with your response.
Think about the demands of responding to a major I.T. incident and consider the different types of communications you might need:
If you don't already have an incident response plan, then creating one can be a daunting exercise to embark on. Three key things to keep in mind are:
Did your blood pressure rise a little reading this? Can't remember the last time your business reviewed your incident response plan? If you'd like some guidance on best practice when it comes to an I.T. or cyber-security incident response plan, get in touch with our team - they'll have you sorted in no time.