Before you run
Data & scope
- Required tables
- Time window
- 24 hours
- Azure Blob resource logs exported in resource-specific mode to StorageBlobLogs, including the categories needed by this hunt.
- Query access and 24 hours of retained Blob logs for each investigated account; Azure Activity alone does not record blob requests.
Documentation review by Codex (AI). No live-tenant execution or detection-performance claim. Validate schema, data coverage and expected results in your workspace.
// Hunting starter. Documentation checked 2026-11-13; not tenant-tested.
StorageBlobLogs
| where TimeGenerated >= ago(1d) and TimeGenerated <= now()
| where AuthenticationType =~ "Anonymous"
| extend HttpCode = toint(StatusCode),
SafeObjectPath = tostring(split(Uri, "?")[0])
| summarize ObservedRequests = count(),
SuccessfulRequests = countif(HttpCode between (200 .. 299)),
DeniedRequests = countif(HttpCode in (401, 403)),
OtherStatusRequests = countif(isnull(HttpCode)
or (HttpCode !between (200 .. 299) and HttpCode !in (401, 403))),
SuccessfulGetRequests = countif(OperationName =~ "GetBlob" and HttpCode between (200 .. 299)),
ObservedGetResponseBytes = sum(iff(OperationName =~ "GetBlob" and HttpCode between (200 .. 299),
ResponseBodySize, long(null))),
MissingGetResponseSizes = countif(OperationName =~ "GetBlob"
and HttpCode between (200 .. 299) and isnull(ResponseBodySize)),
Operations = make_set(OperationName, 10), Statuses = make_set(StatusCode, 10),
ObjectSamples = make_set(SafeObjectPath, 5),
FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated)
by AccountResource = _ResourceId, AccountName, CallerIpAddress
| order by SuccessfulGetRequests desc, ObservedRequests desc, LastSeen desc
| take 200
Read-only query. Run in your own authorized workspace after checking prerequisites.
Run this inventory when validating a storage exposure change or investigating a public URL associated with an AI knowledge source. It selects requests recorded as Anonymous and reports their outcomes separately. An anonymous request that receives a denial is evidence of a request, not evidence that blob content was disclosed.
Interpret access and response size
SuccessfulRequests includes all selected operations with HTTP 2xx status. SuccessfulGetRequests narrows that population to GetBlob. A successful metadata or listing operation is different from a successful content retrieval, so retain the operation samples during triage.
ObservedGetResponseBytes sums available response-body sizes for successful GetBlob requests. Missing sizes are counted separately. A zero or small total should not be interpreted as proof of no exposure, and repeated or partial reads do not equal unique bytes of business information. The request address includes its port in this schema; do not treat every address/port combination as a distinct person. Blob log fields.
The output strips URI query strings before keeping object samples. Paths can still contain sensitive project or document names, so restrict access to exported investigation results. This sanitization is not a general guarantee that every path is safe to publish.
Check the effective exposure
Verify both the account-level anonymous-access setting and the affected container’s configuration. Microsoft describes these as separate controls: allowing anonymous access at account level does not itself make every container public. Anonymous-access configuration.
Compare successful reads with intended public content, approved static assets and the classification of the specific objects. For a retrieval corpus, determine whether the source was meant for authenticated indexing only. Preserve the exposure interval and affected paths before changing configuration, then verify the resulting denial using an approved nonsensitive object.
Denied traffic can come from old links, broken clients, search crawlers or opportunistic probing. It may remain visible after remediation and should not automatically be treated as failed remediation.
Tune and validate
Validate one intended public read, one rejected anonymous request and one authenticated request that should be excluded. Compare the resulting status groups and response-size completeness. Avoid retrieving sensitive content simply to prove that a URL works.
The hunt scans 24 hours and returns up to 200 account/address groups. It cannot reconstruct requests that were not logged and does not inspect object content. It is documentation-checked and has not been executed in a tenant.
Verify the source
Microsoft references
Measure normal activity, validate known test cases, account for ingestion delays, choose a threshold and entity mapping, and assign an owner. Results require investigation.
Follow the detection learning path →