[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-351224-105":53,"doc-detail-351224-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","cp-001-business-continuity-planning-version-2-effective-date-03132018","CP-001-Business-Continuity-Planning - Version 2 - Effective Date 03/13/2018","","Establishes requirements for developing formal, documented contingency plans for UTHSC IT resources to maintain and resume normal business operations after emergencies, disasters, or extraordinary disruptions. Defines scope and key concepts including Business Impact Analysis (BIA), critical functions, and critical systems using data classification, legal/statutory contingency requirements, and Recovery Time Objective (RTO). Assigns responsibilities between the Office of Cybersecurity and data/system custodians and owners, and specifies standard plan elements such as activation authority, contacts, asset identification, backup/restore, testing, training, and mission-critical system history.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":41,"@type":70,"position":76},"https://docshare.wps.com/template/letters/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/cp-001-business-continuity-planning-version-2-effective-date-03132018/351224/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/cp-001-business-continuity-planning-version-2-effective-date-03132018/351224.png","ImageObject",442,249,{"name":88,"@type":89},"\tJames","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-17","2026-09-22",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",7,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What is the purpose of CP-001 Business Continuity Planning?","Question",{"text":109,"@type":110},"It defines requirements for creating formal contingency plans so UTHSC departments can rapidly restore critical functions after an emergency, disaster, or extraordinary disruption.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"What systems are in scope for this contingency planning requirement?",{"text":114,"@type":110},"All UTHSC IT resources deemed necessary for recovering essential or dependent business functions, including critical systems identified through data classification, statutory contingency plan requirements, or RTO targets.",{"name":116,"@type":107,"acceptedAnswer":117},"Which standard plan elements must be included in the contingency plan?",{"text":118,"@type":110},"The plan must address business continuity, emergency mode operation, and recovery, and include items such as activation authority, points of contact, asset and risk identification, backup and offsite storage, restoration procedures, testing and training records, and mission-critical system history.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},351224,1791233550,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":40,"category_name":41,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":101,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":76},2336474466412,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","| Responsible Office: Office of Cybersecurity | Last Review: 04/20/2021\u003Cbr>Next Review: 04/20/2023 |\n| --- | --- |\n| Contact: Chris Madeksho | Phone: 901.448.1579\u003Cbr>Email: [mmadeksh@uthsc.edu](mmadeksh@uthsc.edu) |\n\nPurpose  \nTo establish requirements for the development of formal documented contingency plans for UTHSC IT Resources to maintain and resume normal business operation, recovering from an emergency, disaster, or other extraordinary disruption. The overall goal is to ensure that all departments and business units of the University are prepared to rapidly restore critical functions in the aftermath of any emergency or disaster.  \nScope  \nAll UTHSC IT Resources deemed necessary (critical system) to recover essential business functions or dependent business functions.  \nDefinitions  \nBusiness Impact Analysis (BIA): An analysis of an information system’s requirements, functions, and interdependencies used to characterize system contingency requirements and priorities in the event of a significant disruption. Critical functions: functions required to enable, support, and implement the safekeeping of our students, staff, and visitors and facilitate the resumption of academic, research, and administrative programs.  \nCritical systems: an UTHSC IT Resource having attributes including, but not limited to:  \na. Any system containing the authoritative copy of UTHSC data or information with a classification rating of 3 in any area using the guidelines set forth in GP- 002-Data & System Classification.  \nb. Any system requiring contingency plans as prescribed by Federal or State statutes or regulations.  \nc. Any system identified as having a Recovery Time Objective (RTO) or less than  \n24 hours.  \nd. Deemed critical by the Business Impact Analysis (BIA) .  \n\n| |  |\n| --- | --- |\n| UT Health Science Center:\u003Cbr>CP-001-Business Continuity Planning |  |\n| Version 2 | Effective Date: 03/13/2018 |\n\nData owner: The person who is ultimately responsible for the data and information being collected and maintained by his or her department or division.  \nDisaster: Any IT incident which is determined to have potential impacts on the business continuity and ongoing operations of Southern Oregon University.  \n• Major Disaster: A major disaster will normally have extensive damage to system hardware, software, networks, and/or operating environment.  \n• Minor Disaster: A minor disaster will be characterized by an expected downtime of well below the RTO determined in the business impact analysis, and minor damage to hardware, software, and/or operating environment.  \nRecovery Time Objective (RTO): The overall length of time an information system’s components can be in the recovery phase before negatively impacting the organization’s mission or mission/business processes.  \nSystem owner: Person or organization having responsibility for the development, procurement, integration, modification, operation, and maintenance, and/or final disposition of an information system  \nUTHSC Information Technology (IT) Resource: Any data, device, or other component of the information environment that supports information-related activities. Assets generally include hardware (e.g. servers and switches), software (e.g. mission critical applications and support systems) and information.  \nResponsibilities  \nOffice of Cybersecurity is responsible for:  \n• Developing a contingency plan template that guides data and system custodians and owners through all required elements.  \n• Ensuring all contingency planning requirements and activities are in compliance with UTHSC policies; local, state and federal laws and guidelines.  \n• Advising the Data or System Custodian and the Data or System Owner with regard to the technical aspects of these duties.  \nData and System Custodian in close collaboration with the Data and System Owner is responsible for:  \n• Developing the contingency plan containing all required elements for the UTHSC IT Resource within scope.  \n\n| |  |\n| --- ","cbCaiqgRs53wZpwf","https://ap.wps.com/l/cbCaiqgRs53wZpwf","pdf",205581,"English","# Purpose\n# Scope\n# Definitions\n# Responsibilities\n# Standard Requirements\n## Contingency plan elements","[{\"question\":\"What is the purpose of CP-001 Business Continuity Planning?\",\"answer\":\"It defines requirements for creating formal contingency plans so UTHSC departments can rapidly restore critical functions after an emergency, disaster, or extraordinary disruption.\"},{\"question\":\"What systems are in scope for this contingency planning requirement?\",\"answer\":\"All UTHSC IT resources deemed necessary for recovering essential or dependent business functions, including critical systems identified through data classification, statutory contingency plan requirements, or RTO targets.\"},{\"question\":\"Which standard plan elements must be included in the contingency plan?\",\"answer\":\"The plan must address business continuity, emergency mode operation, and recovery, and include items such as activation authority, points of contact, asset and risk identification, backup and offsite storage, restoration procedures, testing and training records, and mission-critical system history.\"}]","CP-001-Business-Continuity-Planning - Version 2 - Effective Date 03/13/2018 | PDF",1790093110]