> 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/azure-route-table-creation-or-modification.md).
# Azure route table creation or modification
### Synopsis
| Field | Value |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Azure Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Lateral Movement (TA0008), Defense Impairment (TA0112) |
| ATT\&CK Technique | Modify Cloud Compute Infrastructure (T1578), Network Boundary Bridging (T1599), Remote Services: Cloud Services (T1021.007) |
| Severity | Informational |
### Description
An Azure route table, or one of its individual routes, was created or modified. Azure route tables control how traffic flows between subnets and virtual networks. Adversaries can tamper with route tables to redirect traffic to attacker-controlled destinations, bypassing security appliances or enabling man-in-the-middle attacks.
### Attacker's Goals
Redirect or intercept network traffic, bypass security appliances (firewalls, NVAs), or enable lateral movement between Azure subnets.
### Investigative actions
* Verify whether the identity should be making route table changes.
* Inspect the route's address prefix and next-hop -- a 0.0.0.0/0 route pointing at a Virtual Appliance or an internal IP is a strong tamper indicator.
* Examine other API calls made by the identity around the same time.
### Variations
Unusual Azure route table creation or modification
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008), Defense Impairment (TA0112) |
| ATT\&CK Technique | Modify Cloud Compute Infrastructure (T1578), Network Boundary Bridging (T1599), Remote Services: Cloud Services (T1021.007) |
| Severity | Low |
**Description**
An Azure route table, or one of its individual routes, was created or modified. Azure route tables control how traffic flows between subnets and virtual networks. Adversaries can tamper with route tables to redirect traffic to attacker-controlled destinations, bypassing security appliances or enabling man-in-the-middle attacks.
**Attacker's Goals**
Redirect or intercept network traffic, bypass security appliances (firewalls, NVAs), or enable lateral movement between Azure subnets.
**Investigative actions**
* Verify whether the identity should be making route table changes.
* Inspect the route's address prefix and next-hop -- a 0.0.0.0/0 route pointing at a Virtual Appliance or an internal IP is a strong tamper indicator.
* Examine other API calls made by the identity around the same time.
---
# 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/azure-route-table-creation-or-modification.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.