Agenda. Creating a Robust Testing Program. Notification Tests. Overview of Testing. Beverly Schulz, CBCP

Transcription

1 Agenda Overview of Testing Notification Tests Tabletop or Walk-through Tests Simulations Technology Outage Tests Third Party Outage Tests Workplace Outage Tests Workforce Outage Tests Reporting Creating a Robust Testing Program Beverly Schulz, CBCP Notification Tests Preparation, Execution, and Follow-up: Alert team to upcoming exercise* Develop script for notification calls*; set up in automated notification tool Conduct exercise and record Follow up on any incorrect contact information Set goals / objectives (i.e. 75% respond within a certain number of hours) and increase those over time Include just area recovery team contacts, or expand to cover all employees in the area Group by geography, contacting all employees in a city/state/region Group by area to allow ease in reporting Decrease the time allowed for response if multiple modalities are used % of participants responding Overview of Testing Purpose of Testing is to: Answer the question: Can the recover? Reinforce training of recovery team members Test the performance of the recovered systems, people, etc. Expose issues which may prevent recovery Get participants excited about fixing issues Demonstrate improvement year after year Test Types: Notification - A test of the phone numbers within a continuity plan Tabletop or Walk-through Exercises - A test of the continuity plan where participants discuss their response to a simulated disaster scenario Simulation Exercises - A test of IT,, and/or vendor recovery strategies, where participants perform recovery activities * - see Appendix

2 Simulation Tests Types of Simulation Tests: Loss of technology or telephony Loss of critical vendor Loss of workplace Loss of workforce or key resource Test the workplace unavailable scenario for all areas within a building at the same time Ensure the duration allows problems to surface Test a variety of scenarios, not just workplace outage Measure success based on the percentage of functions or applications recovered within their Recovery Time Objective Tabletop Tests Preparation, Execution, and Follow-up: Read the plan! Write a scenario that will test weaknesses within the plan Use scenario injects (i.e. monkey wrenches)* Include multiple, inter-dependent groups with differing RTOs Conduct executive level exercises Conduct surprise exercises Measure success based on percentage of answers known Measure success based on improvement opportunities identified * - see Appendix Disaster Recovery Tests, continued Business function / process validation Customer Purchase #1 #3 #2 #4 #5 Customer Statement Simulation Loss of Technology a.k.a. Disaster Recovery Tests Business function / process validation performance statistics Crisis Management involvement Third Party participation Measurements of success Schedule notification and tabletop exercises right before the Disaster Recovery exercise Conduct tests for each major data center Gradually increase scope so that more than most critical applications tested

3 Disaster Recovery Tests, continued Setting Success Rate Targets Use exercise sponsor or BC Committee to set target success rates Revisit targets on a regular basis (raise the bar) Example Measurements of Success for IT % of s meeting Recovery Time Objectives % of s recovered before end of exercise (even if late) % of s meeting Recovery Point Objectives Measurements of Success for the Business % of Functions meeting Recovery Time Objectives Impact Rating* - Allow to rate their own success using a pre-defined impact scale Disaster Recovery Tests, continued Volume/ Utilization Metric performance statistics (T) Production (T) Test Comparison No impact to better than expected Low impact to Moderate impact to High impact to Very high impact to * - see Appendix Simulation Loss of Workplace Allow real events to count as test credit Scope should align to plans, i.e. if plans are built by building, then tests should be by building Measure success based on the percentage of the area s people testing the strategy Measure success based on the percentage of the functions recovered within Recovery Time Objectives Simulation Loss of Third Party Test the ability of the to respond to the loss of the third party, OR test the third party s ability to recover from their own disaster, OR both! Start with a simple ping test or a tabletop test Expand over time involve login to vendor systems during their DR tests, file exchanges, etc. Measure success based on the percentage of Third Party applications meeting Recovery Time and Recovery Point objectives Measure success based on the percentage of Third Party functions meeting Recovery Time Objective Give extra credit for participation in third party s test

