PIVTR-D
RAzure playbook · Provider and accidental

Data exposed by a vendor or product bug

A code or configuration change at a vendor, Microsoft included, or in your own multi-tenant product on Azure shows one customer's records to another, with no attacker involved. Roll back the change and save the deployment records and request logs first. In Vanta's Inc-868, a performance change deployed May 22, 2025 removed a domain ID filter. Integration data of fewer than 4% of customers was written into other customers' tenants until Vanta reverted the change on May 27.

Look here

LogSearch for
Service Health, Security advisoriesMicrosoft's security notices about Azure services you use. Sensitive fields need Owner or Contributor on the subscription: az graph query -q "ServiceHealthResources | where type =~ 'Microsoft.ResourceHealth/events' | where properties.EventType == 'SecurityAdvisory' | project name, properties.Title, properties.TrackingId, properties.ImpactStartTime"
AzureActivity, Customer LockboxMicrosoft engineer access to your data on a support case. Tenant-scoped requests appear in the Entra audit log: Create Lockbox Request, Approve Lockbox Request, Deny Lockbox Request and Lockbox Request Expiry
Deployment recordsThe deployment that caused the exposure, then the pipeline run and commit behind it: az deployment group list --resource-group <rg>
Container Apps revisionsThe revision that shipped the change: az containerapp revision list --name <app> --resource-group <rg> --all -o table
AppServiceHTTPLogs, AppRequestsRequests per user and path in the window. Needs the App Service HTTP logs category or Application Insights. HTTP logs carry CsUsername, CsUriStem and CIp: AppRequests | where TimeGenerated between (datetime(<start>) .. datetime(<end>)) | summarize Requests=sum(ItemCount) by UserAuthenticatedId, Name, ResultCode
Data-plane logsWhich records each tenant read. Each log needs its diagnostic setting before the incident: blob reads in StorageBlobLogs, SQL batches in SQLSecurityAuditEvents and Cosmos DB requests in CDBDataPlaneRequests, as in blob exposure and database exposure
Vendor noticeThe vendor's list of your records exposed, the other customers who saw them, the exposure window, and whether the vendor has deleted the copies

Contain

#Item
1Save the bad deployment's record before it ages out, with the workspace query results, into case evidence: az deployment group show --resource-group <rg> --name <deployment>
2Save the deployment's template: az deployment group export --resource-group <rg> --name <deployment>
3Lock the Log Analytics workspace against deletion, as in the first 15 minutes
4Roll back App Service by swapping the same two slots again: az webapp deployment slot swap --resource-group <rg> --name <app> --slot staging --target-slot production
5Roll back Container Apps in multiple revision mode by sending all traffic to the last good revision: az containerapp ingress traffic set --name <app> --resource-group <rg> --revision-weight <good-revision>=100
6Deactivate the bad revision: az containerapp revision deactivate --revision <bad-revision> --resource-group <rg>
7Pause the pipeline that shipped the change until the fix has a test for tenant isolation
8For a vendor's exposure, rotate every credential or token the vendor kept for you, and ask the vendor in writing for its root cause analysis and deletion confirmation

Eradicate and recover

#Item
1Build the list of records, owners and viewing tenants from the request and data-plane logs, and give it to the Legal advisor for notification deadlines
2Remove data written into the wrong tenants, and keep a copy of each record removed as evidence
3Add the missing tenant filter back and a test that fails when one tenant's query returns another tenant's rows
4Create a Service Health alert for security advisories: az monitor activity-log alert create --name <name> --resource-group <rg> --condition category=ServiceHealth and properties.incidentType=Security --action-group <action-group-id>
5Turn on Customer Lockbox for Microsoft Azure (Global Administrator, Developer support plan or higher) so later Microsoft data access needs your approval
6Treat a vendor that exposed your data as a supplier incident, following the supply chain scenario
Watch out
  • Application Insights adaptive sampling is on by default in the ASP.NET, ASP.NET Core and Azure Functions SDKs. Sum ItemCount, and use data-plane logs to name exact records.
  • Resource Manager keeps up to 800 deployments per resource group and deletes the oldest once history passes 700. Export the records of the bad deployment on day one.
  • Customer Lockbox skips emergency access, inadvertent exposure during troubleshooting, and legal demands, so your logs never show those cases.

Vanta RCA of product bug Inc-868 (vanta.com/resources/rca-inc-868), checked October 2026. Microsoft Learn: Service Health notifications and impacted resources for security advisories, Resource Graph samples for Service Health, Customer Lockbox for Microsoft Azure, deployment history deletions, AppServiceHTTPLogs and AppRequests tables, Azure CLI reference for az deployment group, az containerapp, az webapp deployment slot and az monitor activity-log alert. Checked October 2026. App Service staging slots, Container Apps revisions and traffic splitting, and Application Insights sampling: checked September 2026.

Adapts material from Dynamic Incident Response: A Framework for Security Teams by Joshua Wright, © 2026 The Escal Institute of Advanced Technologies, Inc. d/b/a SANS Institute, licensed under CC BY 4.0. Figures reproduced under that license. Changes were made. Not published by, endorsed by, or affiliated with the SANS Institute.