5 Steps of the Incident Management Lifecycle | RSI Security (2022)

5 Steps of the Incident Management Lifecycle | RSI Security (1)

The IT Infrastructure Library (ITIL) developed and released a series of agile incident management processes in the ITIL version 4. This most recent version discusses the 5 steps you should be following throughout an incident management lifecycle:

  1. Incident identification
  2. Incident logging
  3. Incident categorization
  4. Incident prioritization
  5. Incident response

Overall, incident management is the process of addressing IT service disruptions and restoring the services according to established service level agreements (SLAs). What starts with a user reporting an issue should ideally end with the service desk fixing the issue as fast as possible.

Here’s what you need to know about the incident lifecycle.

Step 1—Incident Identification

The initial step for any incident management lifecycle is identification.

This starts with an end user, IT specialist, or automated monitoring system reporting an interruption. The alert can come via in-person notification, automated system notice, email, SMS, or phone call.

(Video) The Six Phases of Incident Response

When an incident is reported, the help desk must document the incident and identify whether or not it’s an incident or service request, which are two distinctly different concerns:

  • Incident – According to ITIL 4 an incident is “An unplanned interruption to an IT service or reduction in the quality of an IT service. Failure of a configuration item that has not yet affected service is also an incident – for example, failure of one disk from a mirror set.”

Most incidents are break or fix issues. Examples include:

    • A computer or personal device won’t start up
    • Hardware is not functioning
    • Software needs to be installed or updated
    • Error message when trying to launch an application

Service request – According to ITIL 4, a service request is, “A formal request from a user for something to be provided – for example, a request for information or advice; to reset a password; or to install a workstation for a new user. Service requests are managed by the request fulfilment process, usually in conjunction with the service desk. Service requests may be linked to a request for change as part of fulfilling the request.”

Since these formal requests can be scheduled and follow predefined processes, they’re not nearly as urgent as an incident. Examples include:

    • Creating an account for a new employee/user
    • Requesting upgraded hardware
    • Needing to change a password

It’s best if an incident can be identified early on through automatic monitoring. When that happens, the problem can be resolved before it has an impact on users. However, there will inevitably be times when the service desk is only made aware of the incident by the impacted user.

Once the incident has been identified, the service team can move to the next step in the incident lifecycle ITIL.

Assess your Incident Management plan

(Video) The 6 Steps of the Incident Response Life Cycle and What Is a Security Incident?

Step 2—Incident Logging

After the team has been notified about the incident, it’s crucial that they record and document it.

Thorough reporting helps your organization notice incident trends that may morph into larger problems. It also gives your team better visibility over their workflow, allowing them to delegate their resources where they’re needed most.

Every incident must be reported – big and small – and logged as a ticket. Tickets need to contain the following information:

  • User name
  • User contact information
  • Date and time of the report
  • Description of the incident

When it comes to incident logging, the more details you can include, the better.

Rigorous data collection empowers your service team to find patterns and seek out the root causes for incidents that crop up repeatedly. Armed with this information, the team can either templatize responses for common issues or use automated programs to help streamline resolution processes.

Step 3—Incident Categorization

Incident categorization requires the service team to assign a category and at least one sub category to any incident.

This is done for three critical reasons:

(Video) [Webinar] Beyond Incident Response: Benefits of Full-Lifecycle Incident Management | D3 Security

  1. It helps the service desk sort and model incidents according to their categories and subcategories.
  2. It makes it possible to automatically prioritize some of the issues.
  3. Provides accurate incident tracking.

By assigning appropriate categories, it becomes easier for the help desk to assign, escalate, and then monitor incident trends and frequencies. When done correctly, it streamlines incident logging, prevents redundancy, and quickens the entire resolution process.

Categorization utilizes a hierarchical structure with multiple levels of classification—usually with three to four levels of granularity. But since all organizations are unique, classification must be conducted internally, especially at lower levels. If you need help with yours, HCI recommends taking the following steps:

  • Hold a brainstorming session among the relevant support groups
  • Use this session to decide the ‘best guess’ top-level categories and include an ‘other’ category. Create relevant logging tools to use these new categories.
  • Conduct a trial period that allows several hundreds incidents to fill up each category.
  • Perform an analysis of incidents. The number of incidents logged per category will inform you as to whether or not they’re worth having.
  • Breakdown each incident within higher-level categories to decide if lower-level categories are necessary.
  • Review the results and repeat the activities for a few more months to ensure that your results are accurate and repeatable.

