[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-245924-105":53,"doc-detail-245924-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","incident-response-template","Incident Response Template","","Structured cybersecurity incident response template that guides an organization through detection, documentation, and coordinated action. Captures incident overview details such as date detected, reporter information, impacted systems, incident type, severity, scope, and potential consequences. Provides sections for containment strategy with tracked actions, eradication and recovery steps including root-cause identification, restoration, and patching. Includes communication record logging for internal alerts and external reporting requirements, plus post-incident analysis on what worked, what needs improvement, and recommended policy or technical updates.",{"@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":36,"@type":70,"position":76},"https://docshare.wps.com/template/forms/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/incident-response-template/245924/",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/incident-response-template/245924.png","ImageObject",442,249,{"name":88,"@type":89},"Putri","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-22","2026-09-12",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 details should be filled in the incident overview section?","Question",{"text":109,"@type":110},"Record the date detected, reporter name/department, impacted systems, incident type, severity level, scope description, and potential consequences such as data loss or downtime.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"Which containment actions are tracked in the template?",{"text":114,"@type":110},"The template tracks whether the system was isolated, whether malware was removed, and whether external access was blocked, each marked as completed or not.",{"name":116,"@type":107,"acceptedAnswer":117},"What should be included in eradication and recovery?",{"text":118,"@type":110},"Describe what was done to fix and restore systems, including whether the root cause was identified, what systems were restored, and which patches were applied where applicable.","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},245924,1789232138,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":35,"category_name":36,"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":73,"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":126,"read_time":9},962085571259,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","Use this template to help guide your organisation’s response to cybersecurity incidents in a structured and timely manner.  \nIncident Overview  \n\n| ● Date Detected:\u003Cbr>● Reporter Name/Dept:\u003Cbr>● Impacted System(s) :\u003Cbr>● Incident Type: e.g. Malware, Ransomware, Phishing\u003Cbr>Impact & Scope |\n| --- |\n| ● Severity Level: High / Medium / Low\u003Cbr>● Scope Description: Affected systems or users\u003Cbr>● Potential Consequences: [e.g. data](e.g. data) loss, downtime\u003Cbr>Containment Strategy |\n\n\n| Action Taken | Completed? |\n| --- | --- |\n| System isolated | Yes/ No |\n| Malware removed | Yes/ No |\n| External access blocked | Yes/ No |\n\nEradication & Recovery  \nDescribe what was done to fix and restore systems.  \n● Root Cause Identified: Yes / No  \n● Systems Restored: List specifics  \n● Patches Applied: Where applicable  \nCommunication Record  \nLog internal and external updates.  \n● Team Alerts Issued: Yes / No  \n● External Reporting ( DPC, Garda) : Required?  \nPost-Incident Analysis  \n● What worked well?  \n● What needs improvement?  \n● Recommended policy or tech updates:","cbCaimix5c6enVT2","https://ap.wps.com/l/cbCaimix5c6enVT2","pdf",93491,"English","# Incident Overview\n## Impact & Scope\n# Containment Strategy\n# Eradication & Recovery\n# Communication Record\n# Post-Incident Analysis","[{\"question\":\"What details should be filled in the incident overview section?\",\"answer\":\"Record the date detected, reporter name/department, impacted systems, incident type, severity level, scope description, and potential consequences such as data loss or downtime.\"},{\"question\":\"Which containment actions are tracked in the template?\",\"answer\":\"The template tracks whether the system was isolated, whether malware was removed, and whether external access was blocked, each marked as completed or not.\"},{\"question\":\"What should be included in eradication and recovery?\",\"answer\":\"Describe what was done to fix and restore systems, including whether the root cause was identified, what systems were restored, and which patches were applied where applicable.\"}]","Incident Response Template | PDF"]