Discovery is the process of finding AI agents and other non human identities already operating in an environment. It relies on telemetry from browsers, directories, and devices to build an inventory of tools, workloads, and access paths that may otherwise remain invisible to central IT.
Expanded Definition
In NHI security, discovery is the controlled process of identifying AI agents, service accounts, API keys, certificates, and other non human identities that already exist in an environment. It is broader than simple asset inventory because it also maps where identities authenticate, which systems they touch, and which telemetry sources can prove they are active.
Definitions vary across vendors, but the practical distinction is consistent: discovery is not provisioning, and it is not remediation. It establishes visibility before governance can be enforced. Mature programs combine directory data, browser telemetry, endpoint signals, CI/CD records, and cloud logs to reveal identities that central teams may never have issued directly. That visibility is essential when trying to align with NIST Cybersecurity Framework 2.0 functions for identifying and protecting critical identity assets.
For NHI Management Group, discovery is a prerequisite for lifecycle control because an identity cannot be rotated, offboarded, or restricted if it is not known to exist. The most common misapplication is treating discovery as a one-time scan, which occurs when teams assume directories alone contain the full set of active agents and credentials.
Examples and Use Cases
Implementing discovery rigorously often introduces operational overhead, requiring organisations to weigh broader visibility against data collection, normalization, and privacy controls.
- A security team correlates browser telemetry and cloud audit logs to find an AI agent that authenticates through a hidden API key rather than a managed workload identity.
- An engineering group discovers service accounts in CI/CD pipelines by comparing repository secrets references against actual runtime authentication events, then feeds the results into the NHI Lifecycle Management Guide.
- A governance team finds orphaned certificates on device fleets after merger integration, showing that identity exposure is wider than the original IAM directory.
- A cloud operations team uses the discovery output to prioritize the most exposed identities, following patterns highlighted in the Top 10 NHI Issues.
- A third-party review uncovers NHIs authenticating from partner-managed systems, then maps them to trust boundaries described in the Ultimate Guide to NHIs — Key Challenges and Risks.
In practice, discovery is most valuable when it identifies not just identities, but the access paths and blind spots that normal inventory processes miss.
Why It Matters in NHI Security
Discovery matters because NHI risk scales in places that traditional IAM often fails to see. NHI Mgmt Group reports that only 5.7% of organisations have full visibility into their service accounts, which means most environments cannot reliably answer a basic question: what machine identities are active right now?
That visibility gap leads directly to excess privilege, stale credentials, and unmanaged agent behavior. It also weakens Zero Trust and lifecycle controls because teams cannot scope policy to identities they have not found. Discovery is therefore the bridge between telemetry and governance: it turns scattered signals into an enforceable inventory that can be reviewed, reduced, and monitored over time. It also helps security leaders align with identity governance principles in NIST Cybersecurity Framework 2.0 and related access control practices.
Organisations typically encounter the business impact of discovery only after a breach, audit failure, or cloud migration reveals an unknown agent, at which point discovery becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 | Discovery is the first step in identifying unmanaged non-human identities and their exposure. |
| NIST CSF 2.0 | ID.AM | Asset management requires identifying identity assets and their supporting telemetry sources. |
| NIST Zero Trust (SP 800-207) | Zero Trust depends on discovering identity sources before policy can be enforced. | |
| NIST AI RMF | GV-2 | AI risk governance requires visibility into agents operating across the environment. |
| OWASP Agentic AI Top 10 | A1 | Agentic systems create hidden identities that must be found before they are secured. |
Discover all identities and trust relationships so policy decisions can be scoped correctly.