> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-service-was-disabled.md).

# A service was disabled

### Synopsis

| Field                | Value                |
| -------------------- | -------------------- |
| Activation Period    | 14 Days              |
| Training Period      | 30 Days              |
| Test Period          | N/A (single event)   |
| Deduplication Period | 1 Day                |
| Required Data        | XDR Agent            |
| ATT\&CK Tactic       | Impact (TA0040)      |
| ATT\&CK Technique    | Service Stop (T1489) |
| Severity             | Informational        |

### Description

A service was disabled abnormally. This may be performed by malicious actors in an attempt to evade detection or limit functionality.

### Attacker's Goals

* Evade detection by certain programs.
* Limit the functionality and availability of systems, services, and network resources.

### Investigative actions

* Check if the disabled service could potentially threaten a malicious actor, or if holds a critical role.
* Investigate the disabling process to understand if it performed other suspicious actions.

### Variations

<details>

<summary>A service was disabled without using the ServiceControlManager RPC interface</summary>

**Synopsis**

| Field             | Value                |
| ----------------- | -------------------- |
| ATT\&CK Tactic    | Impact (TA0040)      |
| ATT\&CK Technique | Service Stop (T1489) |
| Severity          | Informational        |

**Description**

A service was disabled abnormally through the registry. This may be performed by malicious actors in an attempt to evade detection or limit functionality.

**Attacker's Goals**

* Evade detection by certain programs.
* Limit the functionality and availability of systems, services, and network resources.

**Investigative actions**

* Check if the disabled service could potentially threaten a malicious actor, or if holds a critical role.
* Investigate the disabling process to understand if it performed other suspicious actions.

</details>

<details>

<summary>An injected process performed an uncommon service deactivation</summary>

**Synopsis**

| Field             | Value                |
| ----------------- | -------------------- |
| ATT\&CK Tactic    | Impact (TA0040)      |
| ATT\&CK Technique | Service Stop (T1489) |
| Severity          | Informational        |

**Description**

A service was disabled abnormally. This may be performed by malicious actors in an attempt to evade detection or limit functionality.

**Attacker's Goals**

* Evade detection by certain programs.
* Limit the functionality and availability of systems, services, and network resources.

**Investigative actions**

* Check if the disabled service could potentially threaten a malicious actor, or if holds a critical role.
* Investigate the disabling process to understand if it performed other suspicious actions.

</details>

<details>

<summary>An unsigned process performed an uncommon service deactivation</summary>

**Synopsis**

| Field             | Value                |
| ----------------- | -------------------- |
| ATT\&CK Tactic    | Impact (TA0040)      |
| ATT\&CK Technique | Service Stop (T1489) |
| Severity          | Low                  |

**Description**

A service was disabled abnormally. This may be performed by malicious actors in an attempt to evade detection or limit functionality.

**Attacker's Goals**

* Evade detection by certain programs.
* Limit the functionality and availability of systems, services, and network resources.

**Investigative actions**

* Check if the disabled service could potentially threaten a malicious actor, or if holds a critical role.
* Investigate the disabling process to understand if it performed other suspicious actions.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-service-was-disabled.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.