> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/core-concepts/posture-and-anomalies.md).

# 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](/core-concepts/orphans.md).
* **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](/core-concepts/philosophy.md)).

## 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](/core-concepts/audit-and-compliance.md), mirroring how [orphans](/core-concepts/orphans.md) 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.aohwv.dev/core-concepts/posture-and-anomalies.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.