The attacker opens an Autonomous AI Database or a Base Database Service DB system to the internet through its access control list (ACL), private endpoint, network security group or security list. A typical run downloads a wallet, resets the ADMIN password, or clones the database or a backup into a compartment the attacker controls and exports it with Data Pump. Save the database's own audit trail first, because Autonomous AI Database purges it after 14 days, then close network access.
Look here
Log
Search for
Audit, Autonomous AI Database
Wallet downloads, network and password changes, clones, backups, restores and compartment moves: GenerateAutonomousDatabaseWallet, UpdateAutonomousDatabase (ACL, isMtlsConnectionRequired, private endpoint label, ADMIN password), CreateAutonomousDatabase (clones and restores to a new database), CreateAutonomousDatabaseBackup, RestoreAutonomousDatabase, ChangeAutonomousDatabaseCompartment
Events service, Autonomous AI Database (needs an Events rule)
Connections from an IP address not seen in 30 days (event name DatabaseConnection) and outbound traffic (NetworkUsageOutbound), under the type: com.oraclecloud.databaseservice.autonomous.database.information
Events service, wallet downloads
Wallet downloads, under the type: com.oraclecloud.databaseservice.generateautonomousdatabasewallet
Events service, ACL changes
Completed access control list changes, under the type: com.oraclecloud.databaseservice.updateautonomousdatabaseacl.end
Database unified audit, inside the database
Sign-ins, statements and exports by database user. Autonomous AI Database purges records older than 14 days once a day, so query it first: SELECT event_timestamp, dbusername, action_name, object_name, client_program_name FROM unified_audit_trail ORDER BY event_timestamp DESC
Data Safe, if the database is registered and audit trails are collected
Sign-in, administrator, entitlement and export activity in the reports Login Activity, Admin Activity, User/Entitlement Changes and Data Extraction Activity (Data Pump and RMAN)
Current state, network access
Changes to the network settings whitelisted-ips, is-mtls-connection-required, private-endpoint and nsg-ids: oci db autonomous-database get --autonomous-database-id <ocid>
Current state, clones
Clones of the database that no owner requested: oci db autonomous-database list-clones --autonomous-database-id <ocid> -c <compartment-ocid> --all
Current state, backups
Backups created in the window, including manual ones: oci db autonomous-database-backup list --autonomous-database-id <ocid> --all
Object Storage write log, if enabled
Dump files written by the database to your buckets. A Data Pump export to a bucket in another tenancy leaves no record in your Object Storage logs
Contain
#
Item
1
Save the unified audit trail and the oci db autonomous-database get output before you change anything. See Evidence
2
Restore the access control list to known sources. Setting --is-acl-enabled true with no entries blocks every client: oci db autonomous-database update --autonomous-database-id <ocid> --whitelisted-ips '["<cidr>","<vcn-ocid>"]'
3
Require mutual TLS, in a separate update: oci db autonomous-database update --autonomous-database-id <ocid> --is-mtls-connection-required true
4
Remove open ingress rules for the listener port from the DB system's network security group, and check the subnet's security lists as well: oci network nsg rules remove --nsg-id <ocid> --security-rule-ids '["<rule-id>"]'
5
Rotate the instance wallet at once. This ends user sessions and voids every downloaded instance wallet: oci db autonomous-database-wallet rotate --id <ocid> --should-rotate true
6
Reset the ADMIN password and the passwords of database users the attacker used: oci db autonomous-database update --autonomous-database-id <ocid> --admin-password <new>
After saving its details, terminate each clone or restored copy the attacker created destructive: oci db autonomous-database delete --autonomous-database-id <clone-ocid>
Eradicate and recover
#
Item
1
List every Autonomous AI Database and DB system in the tenancy and match each to an owner. Clones can sit in any compartment the attacker could write to
2
Remove unknown cross-region and cross-tenancy disaster recovery peers. List them with: oci db autonomous-database list-autonomous-database-peers --autonomous-database-id <ocid>
3
List the tables and schemas that were read or exported. Give the list to the Legal advisor for notification deadlines
4
Move production databases to private endpoints: oci db autonomous-database update --autonomous-database-id <ocid> --private-endpoint-label <label> --subnet-id <ocid> --nsg-ids '["<nsg-ocid>"]'
5
Register the database with Data Safe, start audit trail collection, and set online retention longer than 14 days
6
Grant AUTONOMOUS_DATABASE_CONTENT_READ (wallet download) and AUTONOMOUS_DATABASE_CREATE (clone) only to groups that need them
Watch out
OCI Audit records the control plane only. SQL sessions, queries and Data Pump jobs appear only in the database's own unified audit trail or in Data Safe, and Autonomous AI Database keeps its own trail for 14 days.
A wallet rotated with --grace-period keeps the old wallet valid for up to 72 hours. Rotate with no grace period during containment.
A clone has its own ADMIN password, access control list and wallet. Rotating the source database changes nothing on the clone.
Oracle documentation: Autonomous AI Database events, IAM policies for Autonomous AI Database, rotate wallets for Autonomous AI Database, audit Autonomous AI Database, Base Database Service IAM policy details, Core Services policy reference, Data Safe activity auditing overview, OCI CLI reference for db autonomous-database update, list-clones, list-autonomous-database-peers and delete, db autonomous-database-wallet rotate, db autonomous-database-backup list, db backup list and network nsg rules remove. Checked September 2026. Rechecked October 2026: the service name Autonomous AI Database on the Oracle documentation home page, and every command against OCI CLI 3.94.2.