Skip to content

Commit

Permalink
Update Articles “how-to-secure-your-blob-storage-container”
Browse files Browse the repository at this point in the history
  • Loading branch information
ser1aa authored Dec 16, 2024
1 parent 9adec34 commit 4ee4772
Showing 1 changed file with 0 additions and 4 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -118,12 +118,8 @@ By analyzing logs, you can determine how and when the container was misconfigure

Implement strict naming conventions for Blob Storage containers that do not directly relate to the company or the type of data stored, making them difficult for attackers to predict.

{{< callout type="info" >}}

According to [Wizardcyber](https://wizardcyber.com/azure-blob-storage-navigating-misconfiguration-risks/), cybercriminals often aim to uncover two key pieces of information to exploit Blob Storage: the names of the container and its corresponding storage account. When anonymous access is set to the container level, it becomes possible for an attacker to enumerate, or list, all the blobs within a container.

{{< /callout >}}

### 9. Contact Grayhatwarfare for deletion

Contact [G](https://buckets.grayhatwarfare.com/)[rayhatwarfare](https://buckets.grayhatwarfare.com/) for the deletion of your information. Grayhatwarfare is an online tool and database designed to index publicly exposed cloud storage buckets, including misconfigured Azure Blob Storage containers, Amazon S3 buckets, and Google Cloud Storage. It could be that we've found your misconfigured containers here.
Expand Down

0 comments on commit 4ee4772

Please sign in to comment.