Data exposed by a vendor or product bug
A code or configuration change shows one customer's data to another, and no attacker is involved. Either a vendor tells you your data reached its other customers, or your own multi-tenant product on AWS returns one tenant's records to another. Roll back the change first, and save the deploy records and access logs that show who saw what.
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
| Log | Search for |
|---|---|
| Vendor notice | What the vendor owes you in writing: the exposure window, your records involved, the customers who could see them, and the root cause |
| AWS Health, your account health | Notices from AWS about your account. The API needs Business Support+, Enterprise Support or Unified Operations, and the console view needs only sign-in: aws health describe-events --region us-east-1 --filter "eventTypeCategories=accountNotification,eventStatusCodes=open" |
| Deploy records | The deploy that made the change: CloudTrail CreateDeployment, UpdateService, UpdateFunctionCode20150331v2 and UpdateAlias20150331 in the window. Revision, creator and times of a CodeDeploy deployment: aws deploy get-deployment --deployment-id <id> |
| CloudTrail data events, DynamoDB (off by default) | Reads of tenant tables by principal, if a trail logs AWS::DynamoDB::Table: GetItem, Query, Scan, BatchGetItem |
| CloudTrail data events, S3 (off by default) | Reads of tenant prefixes by principal and time: GetObject |
| ALB access logs (off by default) | Requests in the window by path and client. Delivery is best effort, every 5 minutes per node |
| Application logs in CloudWatch Logs | The caller's tenant ID next to the tenant ID of each record returned, if the application logs both |
| AWS operator access | Access by AWS staff, which AWS documentation describes no customer-facing log for. Ask in the Support case. For EC2, the Nitro System has no mechanism for any person to log in to Nitro hosts or reach instance memory, encrypted instance storage or encrypted EBS data |
Contain
| # | Item |
|---|---|
| 1 | On the vendor side, open a case with the vendor, ask whether the flaw is fixed, and ask for the list of records and recipients. For AWS, open an AWS Support case |
| 2 | Stop a CodeDeploy rollout and roll back the instances it updated: aws deploy stop-deployment --deployment-id <id> --auto-rollback-enabled |
| 3 | Roll back an ECS service to the known-good task definition: aws ecs update-service --cluster <cluster> --service <service> --task-definition <family>:<known-good-revision> |
| 4 | Point a Lambda alias back at the known-good version: aws lambda update-alias --function-name <function> --name <alias> --function-version <known-good> |
| 5 | Revert an AppConfig change: aws appconfig stop-deployment --application-id <app> --environment-id <env> --deployment-number <n> --allow-revert |
| 6 | Export application and access logs for the window, as in Evidence: aws logs create-export-task --log-group-name <group> --from <ms> --to <ms> --destination <evidence-bucket> |
| 7 | Save the build, commit and deploy records of the bad change with the case |
Eradicate and recover
| # | Item |
|---|---|
| 1 | Restore the tenant filter in code, and add a test that fails when a data query lacks the tenant key |
| 2 | Remove other tenants' data written into each tenant's records, from backups taken before the deploy |
| 3 | Build the list of affected tenants and records from data events and application logs. Where data events were off, record that reads cannot be ruled out |
| 4 | Give the list to the Legal advisor for notification deadlines, on both sides of a vendor exposure |
| 5 | On the vendor side, rotate credentials and tokens the vendor kept for you, and review the vendor with Supply chain |
| 6 | Turn on data events for tenant tables and buckets, and ALB access logs, before the next release |
- AppConfig reverts a completed deployment only within 72 hours of completion. After that, deploy the previous configuration version as a new deployment.
- Without data events or access logs, CloudTrail shows the deploy and no reads. The list of exposed records then rests on application logs and the code path.
- CloudWatch Logs runs one export task per account at a time. Queue the largest log groups first.
AWS documentation: AWS Health API and Health Dashboard, CLI health describe-events; CodeDeploy stop-deployment and get-deployment; ECS update-service; Lambda update-alias and CloudTrail event names; AppConfig stop-deployment; CloudWatch Logs create-export-task; DynamoDB CloudTrail data events; ALB access logs; Nitro System whitepaper, no AWS operator access. Vanta RCA of product bug Inc-868 (vanta.com/resources/rca-inc-868), checked October 2026. AWS Health API support plans and AppConfig stop-deployment checked October 2026; other topics checked September 2026.