> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/modules/secure/security-posture/audit-legacy.md).

# Audit (Legacy)

{% hint style="warning" %}
This is the legacy version of Security Posture auditing, shown with a "Legacy" badge in the app menu. It's being phased out in favor of [Compliance Audit](/modules/secure/security-posture/compliance-audit.md), which replaces its single fixed checklist with swappable assessments (multiple compliance frameworks, or a custom checklist) and generally covers the same checks with more flexibility. If you're setting up Security Posture for the first time, use Compliance Audit instead — this page exists for accounts still using the legacy flow.
{% endhint %}

The legacy Audit tool checks a connected tenant against a single, fixed set of security checks — MFA enforcement, legacy authentication, sign-in risk policies, mailbox auditing, sharing restrictions, and more — and scores overall compliance. Like Compliance Audit, it's split into an **Audit** tab (see what's failing) and a **Protect** tab (fix it), and it can be paired with [Posture Templates](/modules/secure/security-posture/posture-templates.md) for bulk remediation.

## Customizing the checklist

Not every check applies to every client. The legacy Audit tool lets you customize which checks count toward a tenant's score by marking specific checks as **ignored** for that tenant — for example, if a client intentionally allows a configuration that the default checklist flags. Ignored checks are excluded from that tenant's compliance score and from the Audit results view, but you can un-ignore them at any time.

{% hint style="info" %}
Ignoring a check here is separate from ignoring a *user* elsewhere in Augmentt — this only affects which security checks apply to a tenant, not which accounts are monitored. See [ignored users](/getting-started/the-10-step-setup-guide/step-4.-assigning-augmentt-licenses.md#what-gets-licensed-automatically) if that's what you're looking for.
{% endhint %}

## Security Posture Report

The Security Posture Report gives you a client-ready summary of a tenant's audit results — its overall compliance score, a breakdown by category, and the individual checks driving the score up or down. It's built for sharing with a client or using in a QBR, rather than for the day-to-day work of fixing checks (that's what the Audit and Protect tabs are for).

{% hint style="info" %}
This is a first-pass overview of the legacy Audit tool. We'll break out a more detailed per-check reference as a follow-up, mirroring what Compliance Audit will get.
{% endhint %}


---

# 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://helpdesk.augmentt.com/modules/secure/security-posture/audit-legacy.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.