[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-171228-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-171228-en":126},{"code":4,"msg":5,"data":6},0,"ok",{"site_id":7,"language":8,"slug":9,"title":10,"keywords":11,"description":12,"schema_data":13,"social_meta":74,"head_meta":76,"extra_data":78,"updated_unix":80},105,"en","information-system-contingency-plan-iscp-nist-sp-800-34-rev1-high-impact-system","Information System Contingency Plan (ISCP) - NIST SP 800-34 Rev.1 High Impact System","","A customizable template for an Information System Contingency Plan (ISCP) for a high-impact information system, aligned to NIST SP 800-53 contingency planning controls. It defines how the plan supports recovery after a service disruption by outlining background, scope, assumptions, and operational concepts. It provides structured guidance for activation and notification, outage assessment, recovery procedures, reconstitution, testing validation, and deactivation. It also includes plan approval language and table-of-contents structure to support testing, maintenance, and version control.",{"@graph":14,"@context":73},[15,34,56],{"@type":16,"itemListElement":17},"BreadcrumbList",[18,23,27,31],{"item":19,"name":20,"@type":21,"position":22},"https://docshare.wps.com","Home","ListItem",1,{"item":24,"name":25,"@type":21,"position":26},"https://docshare.wps.com/template/","Template",2,{"item":28,"name":29,"@type":21,"position":30},"https://docshare.wps.com/template/presentations/","Presentations",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/information-system-contingency-plan-iscp-nist-sp-800-34-rev1-high-impact-system/171228/",4,{"url":32,"name":10,"@type":35,"image":36,"author":41,"headline":10,"publisher":44,"fileFormat":47,"inLanguage":8,"description":12,"dateModified":48,"datePublished":49,"encodingFormat":47,"isAccessibleForFree":50,"interactionStatistic":51},"DigitalDocument",{"url":37,"@type":38,"width":39,"height":40},"https://docshare.wps.com/thumbnails/information-system-contingency-plan-iscp-nist-sp-800-34-rev1-high-impact-system/171228.png","ImageObject",442,249,{"name":42,"@type":43},"Melati","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-10-20","2026-09-01",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",15,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the purpose of the ISCP in a high-impact system?","Question",{"text":63,"@type":64},"The ISCP establishes comprehensive procedures to recover a system quickly and effectively after a service disruption, while supporting continued operations with minimal excessive interruption.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"What phases does the recovery approach include?",{"text":68,"@type":64},"The template organizes recovery into three phases: Activation and Notification, Recovery, and Reconstitution, each with defined objectives and activities.",{"name":70,"@type":61,"acceptedAnswer":71},"How does the template address plan testing and approval?",{"text":72,"@type":64},"It includes plan approval language to confirm completeness and sufficient testing, and it requires that the ISCP is tested at least annually, with testing details referenced in a TT&E results appendix or location.","https://schema.org",{"og:url":32,"og:type":75,"og:title":10,"og:site_name":45,"og:description":12},"article",{"robots":77,"canonical":32},"index,follow",{"doc_id":79,"site_id":7},171228,1791156619,{"code":4,"msg":82,"data":83},"success",[84,88,93,98,102,107,112,117,122],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":86,"slug":87},11,90,"presentations",{"id":89,"doc_module":22,"doc_module_name":25,"category_name":90,"show_sort_weight":91,"slug":92},12,"Resumes",80,"resumes",{"id":94,"doc_module":22,"doc_module_name":25,"category_name":95,"show_sort_weight":96,"slug":97},14,"Invoices",70,"invoices",{"id":55,"doc_module":22,"doc_module_name":25,"category_name":99,"show_sort_weight":100,"slug":101},"Posters",60,"posters",{"id":103,"doc_module":22,"doc_module_name":25,"category_name":104,"show_sort_weight":105,"slug":106},16,"Social Media",50,"social-media",{"id":108,"doc_module":22,"doc_module_name":25,"category_name":109,"show_sort_weight":110,"slug":111},17,"Forms",40,"forms",{"id":113,"doc_module":22,"doc_module_name":25,"category_name":114,"show_sort_weight":115,"slug":116},18,"Letters",30,"letters",{"id":118,"doc_module":22,"doc_module_name":25,"category_name":119,"show_sort_weight":120,"slug":121},21,"Paper Templates",5,"papers-templates",{"id":123,"doc_module":22,"doc_module_name":25,"category_name":124,"show_sort_weight":4,"slug":125},158,"General","general-158",{"code":4,"msg":82,"data":127},{"doc_id":79,"user_id":128,"nickname":42,"user_avatar":129,"doc_module":22,"category_id":85,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":103,"language":135,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":12,"update_tm":139,"read_time":140},962085570644,"https://ap-avatar.wpscdn.com/davatar_994ba38a5ba835b3df7d355c54d3ed8d","NOTE: This sample template is provided to address NIST SP 800-53 security controls from the Contingency Planning family for a high impact information system.  The template provided is a guide and may be customized and adapted as necessary to best fit the system or organizational requirements for contingency planning.\n[System Name]\nSecurity Categorization: High\n[Organization Name]\nInformation System Contingency Plan (ISCP)\nVersion [#]\n[Date]\nPrepared by\n[Organization Name]\n[Street Address]\n[City, State, and Zip Code]\n\u000fTABLE OF CONTENTS\nPlan Approval…………………………………………………….………..….……….……A.3-3\n1. Introduction ………………………………………………….……..……….…….……..A.3-4\n1.1   Background………..………………………………………….………………..A.3-4\n1.2   Scope……..………..…………………………..…….……….……….………..A.3-4\n1.3   Assumptions..…….………………………..….……………….……….……...A.3-4\n2. Concept of Operations ………………………….……..…………………………..……A.3-5\n2.1   System Description………………....……………………………………..…..A.3-5\n2.2   Overview of Three  Phases..………………………………………………….A.3-5\n2.3   Roles and Responsibilities…….…......……………………………………....A.3-6\n3. Activation and Notification………………....………………………..………….……..A.3-6\n3.1   Activation Criteria and Procedure ...………………………..………………..A.3-6\n3.2   Notification…………………...………………………………..………………..A.3-6\n3.3   Outage Assessment…………....…......……………………..………………..A.3-7\n4. Recovery……………………….……………....…………………………………………..A.3-7\n4.1   Sequence of Recovery Activities ....……………………………..…………..A.3-7\n4.2   Recovery Procedures ……...………………………………………..………..A.3-8\n4.3   Recovery Escalation Notices/Awareness..…......……………………..……..A.3-8\n5. Reconstitution..……………….……………....………………….………………..………A.3-8\n5.1   Concurrent Processing …………....………………….…………………..…...A.3-8\n5.2   Validation Data Testing….....………………………….………………….…...A.3-8\n5.3   Validation Functionality Testing.…......……………….………………….…...A.3-9\n5.4   Recovery Declaration…………........………………….………………….…...A.3-9\n5.5   Notification (users)…. ……...………………………….………………….……A.3-9\n5.6   Cleanup ...……………………...…......……………….………………….…….A.3-9\n5.7   Offsite Data Storage……………. ....………………….………………….…...A.3-9\n5.8   Data Backup………………...………………………….…………………..…...A.3-9\n5.9   Event Documentation…………..…......……………….………………….…...A.3-10\n5.10 Deactivation……………………..…......……………….………………….…...A.3-10\nAPPENDICES\n\u000fPlan Approval\nProvide a statement in accordance with the agency’s contingency planning policy to affirm that the ISCP is complete and has been tested sufficiently.  The statement should also affirm that the designated authority is responsible for continued maintenance and testing of the ISCP. This statement should be approved and signed by the system designated authority.  Space should be provided for the designated authority to sign, along with any other applicable approving signatures.  A sample language is provided below:\nAs the designated authority for {system name}, I hereby certify that the information system contingency plan (ISCP) is complete, and that the information contained in this ISCP provides an accurate representation of the application, its hardware, software, and telecommunication components.  I further certify that this document identifies the criticality of the system as it relates to the mission of the {organization name}, and that the recovery strategies identified will provide the ability to recover the system functionality in the most expedient and cost-beneficial method in keeping with its level of criticality.\nI further attest that this ISCP for {system name} will be tested at least annually.  This plan was last tested on {insert exercise date}; the test, training, and exercise (TT&E) material associated with this test can be found {TT&E results appendix or location}.  This document will be modified as changes occur and will remain under version control, in accordance with {organization name}’s contingency planning policy.\n________________________________________\t\t________________________\n{System Owner Name}\t\t\t\t\tDate\n{System Owner Title}\n\u000f1.\tIntroduction\nInformation systems are vital to","cbCaivoFb63Le4cq","https://ap.wps.com/l/cbCaivoFb63Le4cq","docx",57045,"English","# 1. Introduction\n## 1.1 Background\n## 1.2 Scope\n## 1.3 Assumptions\n# 2. Concept of Operations\n## 2.1 System Description\n## 2.2 Overview of Three Phases\n## 2.3 Roles and Responsibilities\n# 3. Activation and Notification\n## 3.1 Activation Criteria and Procedure\n## 3.2 Notification\n## 3.3 Outage Assessment\n# 4. Recovery\n## 4.1 Sequence of Recovery Activities\n## 4.2 Recovery Procedures\n## 4.3 Recovery Escalation Notices/Awareness\n# 5. Reconstitution\n## 5.1 Concurrent Processing\n## 5.2 Validation Data Testing\n## 5.3 Validation Functionality Testing\n## 5.4 Recovery Declaration\n## 5.5 Notification (users)\n## 5.6 Cleanup\n## 5.7 Offsite Data Storage\n## 5.8 Data Backup\n## 5.9 Event Documentation\n## 5.10 Deactivation","[{\"question\":\"What is the purpose of the ISCP in a high-impact system?\",\"answer\":\"The ISCP establishes comprehensive procedures to recover a system quickly and effectively after a service disruption, while supporting continued operations with minimal excessive interruption.\"},{\"question\":\"What phases does the recovery approach include?\",\"answer\":\"The template organizes recovery into three phases: Activation and Notification, Recovery, and Reconstitution, each with defined objectives and activities.\"},{\"question\":\"How does the template address plan testing and approval?\",\"answer\":\"It includes plan approval language to confirm completeness and sufficient testing, and it requires that the ISCP is tested at least annually, with testing details referenced in a TT\\u0026E results appendix or location.\"}]","Information System Contingency Plan (ISCP) - NIST SP 800-34 Rev.1 High Impact System | DOCX",1788280616,6]