---
title: "What naming convention is recommended for Spirion Agents?"
url: "https://dm0bkdes5q7a2ls.productfruits.help/en/article/what-naming-convention-is-recommended-for-spirion-agents"
language: "en"
last_updated: "2026-10-10T01:15:16.380Z"
---

# What naming convention is recommended for Spirion Agents?

Naming conventions apply to both individual Agent endpoints/hosts and Agent Pools (Teams).

In **Spirion Sensitive Data Platform (SDP)** and enterprise deployments, naming conventions apply to both **individual Agent endpoints/hosts** and **Agent Pools (Teams)**.

## 1\. Individual Agent Host Naming Standard

For host machines running the Spirion Endpoint Agent service (`identityfinderCMD.exe` / `idfEndpoint.exe`), follow the standard host/VM naming convention:

Format: \[LOCATION\]-\[ENV\]-\[TYPE\]\[INDEX\]

### **Segment Definitions:**

-   `[LOCATION]` (Site Code):
-   -   `AZ1`: Azure East US / `AZ2`: Azure West US
    -   `ONPREM`: On-Premises Data Center
    -   `FL1` / `NY1`: Regional Office / Remote (`RM1`)
-   `[ENV]` (Environment Tier):
-   -   `P`: Production
    -   `D`: Development / `Q`: QA / `T`: Test
-   `[TYPE]` (Purpose Code):
-   -   `UT`: Utility Server / Dedicated Discovery Agent Worker
    -   `WS`: End-user Workstation / Laptop
    -   `FS`: File Server with local agent
-   `[INDEX]`: Numeric suffix (`001`, `002`, etc.)

#### **Examples:**

-   `AZ1-P-UT001` -> Azure East US Production Dedicated Discovery Agent #1
-   `ONPREM-D-UT002` -> On-Premises Development Discovery Agent #2
-   `FL1-P-WS045` -> Florida Office Production Workstation Agent #45

> **Note:** Hostnames for Windows Agent machines should stay within the **15-character NetBIOS limit**.

## 2\. Agent Pool (Team) Naming Standard

When grouping agents into **Agent Pools** in the Spirion Sensitive Data Platform Console for dynamic load balancing and multi-target discovery scans:

Format: \[SCOPE/GEO\]-\[PURPOSE/ENV\]-AgentPool

### **Standard Examples:**

-   **Geographic / Data Center Pools:**
-   -   `GEO-EU-West-AgentPool` (or `EU-Frankfurt Agent Pool`)
    -   `US-East OnPrem Pool`
-   **Target / Workload Specific Pools:**
-   -   `Central Discovery Pool`
    -   `Cloud Discovery Pool`
    -   `PCI-Isolated-AgentPool`
-   **Environment-Routed Default Pools (SDP Automation):**
-   -   `WARP-I*` (Integration Environment)
    -   `WARP-Q*` (QA Environment)
    -   `WARP-T*` (Test/Staging Environment)

## 3\. Key Naming & Operational Rules

1.  **Avoid "Watcher" in Worker Names:** Never include `Watcher` or `WatcherAgent` in scan worker names. In Spirion Sensitive Data Platform, Watcher processes (`watcher: true`) are reserved for health monitoring and are filtered out from scan job allocation.
2.  **Align Pools with Targets:** Ensure the Agent Pool name directly reflects the scan Target scope
3.  1.  For example, Target `PROD-EU-WEST-CLOUD-S3` connects to Agent Pool `GEO-EU-West-AgentPool`).
4.  **Environment Isolation:** Include the environment tier (`PROD`, `QA`, `TEST`) in the Agent name to prevent accidental cross-environment registration in the Spirion Sensitive Data Platform console.