By categorizing incidents you can extrapolate on which trends require training or problem management.

Step 4—Incident Prioritization

After incidents have been assigned their proper category, the next important task is to prioritize them according to urgency and impact on the users and the business. Urgency is how quickly a resolution needs to happen, whereas impact is the potential damage an incident could cause.

Incidents are typically designated one of three priority statuses:

  1. Low-priority incidents – Do not interrupt users or the business and can generally be worked around. Service to customers and users continues.
  2. Medium-priority incidents – Impact some employees and can moderately disrupt work. Customers may be slightly inconvenienced by the incident.
  3. High-priority incidents – Affect a significant number of users or customers, interrupt the business, and have a noticeable impact on service delivery. Such incidents will almost always cause a financial toll.

Since your help desk’s resources and time is limited, the higher the assigned priority, the quicker the team must respond to the incident. The system ensures that IT teams aren’t focusing on low-level incidents while much larger ones are wreaking havoc on your employees or customers.

5 Steps of the Incident Management Lifecycle | RSI Security (2)

(Video) Incident Response Process - CompTIA Security+ SY0-501 - 5.4

Step 5—Incident Response

After an incident has been identified, logged, categorized, and prioritized, the service desk can get to work on resolution. Incident resolution has sub steps to follow, including:

  • Initial diagnosis – User details the problem and undergoes troubleshooting with the service agent.
  • Incident escalation – If the incident requires advanced support, it can be forwarded to certified support staff or on-site technicians. Most incidents should be able to be resolved by the initial service agent.
  • Investigation and diagnosis – Once the initial incident hypothesis is confirmed, staff can then apply a solution or workaround.
  • Resolution and recovery – The service desk confirms that the user’s service has been restored to agreed upon SLA level.
  • Incident closure – The incident is closed and no further work is required.

RSI Security: Incident Management Lifecycle Experts

From initial reporting to final resolution the incident management lifecycle entails 5 critical steps:

  1. Incident identification
  2. Incident logging
  3. Incident categorization
  4. Incident prioritization
  5. Incident response

At their best IT incidents can be a minor annoyance. But at their worst they can jeopardize your entire business. Should an incident occur, you’ll require an expert partner to guide you through the expanded incident lifecycle.

RSI Security can be your incident management partner through every step of the journey. We’ll work alongside you to ensure that all incident management program best practices are being applied and followed from day one.

Ready to get started? So are we.

Speak with an Incident Management expert today – Schedule a Free Consultation

5 Steps of the Incident Management Lifecycle | RSI Security (3)

(Video) Incident Response Process, Lifecycle & Methodology | NIST SANS | Cybersecurity SOC

RSI Security

RSI Security is the nation’s premier cybersecurity and compliance provider dedicated to helping organizations achieve risk-management success. We work with some of the world’s leading companies, institution and governments to ensure the safety of their information and their compliance with applicable regulation. We also are a security and compliance software ISV and stay at the forefront of innovative tools to save assessment time, increase compliance and provide additional safeguard assurance. With a unique blend of software based automation and managed services, RSI Security can assist all sizes of organizations in managing IT governance, risk management and compliance efforts (GRC).RSI Security is an Approved Scanning Vendor (ASV) and Qualified Security Assessor (QSA).

FAQs

What are the 5 stages of incident life cycle? ›

The NIST incident response lifecycle breaks incident response down into four main phases: Preparation; Detection and Analysis; Containment, Eradication, and Recovery; and Post-Event Activity.

What are the five stages of incident handling? ›

The incident response phases are:
  • Preparation.
  • Identification.
  • Containment.
  • Eradication.
  • Recovery.
  • Lessons Learned.

What are the 5 steps of the NIST framework for incident response? ›

The NIST incident response process is a cyclical activity featuring ongoing learning and advancements to discover how to best protect the organization. It includes four main stages: preparation, detection/analysis, containment/eradication, and recovery.

