> 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/unique-client-computer-model-was-detected-via-ms-update-protocol.md).

# Unique client computer model was detected via MS-Update protocol

### Synopsis

| Field                | Value                                |
| -------------------- | ------------------------------------ |
| Activation Period    | 14 Days                              |
| Training Period      | 30 Days                              |
| Test Period          | N/A (single event)                   |
| Deduplication Period | 7 Days                               |
| Required Data        | Palo Alto Networks Firewall EAL Logs |
| ATT\&CK Tactic       | Initial Access (TA0001)              |
| ATT\&CK Technique    | Hardware Additions (T1200)           |
| Severity             | Informational                        |

### Description

A unique client computer model was detected via MS-Update protocol.

### Attacker's Goals

* The Windows Server Update Services enable machines to discover and download software updates from a dedicated update server while providing the necessary client characteristics to install the suitable client version and build.
* Characteristics may consist of computer model, BIOS version and architecture.
* A unique computer model in the network may indicate an unauthorized and unmanaged connection to the internal network.

### Investigative actions

* Inspect the legitimacy of the host and its hardware components.
* Verify that this host is not a newly deployed end-point or virtual machine as part of a legitimate IT activity.


---

# 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/unique-client-computer-model-was-detected-via-ms-update-protocol.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.