For the complete documentation index, see llms.txt. This page is also available as Markdown.

Posture and Anomalies

Two ways AOH Sync answers "is anything wrong?": one broad and continuous, one specific and event-driven.

Posture

Posture is a tenant's overall identity health, a composite score from 0.0 to 1.0 computed as a point-in-time snapshot. It rolls up component measures including:

  • Orphan density - how many accounts cannot be tied to a person. See Orphans.

  • Stale account density - accounts lingering without recent activity.

  • Excess access - access beyond what a person's role appears to need.

  • Unassigned groups - groups with no clear ownership or assignment.

The value of a single score is trend: 0.7 is not meaningful in isolation, but a drift from 0.85 to 0.7 over a month signals slipping hygiene.

Insufficient data

If a tenant's graph has no users and no groups, AOH Sync marks posture as insufficient data rather than inventing a score. Risk is measured, not guessed (see philosophy).

Anomalies

Anomaly detection flags specific abnormal events. AOH Sync watches for patterns such as:

  • Unusual sign-in behavior.

  • Permission acceleration: access growing faster or more broadly than expected.

  • Vault-related anomalies around secret access.

Each anomaly carries a severity: low, medium, high, or critical. Severity indicates urgency, not certainty; some abnormal events are legitimate.

Acknowledgement

An anomaly can be acknowledged by an admin: a recorded decision logged in the audit trail, mirroring how orphans handle dismissal. An anomaly is either open or acknowledged, and both states are attributable.

How the two work together

Posture tells you the environment is degrading; anomalies tell you which events to look at. A rising count of high-severity sign-in anomalies and a falling posture score are two views of the same problem.

Last updated