Who we protect
Govern people and machines without making them share an identity.
Explore this feature →AIdentity / Built-in agents & automation
Built-in agents. Continuous vigilance. Governed action.
AIdentity’s built-in specialist agents and analytics work with configured identity activity and scheduled checks to detect risk, prepare recommendations and carry out approved changes.
What this means for your team
- Monitor identity activity continuously and run scheduled role-mining and least-privilege analysis when the connected sources and background services are enabled.
- Bring behavioral signals and access evidence into a recommendation that an administrator can inspect, question and approve.
- Automate the work around a decision: gather context, prepare the proposal, route it to eligible reviewers and execute the approved response.
- Keep the decision separate from model confidence. A tenant can classify low-risk proposals as eligible for auto-approval, but the production apply path still holds them for an eligible person’s verified approval and authority. An auto-approval classification does not apply a change.
- Record the actual outcome and retain the proposal-to-decision-to-action trail. An unapplied or failed recommendation is not a completed remediation.
A practical example
An access analysis highlights permissions worth reviewing. AIdentity prepares an evidence-backed recommendation; an eligible administrator approves the response, and the system carries out and records the governed change.
How it works
Select a step to read its explanation
- Configured background analytics consume identity activity and run scheduled checks, without an administrator having to open a dashboard first.
- Collect the permitted identity and access evidence that supports an investigation. Keep the analysis within the relevant tenant and authority boundary.
- Prepare an understandable proposed response with its scope and risk. A model’s confidence cannot authorize a change.
- Send the proposal to an eligible administrator for the required decision. The proposing identity cannot approve its own request.
- Apply the approved change through its owner’s authorization controls and record the actual result. A refusal, outage or failure stays visible as such.
1 / 5
This example illustrates the journey. Select any step to explore it at your own pace.
Explore more AIdentity features
Authentication & MFA
Set the proof each sign-in or sensitive action must provide.
Explore this feature →RBAC, ABAC & ReBAC
Decide access using roles, attributes and relationships together.
Explore this feature →Identity lifecycle
Keep access aligned with joining, changing teams and leaving.
Explore this feature →Federation & applications
Connect applications and identity providers to a governed sign-in experience.
Explore this feature →Identity Graph
Understand who can reach a resource and which relationships give them access.
Explore this feature →Privileged roles (PIM)
Activate powerful roles for a bounded task rather than leaving them always on.
Explore this feature →Privileged access (PAM)
Govern access to privileged targets and credentials.
Explore this feature →Governance & approvals
Put reviews and independent decisions around sensitive access changes.
Explore this feature →Ask AIdentity
Ask questions about identity and access with authorization still enforced.
Explore this feature →Agent & device identity
Give agents and devices their own credentials, ownership and revocation path.
Explore this feature →Audit & privacy
Trace identity decisions while controlling access to sensitive evidence.
Explore this feature →