> 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/possible-authentication-coercion.md).
# Possible authentication coercion
### 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) |
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Forced Authentication (T1187), Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001) |
| Severity | Informational |
### Description
An unusual Remote Procedure Call (RPC) was made to potentially cause authentication coercion.
### Attacker's Goals
* An attacker can abuse Remote Procedure Calls to coerce authentication from servers.
### Investigative actions
* Check for a suspicious process on the initiator.
* Check if the source host is a vulnerability scanner.
* Check for unusual connections from {actor\_remote\_ip} to other servers in the network.
* Check for logged-in users to {actor\_remote\_ip} and investigate their actions.
* Check for indicators of compromise on {actor\_remote\_ip}.
### Variations
Possible authentication coercion from an unconstrained delegation server to a sensitive server
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Forced Authentication (T1187), Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001) |
| Severity | Medium |
**Description**
An unusual Remote Procedure Call (RPC) was made towards a sensitive server, to potentially cause authentication coercion.
**Attacker's Goals**
* An attacker can abuse Remote Procedure Calls to coerce authentication from servers.
**Investigative actions**
* Check for a suspicious process on the initiator.
* Check if the source host is a vulnerability scanner.
* Check for unusual connections from {actor\_remote\_ip} to other servers in the network.
* Check for logged-in users to {actor\_remote\_ip} and investigate their actions.
* Check for indicators of compromise on {actor\_remote\_ip}.
Possible authentication coercion to a sensitive server
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006) |
| ATT\&CK Technique | Forced Authentication (T1187), Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001) |
| Severity | Low |
**Description**
An unusual Remote Procedure Call (RPC) was made towards a sensitive server, to potentially cause authentication coercion.
**Attacker's Goals**
* An attacker can abuse Remote Procedure Calls to coerce authentication from servers.
**Investigative actions**
* Check for a suspicious process on the initiator.
* Check if the source host is a vulnerability scanner.
* Check for unusual connections from {actor\_remote\_ip} to other servers in the network.
* Check for logged-in users to {actor\_remote\_ip} and investigate their actions.
* Check for indicators of compromise on {actor\_remote\_ip}.
---
# 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/possible-authentication-coercion.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.