Service accounts, AI agents, application identities and IoT devices share access models with humans โ and need the same ownership, review cadence, and revocation discipline. RapidValue applies a 4-tier governance model based on autonomy and blast radius.
What's inside
Not all NHIs are equal. A service account running a nightly backup needs different governance than an autonomous AI agent making customer-facing decisions. RapidValue's 4-tier model assigns review cadence, JIT requirements, and credential rotation policies based on tier.
The top-line metrics tell you what's at stake: total NHIs, the ratio of NHIs to humans (industry average is 25:1, often 40+), ownership coverage, stale credential count, and high/critical risk count. Below: the 4-tier breakdown and top 5 risk NHIs.
Service accounts & IoT devices โ low autonomy, reuse existing IGA flows. Governance: reuse IGA policy, manual approval, yearly review. Includes the bulk of legacy service accounts.
System accounts โ scoped, predictable permissions. Governance: scoped permissions, 2-year review, 90-day credential rotation. The traditional "one account per app" category.
AI agents โ autonomous decisions, require JIT + behaviour monitoring. Governance: JIT access, policy-as-code, behaviour monitoring, max-24h credentials. Modern AI deployment category.
Applications delegating to other agents โ federation + audit chain. Governance: agent identity federation, delegation tokens, audit chain. Multi-agent orchestration category.
Every NHI has an owner identity. Ownership transfers fire smart certs to the new owner. Orphaned NHIs (no owner) are surfaced as risk items. Owner is queryable, filterable, and reviewable like any other access decision.
T3 and T4 NHIs require Just-In-Time access elevation rather than standing privileges. Credential rotation policies enforce per-tier: T2 = 90-day, T3 = 24-hour, T4 = federation tokens (no long-lived secret to rotate).
The default cert-rule for NHIs (cr-nhi-ownership-yearly) reviews
T1-T4 NHI ownership every 180 days. Reviewer = manager (proxy for
NHI owner). Auto-action on deadline = flag-for-review (not revoke โ
NHIs shouldn't be silently disabled and break automation).
Per-NHI risk score combines: tier (higher = more weight), missing owner, credential age vs policy, unused activity window, and autonomous-without-JIT flag. Drives the "top 5 risk NHIs" surface on the dashboard.
Why NHIs need their own governance
Industry research puts NHI populations at 25โ60ร human users. Your IGA tool probably governs the humans well and largely ignores the rest. That's where the credential leaks live.
Recent EU breach reports attribute majority of root causes to leaked NHI credentials โ service account passwords in repos, API keys with no rotation, AI agent tokens with no scope. Govern them like humans.
New EU regulations require agent identity governance and demonstrable control over AI-to-system delegation. T3/T4 governance maps directly to these requirements.
NHIs live in the same Identity table as humans, with identity_type = service_account / ai_agent / application / system_account / iot_device. Same audit chain, same reconciliation, same export โ no separate tool.
Connect one target. Run NHI discovery. See your NHI-to-human ratio, your top risk NHIs, and which ones have no owner โ typically uncomfortable to look at the first time.
Book a POC demo โ