{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":44933,"path":"security-management/security-incident-response/si-malic-sftwr-template.md","title":"Security Incident Malicious Software workflow template","bundle":null,"doc_type":null,"release":"australia","body":"\n# Security Incident Malicious Software workflow template\n\nThe Security Incident - Malicious Software - Template allows you to perform a series of tasks designed to handle malicious software on your network.\n\n## Before you begin\n\nRole required: sn\\_si.write\n\n## About this task\n\nThe workflow is triggered when the **Category** in a security incident is set to **Malicious Software**. This action causes a response task to be created for the first activity in the workflow.\n\n\\[Omitted image \"malicious-software-template.png\"\\] Alt text: Malicious Software workflow template\n\n## Procedure\n\n1. Open the security incident for this potential attack, or [create a new security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).\n\n2. In **Category**, select **Malicious code activity**.\n\n3. Save the record.\n\n4. Scroll down and open the **Response Tasks** related list.\n\n The first of a series of response tasks appears. Each time the record is saved, your response to the previous task either causes the next response task to be created or the workflow to end.\n\n\n
\n\nResponse task\n\n\n\nAction\n\n\n\nResults\n\n
\n\nScan Endpoint - Malware Found?\n\n\n\nAfter running a scan, determine whether malware was found.In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the **Remove Malware - Success?** task is executed. If you select **No**, the flow ends.\n\n
\n\nRemove Malware - Success?\n\n\n\nDetermine whether the malware was successfully removed. In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the **Was there a larger breach?** task is executed.If you select **No**, the **Wipe & Reimage** task is executed.\n\n
\n\nWipe & Reimage\n\n\n\nIf you did not successfully remove the malware found, this task instructs you to perform a wipe and reimage on the computers infected with the malware.\n\n\n\nAfter the task is complete, the **Set State to Review** task is executed.\n\n
\n\nWas there a larger breach?\n\n\n\nDetermine whether the breach caused by the malicious software is larger than first believed. In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the following tasks are executed in parallel:- Legal Review\n- HR Review\n- Law Enforcement Review\n If you select **No**, the flow ends.\n\n
\n\nLegal ReviewHR Review\n\n Law Enforcement Review\n\n\n\nPerform the steps necessary for each of these departments to review the process you followed to eradicate the malicious software.\n\n\n\nWhen the tasks are complete, the **Set State to Review** task is executed.\n\n
\n\nSet State to Review\n\n\n\nNo action required.\n\n\n\nThe **State** of the security incident is changed automatically to **Review**, and the flow ends.\n\n
\n**Parent Topic:**[Security Incident Response workflow templates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/sir-orch-workflow-templates.md)\n\n**Related topics** \n\n\n[Security Incident Confidential Data Exposure workflow template]()\n\n[Security Incident Denial of Service workflow template]()\n\n[Security Incident Lost Equipment workflow template]()\n\n[Security Incident Phishing workflow template]()\n\n[Security Incident Policy Violation workflow template]()\n\n[Security Incident Reconnaissance workflow template]()\n\n[Security Incident Rogue Server or Service workflow template]()\n\n[Security Incident Spam workflow template]()\n\n[Security Incident Unauthorized Access workflow template]()\n\n[Security Incident Web/BBS Defacement workflow template]()\n\n"}}