Skip to content
Avistar product reference

What is machine identity governance?

Machine identity governance establishes ownership, reviews access, prioritizes exposure, and keeps evidence current as cloud tenants change.

Read as plain text

What is a machine identity?

A machine identity authenticates software or infrastructure rather than a person. Examples include service accounts, cloud roles, access keys, API tokens, workload identities, and credentials used by AI agents. Nonhuman identity is another name for this category.

What needs to be governed?

Teams need to know which identities exist, who is accountable for them, which workload they serve, what access they hold, and whether that access is still needed.

  • Ownership and last observed activity
  • Privilege and reachable resources
  • Stale credentials and orphan candidates
  • Credential rotation and permission changes
  • Evidence for access reviews and remediation

Why a living inventory?

A point in time assessment helps teams establish an initial inventory. Ongoing discovery keeps that inventory useful as identities are created, become dormant, or gain access between reviews.

Where does an assessment fit?

The initial assessment scopes cloud tenants, discovers identities, scores risk, and prioritizes a remediation roadmap. It is an entry point to governance, not a substitute for continued review.

Sources