4 Ps of the Incident Management Framework

Plans should not be the only goal of Business Continuity Management (BCM) programs.  The true end-state of BCM should be to assure that your organization can successfully manage its response to any disruption, the goal of Incident Management.

An Incident Management focus has 4 components:

Planning – More than just BIAs and Risk Assessment, planning is the process of gathering, analysis and presentation of data crucial to Incident Managers’ and senior executives’ Decision Support.  These include: assessment of current capabilities, vulnerabilities, gaps, single points of failure, process and IT services critical resources, RTO’s and RPO requirements.

Plan Development – Plans must be developed to meet objectives and foster collaboration, not to fill checklists or comply with ‘standards’.  Plans have to be actionable and executable. One of the critical components of actionable plans is its ability to ensure smooth and efficient execution of the strategy to achieve business objectives (industry refers to these plans as ‘playbook’)

Preparedness – Plans are necessary, but alone they do not inspire senior executives’ confidence in your organization’s ability to respond effectively to an incident.  They will gain confidence if Plans are exercised frequently, tested in different scenarios, they consistently meet recovery objectives and that there is quantifiable continuous improvement.

Program Management: Streamlining and automation of repetitive tasks allows more time for better execution of the other 3 Ps. Automate all repetitive tasks such as data refresh and plan review notification. Schedule tasks such as Exercises & tests, user training, program metrics vs KPI, users access management, audit & compliance reporting, Provide decision support for management via interactive Dashboards

The following series of blogs explores the goals, components and values of each of the 4 Ps in detail.

SHARE:
Ramesh Warrier

Ramesh Warrier

eBRP Founder and Chief Designer of eBRP Suite, Ramesh is a proponent of constant change, a visionary who believes that the practice of Business Continuity can deliver improved operational efficiency. Ramesh, B.Tech in Electrical Engineering, has nearly 30 years experience in Business & Technology roles. His thoughts are expressed in blogs, white-papers, frequent webcasts and speaking engagements at industry conferences.

Related Posts

Enterprise Resiliency: Navigating Through Disruptions

Enterprise Resiliency: Navigating T...

In today’s threat landscape, the ability of an organization to…
Orchestrating BC/DR Testing: Virtual – Emergency Operations Centers

Orchestrating BC/DR Testing: Virtua...

  Enhancing Planning and Logistics Management  Coordinating BC/DR tests involves…
Insights into creating a successful Disaster Recovery Test – Part 2: Preparation

Insights into creating a successful...

Insights into creating a successful Disaster Recovery exercise – Part 1: Objectives

Insights into creating a successful...

Aligning Cyber Incident Response Planning with Your BC/DR Program

Aligning Cyber Incident Response Pl...

Cyber disruptions – and their impact on both reputations and…
What Can You Do when your BCM software Relationship Falls Apart

What Can You Do when your BCM softw...

“This isn’t working.”  “I’ve changed.”  “I don’t see a future…
Aligning BC/DR to CSIRP Challenges

Aligning BC/DR to CSIRP Challenges

The immediate reaction to a cyber-security incident is the FUD…
Technology Modeling – the eBRP Way

Technology Modeling - the eBRP Way

Definition: Technology modeling is a point-in-time snapshot of an Enterprise’s…
eBIA – The eBRP Way

eBIA - The eBRP Way

Definition: A Business Impact Analysis (BIA) is the cornerstone of…
Threats, Impacts, BCPs

Threats, Impacts, BCPs

Within Business Continuity circles there is ongoing debate about the…