How CrowdStrike Detects Cloud Storage Misconfigurations to Protect Valuable Data

Cloud storage misconfigurations continue to become more prevalent and problematic for organizations as they expand their cloud infrastructure, driving the importance of technologies such as cloud security posture management (CSPM) as crucial tools for protectors everywhere. 

Consider the recently reported public exposure of data associated with some Microsoft customers and prospects. The data leak was publicly reported Oct. 19 by Microsoft and SOCRadar, whose security researchers discovered the leak and reported it to Microsoft on Sept. 24. Microsoft reconfigured the storage bucket, identified as Azure Blob Storage, “within several hours” of being notified, making it “no longer publicly accessible,” SOCRadar reported.

According to Microsoft, “The issue was caused by an unintentional misconfiguration on an endpoint that is not in use across the Microsoft ecosystem and was not the result of a security vulnerability” and there was “no indication customer accounts or systems were compromised.”

As organizations continue to adopt such cloud data storage services and expand their cloud infrastructure, the risk of misconfigurations is poised to grow — potentially leaving valuable resources exposed to threat actors. Here, we dive into this issue and discuss how CSPM can help. 

Cloud Storage Misconfigurations and the Growing Need for CSPM

Cloud-based data storage is a favorite target of threat actors who seek organizations’ valuable data to achieve their goals, whether they include espionage — an attempt to gather data about the target for use in future attacks — or monetary gain. While cloud service providers (CSPs) offer services to enable scalable data storage solutions and integrations with other services, the risk of exposing data to unauthorized parties through misconfiguration remains high. 

Azure Blob Storage is one example of such storage services which can, if desired, integrate with SQLServer by acting as a backup destination for databases. The service provides a number of configuration settings to increase the security posture of storage Blobs. As the recent report by SOCRadar suggests, organizations using these services would do well to ensure these configurations are consistently monitored and enforced in their environments. This can be difficult to achieve, however, particularly as environments scale and you begin adding complexity through integrations such as SQLServer backup, as in this reported instance. 

Here is where CrowdStrike can help. Read on to learn best practices as well as how CrowdStrike’s CSPM solution, Falcon Horizon™, enables CrowdStrike customers to monitor their storage configurations, quickly identify misconfigurations that can potentially be exploited, and prioritize remediation steps to keep data safe. 

First, we’ll overview the risk that misconfiguration poses to organizations.

How a Threat Actor Could Exploit Misconfigurations

Here, we describe a potential attack scenario involving the following components, all of which were factors in the recent scenario SOCRadar reported:

  1. Misconfigured, publicly accessible Azure bucket 
  2. SQL servers backed up in said Azure bucket  which contain unencrypted data at rest
  3. Additional Azure buckets accessed with information retrieved from SQL server backups

The following steps outline how a threat actor might exploit such a situation for malicious gain. It’s important to note this is a generalized and hypothetical scenario.

1. Recon: The first step in an attack exploiting these weaknesses is understanding the different levels of public accessibility. In the case of Azure Storage Blobs, anonymous public accessibility permissions can be granted at the container or the blob access level.

The container access level allows an anonymous client to make requests to containers enumerating the blobs they contain as well as to individual blobs, accessing their content or metadata. A threat actor only needs to know a storage account name and a container name to enumerate content within these blob storages. 

In contrast, the blob access level only allows requests to individual blobs for their content meaning a threat actor also needs to know the name of individual blobs ahead of time to access them. 

At this point a threat actor would likely perform some general reconnaissance on the target with the goal of defining wordlists containing likely names of storage accounts, containers and blobs. To discover targets of opportunity, threat actors might scan public DNS records to find active storage accounts, based on common naming conventions used for domains, such as <storage_account_name>

2. Enumeration: The second step is enumeration. Though this can be achieved by simply visiting the blob URLs directly in the Azure portal, we will walk through a programmatic method as enumeration is often scripted.

In a case where the access level is set to container, a threat actor can iterate through a wordlist of storage account names and container names making GET requests to the list blobs API that Microsoft provides for Azure. 


This request with the comp=list query parameter returns XML data that can be parsed to retrieve a list of Blobs within the container.

<?xml version="1.0" encoding="utf-8"?>
<EnumerationResults ContainerName="https://{storage_account_name}{container_name}">
				<Last-Modified>Mon, 31 Oct 2022 20:17:14 GMT</Last-Modified>
				<Content-Encoding />
				<Content-Language />
				<Cache-Control />
				<Last-Modified>Wed, 02 Nov 2022 17:21:08 GMT</Last-Modified>
				<Content-Encoding />
				<Content-Language />
				<Cache-Control />
	<NextMarker />

On the other hand, if the access level is blob, a threat actor would need a third wordlist containing possible blob names. They could then iterate through all three wordlists making HEAD requests to the get blob properties API.

curl -I

If the blob exists, this endpoint returns a status code of 200 and some HTTP headers containing blob metadata.

HTTP/1.1 200 OK
Content-Length: 0
Content-Type: text/plain
Content-MD5: 1B2M2Y8AsgTpgAmY7PhCfg==
Last-Modified: Wed, 02 Nov 2022 14:14:03 GMT
ETag: 0x8DABCDC7EC99D24
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: 22ce96f8-901e-0029-50c8-eede8a000000
x-ms-version: 2009-09-19
x-ms-lease-status: unlocked
x-ms-blob-type: BlockBlob
Date: Wed, 02 Nov 2022 14:35:38 GMT

If the blob doesn’t exist a status code of 404 is returned with the message “The specified blob does not exist.”

