{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":44929,"path":"security-management/security-incident-response/si-denial-of-service-template.md","title":"Security Incident Denial of Service workflow template","bundle":null,"doc_type":null,"release":"australia","body":"\n# Security Incident Denial of Service workflow template\n\nThe Security Incident - Denial of Service - Template allows you to perform a series of tasks designed to handle Denial of Service \\(DOS\\) attacks.\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 **Denial of Service**. This action causes a response task to be created for the first activity in the workflow.\n\n\\[Omitted image \"denial-of-service-wf-template.png\"\\] Alt text: Denial of ServiceTemplate\n\n## Procedure\n\n1. Open the security incident for this denial of service occurrence, 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 **Denial of Service**.\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 flow to end.\n\n\n
\n\nResponse task\n\n\n\nAction\n\n\n\nResults\n\n
\n\nIs target business critical?\n\n\n\nDetermine if the target of this DOS attack is business critical. In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the **Set priority to critical** task is executed. If you select **No**, the **Is a vulnerability being exploited?** task is executed.\n\n
\n\nSet priority to critical\n\n\n\nNo action required.\n\n\n\nThe **Priority** of the security incident is changed automatically to **Critical**, and the **Is a vulnerability being exploited?** task is executed.\n\n
\n\nIs a vulnerability being exploited?\n\n\n\nDetermine whether this DOS attack exploits a software vulnerability. In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the **Emergency patch request** task is executed. If you select **No**, the **Internal attacker?** task is executed.\n\n
\n\nEmergency patch request\n\n\n\nIssue an emergency patch request for the system\\(s\\) being attacked.Update the **State** field in the task as appropriate.\n\n\n\nIf you changed the state of the task to **Closed Complete** or **Cancelled**, the next response task is executed.\n\n
\n\nInternal attacker?\n\n\n\nDetermine if the source of this DOS attack is internal to your organization. In the task, select **Yes** or **No** in **Outcome**.\n\n\n\nIf you select **Yes**, the **Isolate attacking host\\(s\\)** task is executed. If you select **No**, the **Notify DOS protection provider and/or ISP** task is executed.\n\n
\n\nIsolate the attacking host\\(s\\)\n\n\n\nPerform the steps necessary to isolate the internal host\\(s\\) responsible for the attack. Update the **State** field in the task as appropriate.\n\n\n\nAfter you complete this step, the **Validate system integrity of attacked systems** task is executed.\n\n
\n\nNotify DOS protection provider and/or ISP\n\n\n\nPerform the steps necessary to contact your Denial of Service protection provider and/or your Internet Service Provider to notify them of the attack. Update the **State** field in the task as appropriate.\n\n\n\nIf you changed the state of the task to **Closed Complete** or **Cancelled**, the next response task is executed.\n\n
\n\nValidate system integrity of attacked systems\n\n\n\nPerform the steps necessary to assess and validate the integrity of the attacked computers. Update the **State** field in the task as appropriate.\n\n\n\nIf you changed the state of the task to **Closed Complete** or **Cancelled**, the next response task is executed.\n\n
\n\nReview DOS protections\n\n\n\nConduct a review of your existing DOS protections and procedures. Make any necessary changes. Update the **State** field in the task as appropriate.\n\n\n\nIf you changed the state of the task to **Closed Complete** or **Cancelled**, the next response 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**. The **Lessons learned meeting** task is executed.\n\n
\n\nLessons learned meeting\n\n\n\nConduct a lessons learned meeting to triage the work performed for this Denial of Service incident. Update the **State** field in the task as appropriate.\n\n\n\nIf you change the state of the task to **Closed Complete** or **Cancelled**, 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 Lost Equipment workflow template]()\n\n[Security Incident Malicious Software 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"}}