The goal of any incident management process is to return the business to operational normalcy, repair any damage and follow communication protocols internally and externally.
Incident management refers to the process an organization uses to discover, assess, address, report and document incidents. The nature of incidents can vary but in call cases, they involve the potential damage or disruption of an organization's critical assets and/or operations. Without rapid mitigation, incidents can escalate to become disastrous. The goal of any incident management process is to return the business to operational normalcy, repair any damage and follow communication protocols internally and externally.
While often correlated with IT/ITIL, incident management and incident response are needed across an entire organization. Some examples of incidents requiring a coordinated, consistent, and rapid response:
In all cases, there is an event trigger followed by a well-executed, cross-departmental process that is handled by a formal or informal Incident Response Team. Each team member is responsible for a specific aspect of the incident mitigation activities as well as knowing how and when to escalate to another team or team member.
At the end of the process, there is a response assessment that reviews what happened, response performance and results. By recording and documenting each incident, the process can be improved and lessons can be learned for future incident management situations.
Everyone has been part of a "fire drill" approach to handling an incident. In some cases individuals step up and guide the response, acting as a traffic cop and doing their best to both communicate and manage activities. However, even in the best situation with the best traffic cops, the response tends to be slower and less effective than it should be. In some cases, these delays and missteps can cost an organization greatly both in terms of revenue and reputation.
Automating the process as much as possible can:
Having a centralized incident reporting system accessible to consistently log incidents and route them to trained personnel for the initial assessment is the first step. This alone could help ensure a rapid, more coordinated response to security incidents by providing checklists for actions to be performed and communicating status.
Once incidents are reported they can be prioritized based on reported or determined severity. While all incidents are logged and analyzed, “Critical” incidents might be routed immediately to the highest level remediation team and key executives. In addition, an alert might be sent back to the originator for immediate clarification and additional information. If a “Critical” incident has not had action taken on it within 5 minutes it could escalate to another team, fire off more alerts, etc.
Our customers have built incident management systems to handle a variety of incident response needs using our low-code workflow automation platform. The example below is from a Privacy Incident system that one of our customers developed to handle potential privacy breaches. Anyone in the organization can submit an incident report and the response workflow is immediately kicked off. Note that we're only showing part of the system here to maintain anonymity. The complexity of the process is well beyond what you see here.
Integrify provides incident management software that allows our customers to build customized, automated response processes based on any type of incident, whether it's a cyberattack, HR issue, or any other kind of incident in need of a coordinated, rapid response. Our software is proven in the field and has been used by some of the largest companies in the world, including GlaxoSmithKline, Sony, AT&T, and BP.
We have a variety of resources to help you on your journey to an automated incident management workflow.
To see how quickly you can begin automating your processes, request a demonstration or trial of Integrify.
Copyright © 2020 Integrify All rights reserved.