What was exposed
A public data exposure / Microsoft
- 1
Business records are reachable without authentication
By September 24, 2022SOCRadar identified publicly accessible Azure Blob Storage. Microsoft confirmed that a misconfigured endpoint permitted unauthenticated access to business transaction data.
- 2
Files describe prospective and existing business
September 2022The records included business contact details and correspondence. Microsoft said attachments might have been present and cautioned that repeated records inflated the researcher’s count.
- 3
Microsoft secures the endpoint
September–October 2022Microsoft required authentication after SOCRadar notified it. It began sending customer notifications on October 4.
Impact
Microsoft confirmed that business transaction records could be read without authentication. It found no indication of compromised customer accounts or systems.
Could this have been prevented?
Require authorization for business records in Blob Storage
If your containers can require authentication, disable anonymous access on the account’s ordinary Blob service endpoints. An enabled static website endpoint can still serve public content, and signed links can still authorize reads. Microsoft did not identify the original access grant.
Incident control assessments
- 0
- Prevented
- 2
- Contained
- 1
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
A public data exposure / Microsoft
1 · Business records are reachable without authentication
1 Contained2 · Files describe prospective and existing business
1 Contained3 · Microsoft secures the endpoint
1 Not coveredKey facts
- SOCRadar reported the endpoint to Microsoft on September 24, 2022. Microsoft secured it and required authentication.
- In its October 19, 2022 report, SOCRadar estimated 2.4 TB at this Microsoft endpoint and attributed records to more than 65,000 entities. Microsoft disputed the population estimate and did not publish a replacement count.
- SOCRadar’s October 19, 2022 report covered six large public buckets in the wider BlueBleed investigation. Its combined figures cannot be assigned to the Microsoft endpoint.
- Microsoft began notifying affected customers on October 4. Its October 28 FAQ said the endpoint did not grant access to customer tenants, subscriptions or production cloud services.
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Investigation Regarding Misconfigured Microsoft Storage LocationMicrosoft Security Response Center · Oct 19, 2022 · Vendor reportBusiness records, access change, duplicate records and customer notifications
- 2.Sensitive Data of 65,000+ Entities in 111 Countries Leaked due to a Single Misconfigured Data BucketSOCRadar · Oct 19, 2022 · ResearchAzure Blob Storage identification, research estimate and distinction from the six-bucket BlueBleed investigation
The estate in the replay is illustrative and drawn at the level of the exposure; the owner's real environment is not public. Verdicts describe what a control does when it is in place before the data is exposed. They are not an assessment of the owner's security program.