Security Incident Policy Violation workflow template
The Security Incident - Policy Violation - Template allows you to perform a series of tasks designed to handle security policy violations.
Before you begin
Role required: sn_si.write
About this task
The workflow is triggered when the Category in a security incident is set to Policy violation. This action causes a response task to be created for the first activity in the workflow.
[Omitted image "policy-violation-wf-template.png"] Alt text: Policy Violation Template
Procedure
-
Open the security incident for the policy violation, or create a new security incident.
-
In Category, select Policy violation.
-
Save the record.
-
Scroll down and open the Response Tasks related list.
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.
|
Response task |
Action |
Results |
|---|---|---|
|
Classify violation |
Classify how this infraction violates your organization's security policies. Update the State field in the task after you have completed it. |
The Advise violator of infraction response task is executed. |
|
Advise violator of infraction |
Communicate the nature of the infraction to the violator. Update the State field in the task after you have communicated it. |
The Obtain acknowledgement from violator response task is executed. |
|
Obtain acknowledgement from violator |
Obtain an acknowledgement from the violator of the infraction. Update the State field in the task as appropriate. |
The HR process response task is executed. |
|
HR process |
Communicate all necessary information about this violation to HR. Update the State field in the task as appropriate. |
The Set state to review response task is executed. |
|
Set state to review |
No action is necessary. |
The State of the security incident is changed automatically to Review. |
|
Schedule security awareness training |
Conduct a security awareness training to educate staff on how to prevent similar security violations in the future. Update the State field in the task as appropriate. |
If you change the state of the task to Closed Complete or Cancelled, the flow ends. |
Related topics
Security Incident Confidential Data Exposure workflow template
Security Incident Denial of Service workflow template
Security Incident Lost Equipment workflow template
Security Incident Malicious Software workflow template
Security Incident Phishing workflow template
Security Incident Reconnaissance workflow template
Security Incident Rogue Server or Service workflow template
Security Incident Spam workflow template
---
title: Security Incident Policy Violation workflow template
description: The Security Incident - Policy Violation - Template allows you to perform a series of tasks designed to handle security policy violations.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/si-policy-violation-template.html
release: australia
product: Security Incident Response
classification: security-incident-response
topic_type: task
last_updated: "2026-09-10"
reading_time_minutes: 3
breadcrumb: [Security Incident Response workflow templates, Understand Security Incident Response Orchestration workflows and workflow templates, Security Incident Response Orchestration, Security Incident Response, Enterprise security case management applications, Security Operations]
---
# Security Incident Policy Violation workflow template
The Security Incident - Policy Violation - Template allows you to perform a series of tasks designed to handle security policy violations.
## Before you begin
Role required: sn\_si.write
## About this task
The workflow is triggered when the **Category** in a security incident is set to **Policy violation**. This action causes a response task to be created for the first activity in the workflow.
\[Omitted image "policy-violation-wf-template.png"\] Alt text: Policy Violation Template
## Procedure
1. Open the security incident for the policy violation, or [create a new security incident](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/security-incident-response/t_ManuallyCreateSecurityIncident.md).
2. In **Category**, select **Policy violation**.
3. Save the record.
4. Scroll down and open the **Response Tasks** related list.
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.
<table id="table_ors_srs_kbb"><thead><tr><th>
Response task
</th><th>
Action
</th><th>
Results
</th></tr></thead><tbody><tr><td>
Classify violation
</td><td>
Classify how this infraction violates your organization's security policies. Update the **State** field in the task after you have completed it.
</td><td>
The **Advise violator of infraction** response task is executed.
</td></tr><tr><td>
Advise violator of infraction
</td><td>
Communicate the nature of the infraction to the violator. Update the **State** field in the task after you have communicated it.
</td><td>
The **Obtain acknowledgement from violator** response task is executed.
</td></tr><tr><td>
Obtain acknowledgement from violator
</td><td>
Obtain an acknowledgement from the violator of the infraction. Update the **State** field in the task as appropriate.
</td><td>
The **HR process** response task is executed.
</td></tr><tr><td>
HR process
</td><td>
Communicate all necessary information about this violation to HR. Update the **State** field in the task as appropriate.
</td><td>
The **Set state to review** response task is executed.
</td></tr><tr><td>
Set state to review
</td><td>
No action is necessary.
</td><td>
The **State** of the security incident is changed automatically to **Review**.
</td></tr><tr><td>
Schedule security awareness training
</td><td>
Conduct a security awareness training to educate staff on how to prevent similar security violations in the future. Update the **State** field in the task as appropriate.
</td><td>
If you change the state of the task to **Closed Complete** or **Cancelled**, the flow ends.
</td></tr></tbody>
</table>
**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)
**Related topics**
[Security Incident Confidential Data Exposure workflow template]()
[Security Incident Denial of Service workflow template]()
[Security Incident Lost Equipment workflow template]()
[Security Incident Malicious Software workflow template]()
[Security Incident Phishing workflow template]()
[Security Incident Reconnaissance workflow template]()
[Security Incident Rogue Server or Service workflow template]()
[Security Incident Spam workflow template]()
[Security Incident Unauthorized Access workflow template]()
[Security Incident Web/BBS Defacement workflow template]()
| title | Security Incident Policy Violation workflow template |
| description | The Security Incident - Policy Violation - Template allows you to perform a series of tasks designed to handle security policy violations. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/si-policy-violation-template.html |
| release | australia |
| product | Security Incident Response |
| classification | security-incident-response |
| topic_type | task |
| last_updated | 2026-09-10 |
| reading_time_minutes | 3 |
| breadcrumb | Security Incident Response workflow templatesUnderstand Security Incident Response Orchestration workflows and workflow templatesSecurity Incident Response OrchestrationSecurity Incident ResponseEnterprise security case management applicationsSecurity Operations |