> 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-authentication-package-registered.md).

# Suspicious authentication package registered

### Synopsis

| Field                | Value                                                                 |
| -------------------- | --------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                               |
| Training Period      | 30 Days                                                               |
| Test Period          | N/A (single event)                                                    |
| Deduplication Period | 14 Days                                                               |
| Required Data        | XDR Agent                                                             |
| ATT\&CK Tactic       | Persistence (TA0003)                                                  |
| ATT\&CK Technique    | Boot or Logon Autostart Execution: Authentication Package (T1547.002) |
| Severity             | Medium                                                                |

### Description

The endpoint registered a suspicious authentication package, which may be used to gain persistence on the host by loading libraries into the time management service.

### Attacker's Goals

Gain persistence using the legitimate Windows authentication package mechanism, which loads libraries into Windows services.

### Investigative actions

* Verify if the registered library is malicious.
* Check if the installing software is a malicious binary.
* Check for any suspicious network activity from "lsass.exe".


---

# 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-authentication-package-registered.md?ask=<question>&goal=<user_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.