AboutWhat's newContact & demo
Control Assurance & Security ReviewsAvailable now

Govern the identities nobody owns.

Service accounts, app registrations, managed identities and API keys now outnumber people. Give each one an owner, an explainable risk rating, live policy checks and a certification cycle.

Illustration with sample data

Overview

What NHI & NHA Governance does

NHI & NHA Governance keeps a register of non-human identities and accounts. They are discovered from Microsoft Entra ID and enriched by Azure, received from user access reviews, or added manually. Each record captures business and technical owners, purpose, account type, technology, relationships to cloud resources and review status.

Risk is computed from named, weighted conditions covering ownership, credential status, privilege, dormancy and certification, with the reasoning recorded. Policy-as-Code results for each identity show live checks such as expiring secrets. Periodic reviews end in certification, certification with remediation, or unable to certify, and remediation tasks are created from the record. Secret values are never stored, only metadata.

Abstract cybersecurity lighting on circuitry
Capabilities

Key capabilities

01

Automatic discovery

Service principals, app registrations and managed identities from Entra ID and Azure.

02

From access reviews

Service accounts found in a UAR are sent straight in.

03

Explainable risk scoring

Weighted conditions with reasoning captured.

04

Policy-as-Code results

Live rule results per identity, such as secret expiry.

05

Periodic certification

Certified, certified with remediation, or unable to certify.

06

Secrets never stored

Only metadata is kept, never credential values.

Benefits

The business case.

Efficiency, multi-framework alignment, reduced complexity and streamlined processes: what NHI & NHA Governance changes for your programme.

Risk reduction
Privilege creep contained

Dormant & orphaned NHIs

Ownership and dormancy conditions surface the riskiest machine identities.

Achieving compliance
ISO A.5.16–A.5.18, PCI 8.6

Service-account controls

Evidence that system and application accounts are managed and reviewed.

Potential savings
>70%

Less manual inventory work

Discovery replaces spreadsheets of service accounts.

Streamlined processes
Workflow built in

Review → certify → remediate

One record carries the full lifecycle.

Efficiency figures compare the effort of each workflow cycle in RiskVantis with the same work done manually or in a traditional GRC tool. Your result depends on your starting point; we will model it with you in a demo.

How it works

From setup to outcome.

Discover

Connect Entra ID and Azure, or receive accounts from a UAR.

Assign owners

Business and technical ownership for each identity.

Assess risk

Weighted conditions and policy checks produce an explainable rating.

Certify

Periodic reviews and remediation tasks.

Framework alignment

Supports your obligations.

NHI & NHA Governance contributes evidence and coverage to these frameworks and regulations.

ISO/IEC 27001:2022 (A.5.16–A.5.18, A.8.2)PCI DSS v4.0.1 (8.6)NIST CSF 2.0 (PR.AA)SOC 2 (CC6.1)

All supported frameworks

FAQ

Common questions.

Which identities are discovered automatically?

Service principals, app registrations and managed identities from Microsoft Entra ID, enriched with Azure role assignments and resource associations.

Does RiskVantis store secrets?

No. Only metadata is stored; credential and secret values are never kept.

How is risk calculated?

From named, weighted conditions covering ownership, credential status, privilege, dormancy and review status, with the reasoning recorded.

See NHI & NHA Governance in action.

Book a 30-minute walkthrough tailored to your frameworks, vendors and team.