Skip to content

Commit 2ea7240

Browse files
authored
Update support matrix for Defender for Storage
Added note about AWS S3 bucket support and permissions for Defender for Storage.
1 parent 99b8f09 commit 2ea7240

1 file changed

Lines changed: 3 additions & 0 deletions

File tree

articles/defender-for-cloud/support-matrix-defender-for-storage.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,9 @@ This article lists the prerequisites and permissions required to [enable Microso
2828

2929
- Storage accounts that belong to a resource group with any of the following names are not supported: `App_Browsers`, `App_Code`, `App_Data`, `App_GlobalResources`, `App_LocalResources`, `App_Themes`, `App_WebReferences`, `Bin`.
3030

31+
> [!NOTE]
32+
> AWS S3 buckets are not directly supported by Defender for Storage. You can use Microsoft Sentinel with the AWs S3 connector to consume AWS GaurdDuty findings and display them within the Defender portal **Alerts** table. [Learn more in Sentinel data connectors)](/azure/sentinel/data-connectors-reference#sentinel-data-connectors).
33+
3134
## Permissions
3235

3336
Depending on the scenario, you need different levels of permissions to enable Defender for Storage and its features. You can enable and configure Defender for Storage at the subscription level or at the storage account level. You can also use built-in Azure policies to enable Defender for Storage and enforce its enablement on a desired scope.

0 commit comments

Comments
 (0)