> 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-entra-id-device-code-authentication-flow.md).
# Suspicious Entra ID Device Code Authentication Flow
### 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 | Identity Threat Module |
| ATT\&CK Tactic | Persistence (TA0003), Lateral Movement (TA0008) |
| ATT\&CK Technique | Account Manipulation (T1098), Use Alternate Authentication Material (T1550) |
| Severity | Informational |
### Description
A user authenticated via Entra ID device code flow.
### Attacker's Goals
* An adversary may leverage an access token generated from a device code authentication flow to gain unauthorized access to tenant resources, which can aid in bypassing multi-factor authentication (MFA) and avoiding traditional endpoint detection.
### Investigative actions
* Validate if the account is authorized to use device flow to access resources.
* Examine possible logins from the IP address.
* Follow further actions done by the account and the IP address.
### Variations
Suspicious Entra ID Device Code Authentication Flow with suspicious characteristics
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Lateral Movement (TA0008) |
| ATT\&CK Technique | Account Manipulation (T1098), Use Alternate Authentication Material (T1550) |
| Severity | Medium |
**Description**
A user authenticated via Entra ID device code flow.
**Attacker's Goals**
* An adversary may leverage an access token generated from a device code authentication flow to gain unauthorized access to tenant resources, which can aid in bypassing multi-factor authentication (MFA) and avoiding traditional endpoint detection.
**Investigative actions**
* Validate if the account is authorized to use device flow to access resources.
* Examine possible logins from the IP address.
* Follow further actions done by the account and the IP address.
Suspicious Entra ID Device Code Authentication Flow from a risky IP address
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Lateral Movement (TA0008) |
| ATT\&CK Technique | Account Manipulation (T1098), Use Alternate Authentication Material (T1550) |
| Severity | Low |
**Description**
A user authenticated via Entra ID device code flow.
**Attacker's Goals**
* An adversary may leverage an access token generated from a device code authentication flow to gain unauthorized access to tenant resources, which can aid in bypassing multi-factor authentication (MFA) and avoiding traditional endpoint detection.
**Investigative actions**
* Validate if the account is authorized to use device flow to access resources.
* Examine possible logins from the IP address.
* Follow further actions done by the account and the IP address.
Suspicious Entra ID Device Code Authentication Flow with Entra Identity Protection risk
**Synopsis**
| Field | Value |
| ----------------- | --------------------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003), Lateral Movement (TA0008) |
| ATT\&CK Technique | Account Manipulation (T1098), Use Alternate Authentication Material (T1550) |
| Severity | Low |
**Description**
A user authenticated via Entra ID device code flow.
**Attacker's Goals**
* An adversary may leverage an access token generated from a device code authentication flow to gain unauthorized access to tenant resources, which can aid in bypassing multi-factor authentication (MFA) and avoiding traditional endpoint detection.
**Investigative actions**
* Validate if the account is authorized to use device flow to access resources.
* Examine possible logins from the IP address.
* Follow further actions done by the account and the IP address.
---
# 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-entra-id-device-code-authentication-flow.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.