> 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-time-provider-registered.md).
# Suspicious time provider registered
### 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 |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution: Time Providers (T1547.003) |
| Severity | Medium |
### Description
The endpoint time provider has been tampered, this change 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 time provider mechanism, which loads libraries into Windows services.
### Investigative actions
* Verify if the registered library is malicious.
* Check if the software performing the installation is a malicious binary.
* Check for any network activity from a "svchost.exe -k LocalService" process that seems suspicious.
### Variations
Suspicious time provider registered manually by reg.exe
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution: Time Providers (T1547.003) |
| Severity | High |
**Description**
The endpoint time provider has been tampered, this change 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 time provider mechanism, which loads libraries into Windows services.
**Investigative actions**
* Verify if the registered library is malicious.
* Check if the software performing the installation is a malicious binary.
* Check for any network activity from a "svchost.exe -k LocalService" process that seems suspicious.
Suspicious time provider registered using an uncommon provider name
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------- |
| ATT\&CK Tactic | Persistence (TA0003) |
| ATT\&CK Technique | Boot or Logon Autostart Execution: Time Providers (T1547.003) |
| Severity | High |
**Description**
The endpoint time provider has been tampered, this change 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 time provider mechanism, which loads libraries into Windows services.
**Investigative actions**
* Verify if the registered library is malicious.
* Check if the software performing the installation is a malicious binary.
* Check for any network activity from a "svchost.exe -k LocalService" process that seems suspicious.
---
# 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/suspicious-time-provider-registered.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.