PIVTR-D
ROracle Cloud playbook · Provider and accidental

Data exposed by a vendor or product bug

A code or configuration change shows one customer's data to another with no attacker involved, either at a vendor, Oracle included, or in your own multi-tenant product on OCI. 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. Preserve the deploy records and logs first, then roll back or block the leaking route.

Look here

LogSearch for
Console Announcements (vendor side)Notices from Oracle about issues specific to your tenancy. Oracle sends them as Console Announcements and emails the tenancy administrator. Send them to a monitored Notifications topic with an announcement subscription: oci announce announcements list -c <tenancy-ocid> --all
Oracle operator accessCommands run by Oracle operators, for the services that log them. Operator Access Control logs operator commands for Exadata Cloud@Customer, Autonomous AI Database on Exadata Cloud@Customer and Compute Cloud@Customer in the operator control's compartment. Delegate Access Control covers ExaDB-D, ExaDB-XS and ExaDB-C@C: oci delegate-access-control delegated-resource-access-request list -c <compartment-ocid> --all
Object Storage read log (your product)Reads of objects under each tenant's prefix, by data.principalName, data.bucketName, data.objectName and data.clientIpAddress, if the log was enabled. Audit records bucket events only, never object reads
API Gateway access and execution logsRequests per tenant, as requestUri, remoteAddr and status in the access log. Authentication results are in the execution log
Load Balancer access logRequests to the leaking endpoint in the window, as request, clientAdd, forwardedForAddr and backendAddr
DevOps deploymentsThe deployment whose time matches the first bad response: oci devops deployment list -c <compartment-ocid> --pipeline-id <ocid> --all
Resource Manager jobsInfrastructure changes applied at the same time: oci resource-manager job list -c <compartment-ocid> --stack-id <ocid>
Application logsThe requesting tenant and the tenant of each record returned, in your own logs. Only these prove which records crossed

Contain

#Item
1Before any rollback, preserve the deployment record and an Audit export for the window, as in Evidence: oci devops deployment get --deployment-id <ocid> > deploy.json
2Preserve the Resource Manager job logs: oci resource-manager job get-job-logs-content --job-id <ocid>
3Redeploy the last good release, and confirm it uses the artifact versions of that release: oci devops deployment create-pipeline-redeployment --deployment-id <deploy-pipeline-ocid> --previous-deployment-id <last-good-deployment-ocid>
4If a rollback is not ready, turn off the feature or block the leaking route at API Gateway or with a WAF request access rule
5Enable Object Storage read and write logs and API Gateway access logs now where they were off
6For a vendor notice, record when it arrived. Ask the vendor in writing for the affected records, the window and the other customers' deletion of your data. For Oracle, open a support request from the Console Help menu
7Rotate any credential or token that appeared in the exposed data

Eradicate and recover

#Item
1Build the list of affected tenants and records from the logs above. Where a log was off, record that the exposure cannot be ruled out
2Remove data written to the wrong tenant and restore correct data from backups or previous object versions
3Give the list, the detection time and the vendor notice time to the Legal advisor for notification deadlines
4Add a cross-tenant test to the deployment pipeline that fails when a query returns another tenant's records
5Enforce tenant isolation below the application code, for example a bucket or prefix per tenant with policies that name it
6For a vendor, request the root cause analysis and review the vendor relationship as in supply chain
Watch out
  • Detection can trail the deploy by days. In Vanta's Inc-868 a customer reported the leak on May 26, Vanta reverted the change on May 27 and finished remediation on June 3, so start the log search at the deploy time.
  • A DevOps rerun lets the operator change parameters and artifacts. A redeployment that picks up the current artifact brings the bug back.
  • Operator Access Control and Delegate Access Control cover the listed Exadata and Cloud@Customer services. The documentation reviewed describes no customer-visible log of Oracle operator access for other services.
  • The Status dashboard shows region and service outages. A customer-specific issue arrives as a Console Announcement, so watch both.

Oracle documentation: Console Announcements, subscribing to announcements, Status service, overview of Operator Access Control, overview of Delegate Access Control, Audit overview, details for Object Storage logs, details for API Gateway logs, details for Load Balancer logs, rolling back a deployment, deployment rerun, adding a WAF request control rule, creating a support request; OCI CLI help for announce, delegate-access-control, devops deployment and resource-manager job. Vanta RCA of product bug Inc-868 (vanta.com/resources/rca-inc-868), checked October 2026. Checked September 2026. Rechecked October 2026: every command against OCI CLI 3.94.2, which lists a required pipeline ID for a pipeline redeployment.

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.