Azure Blob Container Access Level Modification

Last updated 24 days ago on 2025-09-30

Created 5 years ago on 2020-08-20

About

Identifies changes to container access levels in Azure. Anonymous public read access to containers and blobs in Azure is a way to share data broadly, but can present a security risk if access to sensitive data is not managed judiciously.

Tags

Domain: CloudData Source: AzureUse Case: Asset VisibilityTactic: DiscoveryLanguage: kuery

Severity

low

Risk Score

MITRE ATT&CK™

Discovery (TA0007)(opens in a new tab or window)

↳ Cloud Storage Object Discovery (T1619)(opens in a new tab or window)

Defense Evasion (TA0005)(opens in a new tab or window)

↳ File and Directory Permissions Modification (T1222)(opens in a new tab or window)

Exfiltration (TA0010)(opens in a new tab or window)

↳ Transfer Data to Cloud Account (T1537)(opens in a new tab or window)

False Positive Examples

Access level modifications may be done by a system or network administrator. Verify whether the username, hostname, and/or resource name should be making changes in your environment. Access level modifications from unfamiliar users or hosts should be investigated. If known behavior is causing false positives, it can be exempted from the rule.

License

Elastic License v2(opens in a new tab or window)

Definition

Rule Type: Query (Kibana Query Language)
Integration Pack: Prebuilt Security Detection Rules
Index Patterns: logs-azure.activitylogs-*filebeat-*
Related Integrations: azure(opens in a new tab or window)
Query

event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.STORAGE/STORAGEACCOUNTS/BLOBSERVICES/CONTAINERS/WRITE" and event.outcome:(Success or success)

Install detection rules in Elastic Security

Detect Azure Blob Container Access Level Modification in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).