> 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/suspicious-udev-driver-rule-execution-manipulation.md).
# Suspicious Udev driver rule execution manipulation
### 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 with eXtended Threat Hunting (XTH) |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity | Low |
### Description
Udev driver rule was modified with unusual pattern, might be used by adversaries to backdoor existing drivers.
### Attacker's Goals
Adversaries can use this technique to execute arbitrary commands once the machine boots.
### Investigative actions
* Check if the action was done using an automation service.
* Check the rule modification content and look for any suspicious payloads.
* Check if there are any other suspicious activities originated from the same machine/executing user.
### Variations
Unusual Udev driver rule execution manipulation
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Privilege Escalation (TA0004) |
| ATT\&CK Technique | Boot or Logon Autostart Execution: Kernel Modules and Extensions (T1547.006) |
| Severity | Low |
**Description**
Udev driver rule was modified with unusual pattern, might be used by adversaries to backdoor existing drivers.
**Attacker's Goals**
Adversaries can use this technique to execute arbitrary commands once the machine boots.
**Investigative actions**
* Check if the action was done using an automation service.
* Check the rule modification content and look for any suspicious payloads.
* Check if there are any other suspicious activities originated from the same machine/executing user.
---
# 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/suspicious-udev-driver-rule-execution-manipulation.md?ask=&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.