docs/documentation/platform/pam/discovery/overview.mdx
Infisical PAM Discovery automates the process of finding and cataloging privileged accounts, resources, and service dependencies in your environment. Instead of manually enumerating every server, account, and service, Discovery scans your infrastructure and builds a complete inventory automatically.
Discovery operates in phases that vary by source type. A typical scan includes:
flowchart LR
DS[Discovery Source] --> P1[Phase 1
Infrastructure Scan]
P1 --> R[Resources]
P1 --> A[Accounts]
P1 --> P2[Phase 2
Dependency Scan]
P2 --> D[Dependencies]
Infrastructure Scan — Connects to your environment and enumerates machines and accounts. Each machine becomes a PAM Resource, and each account becomes a PAM Account.
Dependency Scan — Connects to each discovered machine and enumerates services and tasks that run under specific accounts. These are stored as Dependencies linked to the account whose credentials they use.
All network traffic flows through your Infisical Gateway, so no inbound firewall rules are needed.
A Discovery Source is the configuration that tells Infisical what to scan. It includes:
Each scan creates a Run record that tracks:
Resources and accounts that were present in a previous run but not found in the current run are marked as Stale. Stale items are never automatically deleted — they remain visible with a "Stale" badge so you can investigate why a previously-discovered item is no longer responding.
Dependencies represent services and tasks that rely on a specific account's credentials. Discovery currently detects three types:
| Type | Description |
|---|---|
| Windows Service | A Windows service configured to run under a specific account |
| Scheduled Task | A Windows scheduled task that runs under a specific account |
| IIS App Pool | An IIS application pool configured with a specific identity |
Each dependency has an Enabled toggle that defaults to off. When enabled, Infisical will automatically update the dependency's credentials after rotating the linked account's password during credential rotation.
<Info> Dependencies discovered by a scan will never have their **Enabled** status overwritten by subsequent scans. Your explicit enable/disable decisions are always preserved. </Info>Prerequisites vary by discovery type, but all sources require:
Refer to the specific discovery type documentation for detailed prerequisites.
<Warning> Discovery requires an Infisical Gateway. All scan traffic is routed through the Gateway. No direct connectivity from Infisical to your infrastructure is needed. </Warning>