What are the 6 stages in the incident management life cycle? ›

Incident response is typically broken down into six phases; preparation, identification, containment, eradication, recovery and lessons learned.

What is the lifecycle of major incident management? ›

The incident lifecycle (also sometimes known as the incident management process) is the path we take to identify, resolve, understand, and avoid repeating incidents.

What are the 7 steps in incident response? ›

Understanding the Theory Behind Incident Response
  1. Preparation.
  2. Threat Detection.
  3. Containment.
  4. Investigation.
  5. Eradication.
  6. Recovery.
  7. Follow-Up.
Mar 29, 2022

What is an incident management process? ›

Incident management is the process of responding to an unplanned event or service interruption to restore the service to its operational state.

What is Incident Management in ITIL? ›

ITIL incident management (IM) is the practice of restoring services as quickly as possible after an incident. And it's a main component of ITIL service support. ITIL incident management is a reactive process. You can use IM to diagnose and escalate procedures to restore service. So, it's not a proactive measure.

What are the 5 steps of incident response in the ISO IEC 27035 1 2016 international standard? ›

ISO/IEC 27035-1:2016 outlines the principles underlying information security incident management, which is broken into five areas:
  • Planning and preparation. Establish an information security incident management policy. ...
  • Detection and reporting. ...
  • Assessment and decision. ...
  • Response to incidents. ...
  • Lessons learned.

What are the 5 pillars of NIST? ›

The five domains in the NIST framework are the pillars support the creation of a holistic and successful cybersecurity plan. They include identify, protect, detect, respond, and recover.

What is a security incident NIST? ›

A violation or imminent threat of violation of computer security policies, acceptable use policies, or standard security practices. Source(s): NIST SP 800-61 Rev. 2 under Incident. See incident.

What is a security incident response plan? ›

Share to Facebook Share to Twitter. Definition(s): The documentation of a predetermined set of instructions or procedures to detect, respond to, and limit consequences of a malicious cyber attacks against an organization's information systems(s).

What is incident life cycle? ›

From initial reporting to final resolution the incident management lifecycle entails 5 critical steps: Incident identification. Incident logging. Incident categorization. Incident prioritization.

What is incident lifecycle in ITIL? ›

ITIL's incident management lifecycle includes a set of instructions that encourages IT professionals to work together to ensure effective IT service delivery.

What are the 4 main stages of a major incident? ›

Most major incidents can be considered to have four stages: • the initial response; the consolidation phase; • the recovery phase; and • the restoration of normality.

What is incident lifecycle in ITIL? ›

ITIL's incident management lifecycle includes a set of instructions that encourages IT professionals to work together to ensure effective IT service delivery.

How many phases are in the ITIL life cycle? ›

The 5 stages of ITIL.

What are the six phases of the incident response life cycle quizlet? ›

What are the six phases of the incident response life cycle? Preparation, Identification, Containment, Eradication, Recovery, and Lessons Learned.

Videos

1. Major Security Incident Management Demonstration
(ServiceNow - Now Community)
2. SOC 101: Real-time Incident Response Walkthrough
(Exabeam)
3. [Webinar] SOAR Like An Eagle: The Key to Fast, Full-Lifecycle Incident Response | D3 Security
(D3 Security)
4. The 5 Stages of the ITIL Service Lifecycle
(QuickStart)
5. The Five Stages of Vulnerability Management
(Ascend Technologies)
6. How To - Security Incident Response
(ServiceNow - Now Community)

Top Articles

You might also like

Latest Posts

Article information

Author: Allyn Kozey

Last Updated: 12/10/2022

Views: 5271

Rating: 4.2 / 5 (63 voted)

Reviews: 86% of readers found this page helpful

Author information

Name: Allyn Kozey

Birthday: 1993-12-21

Address: Suite 454 40343 Larson Union, Port Melia, TX 16164

Phone: +2456904400762

Job: Investor Administrator

Hobby: Sketching, Puzzles, Pet, Mountaineering, Skydiving, Dowsing, Sports

Introduction: My name is Allyn Kozey, I am a outstanding, colorful, adventurous, encouraging, zealous, tender, helpful person who loves writing and wants to share my knowledge and understanding with you.