IT Service Continuity Planning

1,626 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,626
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
102
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

IT Service Continuity Planning

  1. 1. Service Continuity Planning Taking IT to the Next Level… September 11, 2007 Infotech Consulting
  2. 2. Statistics Disaster recovery, security, and replacing existing systems are priorities. For 2007 technology-related themes, 61% of our government respondents list significant upgrades of their disaster recovery capabilities as either a priority or a critical priority. Fifty-four percent say that upgrading their organization's security environment is important, and 51% tell us that replacing or upgrading existing application systems are important Forrester , April 2007
  3. 3. Key Consideration <ul><li>There are a number of industry best practice frameworks that exist for organizations to use when addressing IT continuity management including: </li></ul><ul><ul><li>National Institute of Standards (NIST); </li></ul></ul><ul><ul><li>National Fire Protection Association (NFPA); </li></ul></ul><ul><ul><li>Disaster Recovery International (DRI); </li></ul></ul><ul><ul><li>International Standards Organization (ISO). </li></ul></ul><ul><li>Infotech believes that the best framework for organizations to utilize is the Information Technology Infrastructure Library (ITIL) / ISO 20000. This framework allows organizations the most flexibility in the implementation and management of a robust service continuity program. </li></ul>
  4. 4. Drivers for Adopting Standards
  5. 5. ITSCM <ul><li>ITIL defines IT Service Continuity Management (ITSCM) as: </li></ul><ul><ul><li>The goal for ITSCM is to support the overall Business Continuity Management process by ensuring that the required IT technical and services facilities (including computer systems, networks, applications, telecommunications, technical support and service desk) can be recovered within required, and agreed, business timescales. </li></ul></ul><ul><li>In the broadest terms, ITSCM is defined in terms of business processes to be covered and their IT support requirements (e.g. systems, networks, communications, support staff skills, data and documentation, etc.) and risks that need to be addressed. </li></ul>
  6. 6. ITIL Source: Office of Government Commerce Service Support Service Delivery Security Management The Business Perspective ICT Infrastructure Management Planning to Implement Service Management Applications Management The Business The Technology
  7. 7. ITIL Service Delivery * Office of Government Commerce (OGC)
  8. 8. The Complete Service Continuity Lifecycle Phase 2 Requirements and Strategy Implementation Organization and Implementation Planning Implement Stand-by Requirements Develop Recovery Plans Implement Risk Reduction Measures Phase 3 Phase 4 Operational Management Develop Procedures Project Kickoff Initial Testing Review and Audit Testing Change Management Training Education and Awareness Assurance Business Impact Analysis (BIA) Risk Assessment Service Continuity Strategy Phase 1 Initiate
  9. 9. Where do YOU Start ? Requirements and Strategy Business Impact Analysis (BIA) Risk Assessment Service Continuity Strategy Define Your Requirements Define How To Achieve Them
  10. 10. Where do YOU start? <ul><li>A simple analogy: </li></ul><ul><ul><li>If your home was on fire, in what order would you begin to remove the following items from harms way? </li></ul></ul><ul><ul><ul><li>Family Photos; </li></ul></ul></ul><ul><ul><ul><li>Golf Clubs; </li></ul></ul></ul><ul><ul><ul><li>Big Screen TV; </li></ul></ul></ul><ul><ul><ul><li>Lock box with identification and bank information; </li></ul></ul></ul><ul><ul><ul><li>Kids; </li></ul></ul></ul><ul><ul><ul><li>Jewelry; </li></ul></ul></ul><ul><ul><ul><li>Makeup; </li></ul></ul></ul><ul><ul><ul><li>Mr. Squiggles the Hamster; </li></ul></ul></ul><ul><ul><ul><li>The complete box set of the “I Love Lucy” show; </li></ul></ul></ul><ul><ul><ul><li>Significant other. </li></ul></ul></ul>
  11. 11. How do YOU organize this? <ul><li>You walk through your house and create an inventory of your personal items; </li></ul><ul><li>You think through the possible disaster scenarios (e.g. fire, flood, wind damage, security breach, etc.); that could occur and define their likelihood of occurrence (e.g. flood threat is high, located next to a river.); </li></ul><ul><li>You prioritize, rationalize and assign a criticality to your items; </li></ul><ul><li>You think through reasonable solutions based on the criticality and the recovery time requirements of each individual item; </li></ul><ul><li>You identify the elements and the associated costs required to implement these solutions. </li></ul>
  12. 12. What do YOU get? An Actionable Plan
  13. 13. Your County Context <ul><li>Administration files and records; </li></ul><ul><li>Human Resources and Payroll Systems; </li></ul><ul><li>Tax Records; </li></ul><ul><li>Historical Records; </li></ul><ul><li>Court Systems; </li></ul><ul><li>Financial Systems; </li></ul><ul><li>Internet Accessible and Electronic Commerce Systems ; </li></ul><ul><li>Local and Wide Area Networks. </li></ul>
  14. 14. Requirements and Strategy: Business Impact Analysis <ul><li>Business Impact Analysis: </li></ul><ul><ul><li>This is a key driver for identifying how much the organization stands to lose as a result of a disaster or other service disruption. The BIA identifies: </li></ul></ul><ul><ul><ul><li>Critical Business Processes and the levels of integration between them; </li></ul></ul></ul><ul><ul><ul><li>The form that the damage or loss may take including lost income, additional costs, damaged reputation, etc.; </li></ul></ul></ul><ul><ul><ul><li>The degree of damage or loss as time progresses; </li></ul></ul></ul><ul><ul><ul><li>Staffing, skills, facilities and services required to enable critical and essential business processes to continue; </li></ul></ul></ul><ul><ul><ul><li>The time within which minimum and maximum levels of services should be recovered; </li></ul></ul></ul><ul><ul><ul><li>The time within which all required business processes should be fully recovered. </li></ul></ul></ul><ul><ul><li>These inputs allow for a mapping of critical service, application and infrastructure components to critical business processes. </li></ul></ul>
  15. 15. Requirements and Strategy: Risk Assessment <ul><li>Risk Assessment </li></ul><ul><ul><li>Understanding the likelihood that a disaster or other service disruption will actually occur. The Risk Assessment identifies: </li></ul></ul><ul><ul><ul><li>Risks to particular services or processes; </li></ul></ul></ul><ul><ul><ul><li>Threat and vulnerability levels (e.g. motivation, available resources, single points of failure); </li></ul></ul></ul><ul><ul><ul><li>Levels of risk; </li></ul></ul></ul><ul><ul><ul><li>Initial risk reduction measures. </li></ul></ul></ul><ul><ul><li>Failure to assess all relevant risks leaves the organization open to possible disruptions; </li></ul></ul><ul><ul><li>These inputs allow for a foundational understanding of risks and potential risk reduction measures across the entire infrastructure. </li></ul></ul>
  16. 16. Requirements and Strategy: Service Continuity Strategy <ul><li>Service Continuity Strategy </li></ul><ul><ul><li>Defining the appropriate risk reduction measures and continuity of operations plan: </li></ul></ul><ul><ul><ul><li>Address availability management options including the elimination of single points of failure; </li></ul></ul></ul><ul><ul><ul><li>Considerations around outsourcing services to more than one provider; </li></ul></ul></ul><ul><ul><ul><li>Greater security controls; </li></ul></ul></ul><ul><ul><ul><li>Appropriate backup and recovery tools and methodologies; </li></ul></ul></ul><ul><ul><ul><li>Procedural improvements. </li></ul></ul></ul><ul><ul><li>Further defined recovery options: </li></ul></ul><ul><ul><ul><li>Do nothing; </li></ul></ul></ul><ul><ul><ul><li>Manual work-arounds; </li></ul></ul></ul><ul><ul><ul><li>Reciprocal agreements; </li></ul></ul></ul><ul><ul><ul><li>Gradual recovery; </li></ul></ul></ul><ul><ul><ul><li>Intermediate recovery; </li></ul></ul></ul><ul><ul><ul><li>Immediate recovery. </li></ul></ul></ul><ul><ul><li>The plan provides for a balance between the cost of risk reduction measures and recovery options. </li></ul></ul>
  17. 17. Tools <ul><li>Business Impact Analysis Document </li></ul><ul><ul><li>Documents the mission critical processes that are supported by the current Information Systems, the level of disruption experienced in the event of a disaster and the overall recovery time requirements. These elements assist in defining the appropriate strategies for system recovery and resumption purposes. In addition, this document will identify the threats, risks and likelihood of a serious disruption to services. </li></ul></ul><ul><li>Risk Model </li></ul><ul><ul><li>This model provides the organization with a graphical representation of the identified threats and vulnerabilities including the likelihood of occurrence. This assists in obtaining “buy in” from the organization in terms of setting priority and criticality to affected systems as well as the priority of remediation activities. </li></ul></ul><ul><li>Service Continuity Plan </li></ul><ul><ul><li>The Service Continuity Plan defines the most appropriate methods of service recovery options and risk reduction measures. In addition, cost estimates, levels of efforts, and defined roles and responsibilities to execute are defined to implement the appropriate solutions. </li></ul></ul><ul><li>Service Continuity Kick Start Templates </li></ul><ul><ul><li>Business Impact Analysis approach for future assessments; </li></ul></ul><ul><ul><li>Systems documentation template; </li></ul></ul><ul><ul><li>Crash kit contents; </li></ul></ul><ul><ul><li>Communication Plans (notification procedures); </li></ul></ul><ul><ul><li>Roles and responsibilities template; </li></ul></ul><ul><ul><li>Risk Analysis approach. </li></ul></ul>
  18. 18. Key Activities Business Impact Analysis (BIA) Risk Assessment Service Continuity Strategy <ul><li>High Level overall ITIL and ISO 17799 assessments; </li></ul><ul><li>Execute Systems Inventory; </li></ul><ul><li>Interviews with Key IT Personnel; Application Owners and Business Administrators; </li></ul><ul><li>Data classification; </li></ul><ul><li>Document findings, requirements. </li></ul>Project Kick Off <ul><li>Review project scope, work plan and charter; </li></ul><ul><li>Identify key personnel, roles and responsibilities. </li></ul><ul><li>Develop Risk Model; </li></ul><ul><li>Facilitated risk review meeting with Organization Stakeholders; </li></ul><ul><li>Develop preliminary list of risk reduction measures. </li></ul><ul><li>Develop risk reduction and recovery options for appropriate systems or IT processes; </li></ul><ul><li>Review strategy with Organization Stakeholders; </li></ul><ul><li>Review appropriate “Kick Start” templates with Organization IT personnel. </li></ul>
  19. 19. Sample Tools Outage Impacts and Allowable Outage Times Recovery Priority Business Impact Analysis Components
  20. 20. Sample Tools Impact Time 1 day 2 days 1 week 2 days 1 Month Very High High Medium Low Very Low Email Impact by length of disruption Graph Vulnerability Threat High Medium Low High Medium Low Risk Measurement Table Risk weighting and prioritization based on threats and likelihood of occurrence Business Impact Analysis Components ERP Line of Business Web Site Custom SQL e Commerce
  21. 21. Sample Tools Business Impact Analysis Components
  22. 22. Sample Tools Service Continuity Strategy Components
  23. 23. Typical Supporting Materials and Tools <ul><li>The following documentation and / or materials are being requested in advance to the start of the engagement: </li></ul><ul><ul><li>Organizational roles and responsibilities; </li></ul></ul><ul><ul><li>Risk management plans; </li></ul></ul><ul><ul><li>Policies, procedures, standards, and guidelines; </li></ul></ul><ul><ul><li>General network and system documentation; </li></ul></ul><ul><ul><li>System inventories by network segment including criticality; </li></ul></ul><ul><ul><li>Prior security assessment findings; </li></ul></ul><ul><ul><li>Disaster recovery invocation procedures (with decision tree); </li></ul></ul><ul><ul><li>Application inventory with criticality; </li></ul></ul><ul><ul><li>Backup and Recovery plans per application or service; </li></ul></ul><ul><ul><li>Recovery testing procedures and most recent testing results; </li></ul></ul><ul><ul><li>Crash kit contents. </li></ul></ul>
  24. 24. <ul><li>Questions????? </li></ul>
  25. 25. Contact <ul><li>Harry Druck </li></ul><ul><li>Solutions Development </li></ul><ul><li>(717) 877 – 6957 </li></ul><ul><li>[email_address] </li></ul><ul><li>Merritt Neale </li></ul><ul><li>Director, Security and Infrastructure Practice </li></ul><ul><li>(717) 319 – 9345 </li></ul><ul><li>[email_address] </li></ul>

×