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.

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.

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.

Parent Topic:Security Incident Response workflow templates

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}[]