[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-seo-189312-105":3,"detail-sidebar-cat-1-en-105":81,"doc-detail-189312-en":127},{"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","company-name-cybersecurity-incident-response-plan-version-10","{Company Name} Cybersecurity Incident Response Plan - Version 1.0","","This document outlines the {Company Name} Cybersecurity Incident Response Plan, version 1.0. It details the procedures and protocols to be followed in the event of a cybersecurity incident. The plan includes sections for Document Owner, Approval Dates, Reviewers, Version History, Testing Procedures, and a Severity/Impact Matrix. The Severity Matrix defines incident levels from 1 (Severe: Widespread Sensitive Data Compromise) to 4 (None: Isolated Systems), based on Business Impact and Scope. Key personnel roles and their responsibilities during an incident are to be defined, along with the review and approval process. The document emphasizes the importance of regular testing and updates to ensure the plan's effectiveness in mitigating and responding to cyber threats. It serves as a critical framework for maintaining operational continuity and protecting sensitive data in the face of sophisticated cyberattacks.",{"@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/general/","General",3,{"item":32,"name":10,"@type":21,"position":33},"https://docshare.wps.com/template/company-name-cybersecurity-incident-response-plan-version-10/189312/",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/company-name-cybersecurity-incident-response-plan-version-10/189312.png","ImageObject",442,249,{"name":42,"@type":43},"Maeve","Person",{"url":19,"name":45,"@type":46},"DocShare","Organization","application/pdf","2026-09-27","2026-09-03",true,{"@type":52,"interactionType":53,"userInteractionCount":55},"InteractionCounter",{"@type":54},"ViewAction",6,{"@type":57,"mainEntity":58},"FAQPage",[59,65,69],{"name":60,"@type":61,"acceptedAnswer":62},"What is the purpose of the Cybersecurity Incident Response Plan?","Question",{"text":63,"@type":64},"The plan outlines the procedures and protocols to be followed in the event of a cybersecurity incident to mitigate impact and ensure operational continuity.","Answer",{"name":66,"@type":61,"acceptedAnswer":67},"How are cybersecurity incidents classified in this plan?",{"text":68,"@type":64},"Incidents are classified based on severity, ranging from 1 (Severe: Widespread Sensitive Data Compromise) to 4 (None: Isolated Systems), considering business impact and scope.",{"name":70,"@type":61,"acceptedAnswer":71},"Who is responsible for the Cybersecurity Incident Response Plan?",{"text":72,"@type":64},"The plan designates a Document Owner and Reviewers responsible for its maintenance, approval, and updates, with specific roles and responsibilities to be defined.","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},189312,1788395911,{"code":4,"msg":82,"data":83},"success",[84,89,94,99,104,109,114,119,124],{"id":85,"doc_module":22,"doc_module_name":25,"category_name":86,"show_sort_weight":87,"slug":88},11,"Presentations",90,"presentations",{"id":90,"doc_module":22,"doc_module_name":25,"category_name":91,"show_sort_weight":92,"slug":93},12,"Resumes",80,"resumes",{"id":95,"doc_module":22,"doc_module_name":25,"category_name":96,"show_sort_weight":97,"slug":98},14,"Invoices",70,"invoices",{"id":100,"doc_module":22,"doc_module_name":25,"category_name":101,"show_sort_weight":102,"slug":103},15,"Posters",60,"posters",{"id":105,"doc_module":22,"doc_module_name":25,"category_name":106,"show_sort_weight":107,"slug":108},16,"Social Media",50,"social-media",{"id":110,"doc_module":22,"doc_module_name":25,"category_name":111,"show_sort_weight":112,"slug":113},17,"Forms",40,"forms",{"id":115,"doc_module":22,"doc_module_name":25,"category_name":116,"show_sort_weight":117,"slug":118},18,"Letters",30,"letters",{"id":120,"doc_module":22,"doc_module_name":25,"category_name":121,"show_sort_weight":122,"slug":123},21,"Paper Templates",5,"papers-templates",{"id":125,"doc_module":22,"doc_module_name":25,"category_name":29,"show_sort_weight":4,"slug":126},158,"general-158",{"code":4,"msg":82,"data":128},{"doc_id":79,"user_id":129,"nickname":42,"user_avatar":130,"doc_module":22,"category_id":125,"category_name":29,"doc_title":10,"doc_description":12,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":55,"is_deleted":4,"is_public":22,"is_downloadable":22,"audit_status":22,"page_count":136,"language":137,"language_code":8,"site_id":7,"html_lang":8,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":12,"update_tm":80,"read_time":90},5909877438554,"https://ap-avatar.wpscdn.com/avatar/5600025385ad2bf12a7?_k=1778553567797529272","| Type of Information | Document Data |\n| --- | --- |\n| Title | {Company Name} Cybersecurity Incident Response Plan |\n| Document Version | 1.0 |\n| Last Update |  |\n| Document Owner |  |\n\n\n| Name | Role | Date Approved | Email Address |\n| --- | --- | --- | --- |\n|  |  |  |  |\n|  |  |  |  |\n|  |  |  |  |\n\n\n| Reviewer | Role | Email Address |\n| --- | --- | --- |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n\n\n| Version\u003Cbr>Number | Version Date | Author/Reviser | Nature of Change | Date\u003Cbr>Approved |\n| --- | --- | --- | --- | --- |\n| 1.0 |  |  | Initial Version |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n|  |  |  |  |  |\n\n| Test Date | Authority | Notes |\n| --- | --- | --- |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n|  |  |  |\n\n| Severity | Business Impact | Scope |\n| --- | --- | --- |\n| 4 | None | Isolated Systems |\n| 3 | Limited | Isolated Environment |\n| 2 | Moderate | Limited / More widespread |\n| 1 | Severe | Widespread Sensitive Data Compromise |","cbCaiofmHGhGIoYf","https://ap.wps.com/l/cbCaiofmHGhGIoYf","pdf",316446,35,"English","# {Company Name} Cybersecurity Incident Response Plan\n# Document Metadata\n## Document Version\n## Last Update\n## Document Owner\n# Approval\n## Name\n## Role\n## Date Approved\n## Email Address\n# Review\n## Reviewer\n## Role\n## Email Address\n# Version History\n## Version Number\n## Version Date\n## Author/Reviser\n## Nature of Change\n## Date Approved\n# Testing\n## Test Date\n## Authority\n## Notes\n# Severity Matrix\n## Severity\n## Business Impact\n## Scope","[{\"question\":\"What is the purpose of the Cybersecurity Incident Response Plan?\",\"answer\":\"The plan outlines the procedures and protocols to be followed in the event of a cybersecurity incident to mitigate impact and ensure operational continuity.\"},{\"question\":\"How are cybersecurity incidents classified in this plan?\",\"answer\":\"Incidents are classified based on severity, ranging from 1 (Severe: Widespread Sensitive Data Compromise) to 4 (None: Isolated Systems), considering business impact and scope.\"},{\"question\":\"Who is responsible for the Cybersecurity Incident Response Plan?\",\"answer\":\"The plan designates a Document Owner and Reviewers responsible for its maintenance, approval, and updates, with specific roles and responsibilities to be defined.\"}]","{Company Name} Cybersecurity Incident Response Plan - Version 1.0 | PDF"]