4 Reporting Identify issues resulting from test, assignments for resolutions, and target completion dates Include the following within the post test report: Scenario summary Objectives Results Lessons learned and recommendations for future tests Issues tracking and summary Simulation Loss of Workforce Allow real events to count as test credit Ensure the scope of the test allows problems to surface (ex. require a minimum of 25% workforce loss) Measure success based on the percentage of the area s people testing the strategy Measure success based on the percentage of the functions recovered within Recovery Time Objectives Develop a process to track actions to confirm closure Include of testing in Business Continuity metrics Questions? Reporting, cont d Consider developing metrics for Executive Management to show their ability to recover, based on testing : BC Issues from Testing and Events All issues documented appropriately including level of risk and actively remediated and updated Reflects mixed between 1 and a 3 Issues not registered or not being actively remediated Reflects mixed between 3 and a 5 Issues not registered and not being actively remediated Notification Testing % response rate 94-85% response rate 84-75% response rate 74-50% response rate <50% response rate Workforce Strategy Testing 100% of Mission Critical plans and >75% of remaining plans scored 2 or % of plans scored 2 or % of plans scored 2 or 1 or insufficient testing has occurred (i.e. risk is unknown) 50-25% of plans scored 2 or 1 <25% of plans scored 2 or 1 Workplace Strategy Testing 100% of Mission Critical plans and >75% of remaining plans scored 2 or % of plans scored 2 or % of plans scored 2 or 1 or insufficient testing has occurred (i.e. risk is unknown) 50-25% of plans scored 2 or 1 <25% of plans scored 2 or 1 Third Party Strategy Testing 100% of Mission Critical Third Parties met recovery time and recovery point and >75% of remaining third parties met recovery time and recovery point 99-75% of Third Parties met recovery time and recovery point 74-51% of plans scored 2 or higher or insufficient testing has occurred (i.e. risk is unknown) 50-25% of Third Parties met recovery time and recovery point <25% of Third Parties met recovery time and recovery point Disaster Recovery Testing 100% of plans with needs 99-90% of plans with met by app DR exercise needs met by app DR exercise 89-80% of plans with 79-70% of plans with needs met by app DR exercise needs met by app DR exercise <69% of plans with needs met by app DR exercise

5 Appendix 1 Notification Alert Sample text to use when alerting a group about an upcoming notification exercise: Subject: Notification Exercise Required Annually Per Business Continuity Standards, we are required to perform a Notification Exercise annually. This is performed without advance notice to test the accuracy of contact information, as well as the accessibility of the Recovery Team Members. We will be conducting this exercise before [month/day]. The attached Business Continuity Plan has all of the required information for a successful exercise. During which, you will be contacted via phone and . The automated system will call all phone numbers you have currently listed in the HR system (main, work, work cell, personal cell, home, etc.) in an effort to reach you. Note: when responding to the phone notification, please wait to hear that your response has been accepted before hanging up otherwise your response will not be registered. These contacts will continue several times within a 2 hour timeframe until contact is made and response has been received by the participant. For more information beverly.schulz@capitalone.com Various internet sites: Please let me know if you have any questions or if you would like additional information about the Notification Exercise. Appendix 3 - Tabletop Tests Scenarios and Injects Natural Disasters and Accidents: Main Scenario Inject Earthquake, Roof collapse hurricane, flood, Area roads blocked and local / state travel restrictions are being enforced blizzard, or IT is wondering how many computers you will need and what applications tornado you will need loaded on them. They are also inquiring as to any other equipment (fax, printer, copier, phones) you will need. Please respond. Fire Determined to be arson Mold grows due to water used in fire suppression, causing health issues for half of the employees so far. Which functions can be delayed and which can be transferred? Sink hole or Area roads blocked and local / state travel restrictions are being enforced impassable facility access Plane crash or mass transit accident Multiple executives on board The designated area decision maker was injured. Who is next in command? Appendix 2 Notification Template Sample text to use when conducting a notification exercise: This is the Business Continuity Management team, conducting your annual Notification Exercise in partnership with your [insert name] area. This mandatory exercise is required for all areas per Business Continuity Policy. In order for this exercise to be successful, please acknowledge receipt of this notification by entering 1 on your phone or in the body of the . Thank You.

6 Appendix 4 Impact Rating Samples What was the impact to CUSTOMERS? No impact = we do not work with customers Low Impact = minimal inconvenience to customers Moderate impact = inconvenienced and irate customers High impact = dissatisfied customers, escalating high % of complaints to managers Very high impact = customers are closing accounts at an unacceptable rate What REGULATORY impacts may have been caused? No impact Low impact = minor, isolated compliance issues Moderate impact = Regulators require issue resolution High impact = Regulators publicly warn company Very high impact = Regulators take action against company Appendix 3 - Tabletop Tests, cont d Infrastructure: Main Scenario Generator failure Heating / air conditioning failure Network or telecommunications failure Facility access disruption Inject Fuel supply vendor can t deliver Associates report health issues Determined to be malicious code All doors failed open Natural Disasters and Accidents: Main Scenario Loss of personnel due to illness Third party bankruptcy / hostile takeover Internet or cyber incident Protests block building access Inject Determined to be food poisoning from on-site cafeteria Choose a singlesource vendor Business critical data being released on Internet Time-released cyber attack Police blockade, tear gas, or injury to customer/employee Appendix 4 Impact Rating Samples, cont d What amount of REVENUE* would have been permanently lost due to the missed or failed recovery? None = we do not generate revenue Low = Zero to 50 thousand US dollars Moderate = 50 to 500 thousand US dollars High = 500 thousand to 1 million US dollars Very High = over 5 million US dollars * - Numbers for illustrative purposes only