# At least one Microsoft Defender for Cloud Apps anomaly detection policy is generating alerts

Microsoft Defender for Cloud Apps includes anomaly detection policies that baseline each user's behavior and surface deviations such as impossible travel…

Source: https://maester.dev/docs/tests/ZTA.41081

<!-- This file is generated by website/scripts/generate-test-docs.mjs. Do not edit manually. -->

## Overview

Microsoft Defender for Cloud Apps includes anomaly detection policies that baseline each user's behavior and surface deviations such as impossible travel, activity from an infrequent country, activity performed by a terminated user, and unusual file download, share, or delete volume. When no anomaly detection policy is producing alerts, a threat actor who compromises a credential and exfiltrates from a software-as-a-service app operates in the same telemetry surface as the legitimate user, and the security team has no signal that the behavior is anomalous. This check confirms that anomaly detection is active and producing alerts so credential-based attacks against cloud apps surface in the incident queue rather than completing silently.

## Remediation

- [Get behavioral analytics and anomaly detection](https://learn.microsoft.com/en-us/defender-cloud-apps/anomaly-detection-policy)
- [Tune anomaly detection policies](https://learn.microsoft.com/en-us/defender-cloud-apps/anomaly-detection-policy#tune-anomaly-detection-policies)
- [Connect apps to get visibility and control](https://learn.microsoft.com/en-us/defender-cloud-apps/enable-instant-visibility-protection-and-governance-actions-for-your-apps)
- [Best practices for protecting your organization with Microsoft Defender for Cloud Apps](https://learn.microsoft.com/en-us/defender-cloud-apps/best-practices)

## Run it

The check runs as part of the whole assessment, with the ZeroTrustAssessment module installed:

```powershell
Install-Module ZeroTrustAssessment -Scope CurrentUser
Connect-Maester
Invoke-Maester -Pack ZTA -SkipBuiltIn
```

Leave out `-SkipBuiltIn` to run Maester's own checks in the same run.

<details>
<summary>About this check</summary>

| | |
| --- | --- |
| Severity | High |
| Effort to fix | Low |
| Impact on users | Low |
| Pillar | SecOps |
| Category | SaaS threat detection |
| Product | [Defender](/docs/tests/products/defender) |
| Feature | Tenant settings |
| Area | Logging and detection |
| ATT&CK | [T1078.004](/docs/tests?mitre=T1078.004) Cloud Accounts |
| Licence | ADALLOM_S_STANDALONE, ADALLOM_S_O365 |
| Tenant | Workforce |

Product, feature, area and ATT&CK are Maester's: the assessment does not record them, so Maester keeps them in the pack's `taxonomy.json`.

</details>

<p class="mt-ms-note not-content"><svg class="mt-ms-note__logo" viewBox="0 0 21 21" aria-hidden="true"><rect width="10" height="10" fill="#f25022"/><rect x="11" width="10" height="10" fill="#7fba00"/><rect y="11" width="10" height="10" fill="#00a4ef"/><rect x="11" y="11" width="10" height="10" fill="#ffb900"/></svg><span>A Microsoft check, part of the <a href="/docs/tests/packs/zero-trust-assessment">Zero Trust Assessment</a> pack. Text from ZeroTrustAssessment 3.1.0, © Microsoft, <a href="/docs/tests/packs/zero-trust-assessment#licence">MIT licence</a>.</span></p>
