---
title: Security Incident Rogue Server or Service workflow template
description: The Security Incident - Rogue Server or Service - Template allows you to perform a series of tasks designed to handle activity from rogue servers or services affecting your network.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/security-management/security-incident-response/si-rogue-wf-template.html
release: australia
product: Security Incident Response
classification: security-incident-response
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 4
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 Rogue Server or Service workflow template

The Security Incident - Rogue Server or Service - Template allows you to perform a series of tasks designed to handle activity from rogue servers or services affecting your network.

## 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 **Rogue server or service**. This action causes a response task to be created for the first activity in the workflow.

\[Omitted image "rogue.png"\] Alt text: Rogue server or service workflow template

## Procedure

1.  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).

2.  In **Category**, select **Rogue server or service activity**.

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_kfs_lvs_kbb"><thead><tr><th>

Response task

</th><th>

Action

</th><th>

Results

</th></tr></thead><tbody><tr><td>

Rogue server or service verified?

</td><td>

Determine whether a connection with a rogue server or service has been verified on your network.In the task, select **Yes** or **No** in **Outcome**.

</td><td>

If you select **Yes**, the following two tasks are executed in parallel:-   **Identify impacted system\(s\)**
-   **Potential data loss?**
 If you select **No**, the flow ends.

</td></tr><tr><td>

Identify impacted system\(s\)

</td><td>

Determine the systems impacted by contact with the rogue server or service.

</td><td>

When this task is complete, the **Update system\(s\) - Remove rogue connections** task is executed.

</td></tr><tr><td>

Potential data loss?

</td><td>

Determine whether the connection with the rogue server or service caused potential data loss. In the task, select **Yes** or **No** in **Outcome**.

</td><td>

If you select **Yes**, the **Create potential data loss incident** task is executed.If you select **No**, the **Update system\(s\) - Remove rogue connections** task is executed.

</td></tr><tr><td>

Create potential data loss incident

</td><td>

Perform the steps necessary to create a security incident for the potential data loss.

</td><td>

When this task is complete, the **Update system\(s\) - Remove rogue connections** task is executed.

</td></tr><tr><td>

Update system\(s\) - Remove rogue connections

</td><td>

Perform the steps necessary to remove the rogue connections.

</td><td>

When this task is complete, the **Set state to review** task is executed.

</td></tr><tr><td>

Set state to review

</td><td>

No action required.

</td><td>

The **State** of the security incident is changed automatically to **Review**, and the **Lessons learned meeting** task is executed.

</td></tr><tr><td>

Lessons learned meeting

</td><td>

Conduct a lessons learned meeting to triage the work performed for this rogue server or service incident. Update the **State** field in the task as appropriate.

</td><td>

When this task is complete, 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 Policy Violation workflow template]()

[Security Incident Reconnaissance workflow template]()

[Security Incident Spam workflow template]()

[Security Incident Unauthorized Access workflow template]()

[Security Incident Web/BBS Defacement workflow template]()