> 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/compliance-audit.md). # Compliance Audit Compliance Audit is where you check a tenant's Microsoft 365 configuration against a security checklist, see exactly what's failing, and fix it — either one setting at a time or as a bulk remediation. It's organized into three tabs: **Audit**, **Protect**, and **Assessments**. ## Assessments: choosing what you audit against An assessment is the checklist Compliance Audit measures a tenant against. Before you can see results on the Audit tab, the tenant needs at least one assessment assigned to it. Augmentt ships a set of ready-made **Default assessments** you can assign as-is, including: * CIS Microsoft 365 Foundations Benchmark (multiple versions) * CIS Controls v8 * CMMC Level 1 and Level 2 * HIPAA Security Rule * NIST CSF 2.0 * Essential 8, at Maturity Levels 1 through 3 * Augmentt Quick Baseline — a short, opinionated starting checklist if you don't need a full compliance framework Individual checks are also tagged against recognized frameworks (for example CISA's SCuBA baselines) so results can be reported in those terms even when the framework itself isn't one of the top-level Default assessments above. If none of the defaults fit, you can build a **custom assessment** by picking exactly the checks you want included — useful when a client only cares about a subset of controls, or when you want to combine checks from more than one framework into one checklist. {% hint style="info" %} An assessment tells Compliance Audit *what to measure*. It doesn't fix anything by itself — for that, see [Posture Templates](/modules/secure/security-posture/posture-templates.md). {% endhint %} ## Audit: seeing what's failing The **Audit** tab runs the tenant's assigned assessment(s) and shows every check with a pass/fail (compliant/non-compliant) status, grouped by category. At the top, the **Show** row has two special cards — **All posture checks** (the full catalog, regardless of which assessment they belong to) and **All saved assessments** (previously saved assessment-run snapshots) — followed by a scrollable row of cards, one per assessment assigned to the tenant. Each assessment card shows its own check count, overall compliance percentage, and a Compliant/Partial/Non-compliant/Resolved/Other breakdown with a colored progress bar; clicking one filters the table below to just that assessment. A **Status** bar underneath totals whatever's currently selected. The check table always shows **Security Check** (the check's name) and **Status** (a compliance badge: Compliant, Partially Compliant with a percentage, or Non-compliant). Everything else is optional — a column-picker icon above the table lets you toggle on the columns you want to see: * **Status Details** — a plain-language explanation of the result (for example, "You have 17 of 71 privileged accounts that don't use MFA") * **Categories** — the check's category (Identity, Exchange, SharePoint, and so on) * **Portal** — which admin portal the setting lives in * **Rationale** — why the check matters from a security standpoint * **Assessments** — every assessment this check belongs to, shown as pills. A widely-applicable check like Admin MFA can appear under most or all of them at once * **M365 License Req.** — the minimum Microsoft 365 license the check needs to evaluate or remediate * **Secure Score** — the check's contribution to Microsoft Secure Score, where applicable * **Notes** — any notes your team has added on this check for this tenant Selecting a check opens its detail panel, with up to five tabs: **Overview**, **Details**, **Configure**, **Instructions**, and **Notes**. The Overview tab is the richest — it repeats the check's current Status and Status Details, then its category, rationale, Secure Score impact, and which assessments it belongs to, and finally a **Compliance** section listing the specific compliance-framework control(s) it maps to (for example "CIS M365 V6 (L1) — 5.2.2.1"), each with that framework's own title and description. Details shows the specific tenant data the check evaluated (which users, which settings), and Notes holds any notes your team has added for this tenant. Configure and Instructions are mutually exclusive per check, not both-and: a check Augmentt can remediate directly shows a **Configure** tab with the control to change the setting from right there; a check that requires a manual change in Microsoft 365 (or another admin center) — or is purely informational — shows an **Instructions** tab with step-by-step guidance instead. Which one you get depends entirely on the check; there's no way to tell in advance from the table alone. ## Protect: fixing what's failing The **Protect** tab is the remediation side of the same checklist. Instead of working through checks one at a time, you pick a [Posture Template](/modules/secure/security-posture/posture-templates.md) from the dropdown at the top — the template's target settings are compared against the tenant's current configuration, and every check where they differ appears in the list below with its **Current Status** and what it would **Change to** if applied. Check the box next to any checks you want to include (or use **Configure all** to select everything with a pending change), then apply — Augmentt pushes the target configuration for just the checks you selected. As on the Audit tab, this only works for checks Augmentt can remediate directly; checks that require a manual change still need their Instructions tab on the Audit side. ## Assessments vs. Posture Templates It's easy to conflate these two, since both revolve around a checklist of security settings: * An **assessment** (this page) defines what you *audit against* — it's the scorecard. * A [**Posture Template**](/modules/secure/security-posture/posture-templates.md) is what you *remediate with* — a reusable bundle of target settings you can push to a tenant. Short version: audit with an assessment, remediate with a template. Templates aren't tied to Compliance Audit specifically — they also work with the legacy [Audit](/modules/secure/security-posture/audit-legacy.md) tool. {% hint style="info" %} This is a first-pass overview of Compliance Audit. A full per-check reference (what each individual check verifies and how to remediate it manually) will be broken out into its own guide. {% 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/compliance-audit.md?ask=&goal= ``` `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.