Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Understand Security Incident Response Orchestration workflows and workflow templates

Log in to subscribe to topics and get notified when content changes.

Understand Security Incident Response Orchestration workflows and workflow templates

The Security Incident Response base system includes a series of workflows and workflow templates designed to work with security incident records.

Before you begin

You can tailor all workflows and workflow templates to better suit your needs, assuming you have the appropriate role: sn_sec_cmn.admin. Workflows are used throughout the Security Operations system to perform a variety of tasks.

Workflow templates, however, are triggered by selecting a value in the Category field in a security incident. When this occurs, the workflow template associated with the selection kicks off a workflow template that instructs the security analysts how to deal with a specific type of threat.

For example, if you select Denial of Service from the Category field in a security incident, the Security Incident - Denial of Service - Template is executed and the analyst is directed to determine whether the target of the DOS is business critical. If so, the next task causes the priority of the security incident to be set to 1 - Critical, and then executes the next task. And so on.

So Security Incident Response workflows and workflow templates are essentially the same, except the templates are used for a specific set of functions within a security incident.

Role required: sn_si.basic


  1. Navigate to Security Operations > Workflows > View Security Workflows.
  2. A list of the workflows and workflow templates shipped in the base system are displayed. Any new workflows that you have created in the Security Operations application suite are also included in the list.
  3. Click the name of the workflow or workflow template you want to view.
    Note: Workflows can be triggered in several different ways. Be aware that associating a workflow with a workflow trigger does not necessarily mean the workflow is active.