> 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/new-administrative-behavior.md).
# New Administrative Behavior
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 12 Hours |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
Palo Alto Networks Firewall traffic Logs OR XDR Agent OR Third-Party Firewalls
|
| Detector Tags | NDR Lateral Movement Analytics |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services (T1021) |
| Severity | Medium |
### Description
The endpoint performed new administrative actions, relative to its previously profiled behavior. It is possible that an endpoint will infrequently be used for administrative activities, so analytics is performed using logs collected over a long period of time, also comparing the activity to that of other endpoints. That is, if many endpoints are contacting the same destination with the same administrative activity, then this network activity is less likely to result in this alert.
An attacker may be operating on the host, probing other computers and moving laterally inside the network using a trusted computer and credentials. Attackers typically exhibit administrative behaviors when performing reconnaissance and lateral movement.
### Attacker's Goals
An attacker is using administrative functions to move from one endpoint to another, or to scan the network for new endpoints to attack.
### Investigative actions
Investigate the endpoint to determine if it is legitimately being used for administrative functions.
### Variations
New SSH Administrative Behavior
**Synopsis**
| Field | Value |
| ----------------- | ------------------------- |
| ATT\&CK Tactic | Lateral Movement (TA0008) |
| ATT\&CK Technique | Remote Services (T1021) |
| Severity | Informational |
**Description**
The endpoint performed new SSH administrative actions, relative to its previously profiled behavior. It is possible that an endpoint will infrequently be used for administrative activities, so analytics is performed using logs collected over a long period of time, also comparing the activity to that of other endpoints. That is, if many endpoints are contacting the same destination with the same administrative activity, then this network activity is less likely to result in this alert.
An attacker may be operating on the host, probing other computers and moving laterally inside the network using a trusted computer and credentials. Attackers typically exhibit administrative behaviors when performing reconnaissance and lateral movement.
**Attacker's Goals**
An attacker is using administrative functions to move from one endpoint to another, or to scan the network for new endpoints to attack.
**Investigative actions**
Investigate the endpoint to determine if it is legitimately being used for administrative functions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/new-administrative-behavior.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.