HTTP/1.1 404 The specified blob does not exist.
Transfer-Encoding: chunked
Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
x-ms-request-id: eb2b2339-801e-00a3-6ac8-ee853b000000
x-ms-version: 2009-09-19
Date: Wed, 02 Nov 2022 14:35:43 GMT

While more cumbersome, a threat actor could enumerate existing blobs by making these requests and recording those that return status codes of 200.

3. Data Exfiltration: Once the publicly accessible blobs are discovered and enumerated, they can be downloaded and their contents inspected via get blob requests.


The response body of this request will contain the contents of the blob.

4. Further Enumeration and Exfiltration: In this reported case the downloaded blobs contained unencrypted SQL Server backups. Database backups often contain sensitive information; if they are unencrypted, all it would take for the threat actor to access their data is the use of SQL statements to read and retrieve the stored information just as an authorized administrator or data owner would. Upon inspection of the backups, fields are discovered referencing further publicly accessible Azure Blob Storages that were unknown to the threat actor. At this point, the threat actor can repeat the enumeration and exfiltration of these newly discovered Azure Blobs which might contain further sensitive information.

CrowdStrike Best Practices for Configuring Azure Blob Storage

As a baseline for protection, CrowdStrike recommends implementing the following essential controls when using Azure Blob Storage services:

  • Apply access control lists (ACLs) to restrict access to files or directories in storage to certain security principals (users, groups or application service principals)
  • Apply storage networking firewalls to restrict access to only authorized IP spaces or virtual networks (never allow access from the entire public Internet unless that fits your intended use)
  • Apply authorization methods to restrict access to only authorized users or services, and refrain from enabling anonymous access unless that fits your intended use
  • Leverage encryption at rest and in transit to secure the data from unauthorized view

Note: Because threat actors who gain access to user accounts that can manage these settings may modify them to create exposures they can leverage externally, CrowdStrike also recommends you:

In its investigation, SOCRadar discovered additional publicly accessible Azure Blobs by analyzing some unencrypted SQLServer backups found in the initial blob. To prevent this from happening, CrowdStrike recommends not only ensuring your Azure Blob Storage configuration is secure but also securing the configuration of any services that interact with Azure Blob. As unencrypted SQLServer backups were relevant in this case CrowdStrike recommends the following:

Falcon Horizon Policies to Support Best Practice Configuration

Falcon Horizon CSPM can detect misconfigurations in storage accounts as well as Azure SQL services that would help protect customers from an attack like the one outlined above. Namely, Falcon Horizon can:

  • Alert on storage accounts that are set as publicly accessible
    • Allowing users to prevent public data exposure in storage blobs
  • Alert on storage accounts that are not encrypting data at rest via file service or blob service encryption
    • Allowing customers to ensure they are encrypting data at rest in storage
  • Alert on azure SQL databases that are not encrypting data via transparent data encryption
    • Allowing customers to ensure they are encrypting data within the database as well as within backups of the database. This way again, even if the backups are publicly accessible, threat actors would likely not be able to read them. It should be noted that whilst Azure SQL databases don’t back up to Azure Storage Blobs, SQL Servers running on-premises or in Azure VMs can and often do

The following table contains a current list of Falcon Horizon detection policies. These enable discovery of Azure Blob Storage configuration issues at scale that may allow remote threat actors to exploit related weaknesses. They are listed under two headings as Falcon Horizon has two types of detection policies: indicators of attack (IOAs), which are behavior-based detections (e.g., actions taken by a user), and indicators of misconfiguration (IOMs), which are misconfiguration based detections (e.g., static configuration settings of a service).

Policy Type Policy Severity Policy Name Policy Description
IOA Medium Storage Account Networking changed to All Networks A user has modified the storage account network rules to default “allow” access. This may indicate an attempt to allow unauthorized access in an attempt to steal data from the storage account.
IOM High Storage Account configured to allow access from all networks An Azure Storage Account was identified as being configured to allow access from all networks via network ACLs. This poses risk to the environment because malicious actors from any network may be able to access your storage account and its contents, potentially allowing an actor to abuse sensitive data.
IOM Critical Storage Account blob container configured with public access An Azure blob container was identified as being configured to allow access from the public internet. This poses risk to the environment because malicious actors from any network may be able to access your blob containers and their contents, potentially allowing an actor to abuse sensitive data.
IOM Informational SQL db has transparent data encryption disabled An Azure SQL server was identified as having transparent data encryption disabled. This means that data within that SQL database will not be encrypted at rest, and thus is vulnerable to malicious offline activity. Azure enables TDE by default on newer SQL databases, but must be manually enabled on older instances.
IOM Informational Storage Account configured with blob service encryption disabled An Azure Storage account was identified that has blob service encryption set to disabled. This means that data within that blob service will not be encrypted at rest, and thus is vulnerable to malicious offline activity.
IOM Informational Storage Account configured with file service encryption disabled An Azure Storage Account was identified as having file service encryption set to disabled. This means that data within that file service will not be encrypted at rest, and thus is vulnerable to malicious offline activity.
IOM High Storage Account has all blobs and containers set to allow public access An Azure Storage Account was identified as being configured to allow all blobs and containers access from the public internet. This poses risk to the environment because malicious actors from any network may be able to access your blobs and containers and their contents, potentially allowing an actor to abuse sensitive data.


Threat actors have proven to show a continued interest in gaining access to the information stored by cloud services. By leveraging security standards and monitoring solutions like those described above, protectors of this data can work to ensure it remains secure, to stop the breach from happening.

Additional Resources

Related Content