What you will learn from this tip: What is a business impact analysis, what are the benefits of a BIA and how to...
Conducting a business impact analysis is hard work and takes time. But once this data is collected, security practitioners can confidently request resources, and more importantly, prioritize security efforts across the enterprise.
Simply stated, BIA is an analytic process that aims to reveal business and operational impacts stemming from any number of incidents or events.
A BIA traditionally leads to a report detailing likely incidents and their related business impact in terms of time and dollars. For example, a BIA report for an online retailer may include a Web site outage of one day with the loss calculated as the yearly gross sales divided by number of days per year the site is open for business.
In order to conduct a BIA you need to understand the business operations of your company in detail. You need to roll up your sleeves and reach out to operational folks to get the real picture. I remember one such exercise on a consulting engagement at a large bank where it was assumed that if the tellers lost their computer terminals that the dollar impact per hour was in the millions. The bank tellers later told me that when the terminals aren't available they can continue accepting deposits and other transactions, then manually batch the transactions at the end of the day. There was actually a five- to seven-hour window of no real loss of revenue.
Here is a simple step-by-step approach that will put you on your way to conducting a successful business impact analysis.
- Document the gross revenue and net profit your organization generates per year. This data sets the upper bound for business losses related to business operations. It will not, however, set the limits for reputation, regulatory or legal losses that can rise above yearly revenue.
- Define the critical business systems your organization operates. This data can be entered and tracked in a spreadsheet. In many cases the revenue data can be linked to critical systems. This is especially true in e-commerce-driven companies.
- Classify each system as business critical, important or non-critical. Ask system operators what would happen if a particular system was not available for an hour, a day or a week. In most cases you can quickly classify systems based on operator responses.
- Document which systems have cross dependencies. There may be non-critical systems that act as upstream or downstream components to critical systems. For example, DNS service may not appear to be critical to an online store until it is discovered that the credit card gateway relies on DNS to send credit card requests and process transactions. This type of cross dependency may require a reclassification of systems when linked to critical applications.
- Estimate the financial, revenue and non-revenue impacts associated with each system. For example, a payment gateway server for fax orders that does only 1% of the total revenue of the company can easily be estimated as .01 x gross revenue. If data does not exist or is not easy to estimate, the replacement cost (including labor) can be used for important and non-critical systems. For non-revenue related systems, note impact. For example, if the payroll system is not working, employees may not get paid on time -- which may cause other issues.
- Estimate the cost to identify, remediate, recover and resume operations for each system in the spreadsheet. Include labor, hardware and software costs. For incidents that result in negative reputation, legal and regulatory outcomes, include estimate of fines, legal costs or a marketing campaign to win back customer confidence. Add these costs to impacts defined in step five.
- Identify the Maximum Acceptable Outage (MAO) for each system. This is the time from the detection of the outage to obviation of importance to business. For example, if an online bookseller's website is down for over a week, it may lose all customers to the competition. However, an overnight outage may only result in a few lost orders. Some real-time financial industry systems may have very low MAO values, where more elongated global supply-chain processes with built-in delays may have MAO values that exceed a month.
- Identify and document potential system threats, severity and the probability at which they may occur. For example, a datacenter fire severity would be 1.00 (on a .0–1.0 scale) but the probability may only be .01 (1%) in a given year. Threat statistics are available from a variety of sources and are used by insurance companies to calculate insurance premiums. Create a threat score for each incident type in a different section of the same spreadsheet. In the above example you would multiply (.01 x 1.0 =.01) and yield a combined risk score of .01 or 1%. Do this for all conceivable threats. You will also want to list one generic loss at 100% just to have a line item that reflects a complete loss for each system regardless of the incident or probability. This sets the upper bound for the system valuation.
- Now you have most of the data needed to start the process. It is best to use the simple formula functions that a spreadsheet provides. For every system you have defined with a loss value, multiply the series of values from the threats listed in step eight with the combined loss values from step six to see the relative loss or impact per system. Do this on a line item basis. For each system calculate all possible listed threats. Do not include items that are not physically possible. For example, if you have business systems in Malaysia and New York, don't include the volcano or similar incidents that can't really happen in New York.
- In this last step you will sort the data you have to show the top priority systems both from a business criticality and impact perspective. In the spreadsheet, select all columns in the sheet and use the "auto-filter" function on the data-sorting menu of your spreadsheet to link all the columns relationally. You can now sort on any of the variables in the sheet. Optionally, you can create a scorecard-like report by dressing up the spreadsheet, or add a narrative document and use the spreadsheet as the supporting data source.
Your BIA report can be used to request and prioritize resources, and incident response activity. If done properly, it will be in a format your CFO and finance department can understand and include impact data gathered from these very same people, thus overcoming any objections or pushback on the validity of your report and subsequent resource requests!
About the author
George Wrenn, CISSP, ISSEP, is a technical editor for Information Security magazine and a security director at a financial services firm. He's also a graduate fellow at the Massachusetts Institute of Technology.
Dig Deeper on Information Security Incident Response-Detection and Analysis