> 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/discover/discover-compliance.md).

# Discover Compliance

Discover Compliance layers regulatory and security-posture context onto the applications your customers are actually using, so you can strengthen your CSRA (Cyber Security Risk Assessment) reports and give customers a clearer picture of whether the SaaS apps in their environment meet their compliance needs.

Find it at **Discover > Discover Compliance**.

## What the report checks

For each discovered application, the Compliance report shows support/coverage for:

* **SSO** (Single Sign-On)
* **MFA** (Multi-Factor Authentication)
* **HIPAA**
* **CCPA**
* **ISO 27001**
* **SOC 2**
* **PCI**
* **SOX**
* **FedRAMP**

It also surfaces the **latest known breaches** for each application, with reference material, going back to January 2024.

## The applications list

Applications are listed with:

| Column           | Description                                   |
| ---------------- | --------------------------------------------- |
| Application Name | The app                                       |
| Category         | Its classification                            |
| Approval Status  | Approved / Restricted / Pending Review        |
| SSO Support      | Whether the app supports SSO                  |
| MFA Support      | Whether the app supports MFA                  |
| Compliance       | Which frameworks the app supports/aligns with |
| Latest Breach    | Most recent known breach, if any              |
| Users count      | How many employees are using it               |

## How this fits into your reporting

Discover Compliance is meant to be pulled directly into the risk conversation you're already having with customers — pairing "here's what's actually in use" (from Application Usage and the App Catalog) with "here's whether it meets your compliance bar" in one view, rather than needing a separate manual audit.

## Helping improve the compliance data

Compliance and breach data for thousands of SaaS applications is maintained by Augmentt's analyst team, and it's community-sourced in part: if you spot compliance data that's incomplete, incorrect, or missing for an application, send documentation for that app's actual compliance posture to **<support@augmentt.com>**. Augmentt's analysts prioritize these updates for the benefit of the whole partner community — so a correction you report can end up helping every MSP using Discover, not just your account.

{% hint style="info" %}
Because compliance and breach data is maintained by Augmentt's analyst team rather than pulled live from each vendor, expect some lag between a real-world event (a new breach disclosure, a vendor achieving a new certification) and it reflecting in this report. If a customer needs authoritative, real-time compliance status for a specific vendor for an audit, treat this report as a strong starting point rather than the final source of truth, and verify against the vendor's own documentation.
{% endhint %}

{% hint style="warning" %}
Not independently verified this session (codebase access was unavailable): the exact scope/cadence of how frequently the underlying compliance and breach dataset is refreshed. If a partner asks for a specific refresh SLA, check with support rather than assuming a fixed cadence.
{% 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/discover/discover-compliance.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.