iac.htora.dev · security templates

Home/Refreshers/Incident response on Oracle Cloud: refresher

Incident response on Oracle Cloud

What the Audit service records, how to read a principal, the credentials to revoke, and how to keep an instance's disks.

Remember

  1. Audit records every supported API call, reads included, for 365 days. The period cannot be changed.
  2. principalId names who called. An instance acting as itself shows its own OCID.
  3. A user can have three API keys, two auth tokens, two secret keys, and two SMTP credentials. Deleting one ends it at once.
  4. Terminating from the CLI deletes the boot volume unless you pass --preserve-boot-volume true.
  5. Boot volume backups are crash-consistent while the instance runs.

Commands

Audit events for a dayoci audit event list --compartment-id <ocid> --start-time <from> --end-time <to>
A user's API keysoci iam user api-key list --user-id <ocid>
Back up a boot volumeoci bv boot-volume-backup create --boot-volume-id <ocid> --type FULL
Clone it for analysisoci bv boot-volume create --source-boot-volume-id <ocid>

Watch out

  • A deactivated user's open console session stays open, with limited capabilities.
  • A dynamic group rule can match more instances than the one you meant.
  • Local NVMe drives are erased when the instance terminates.
Check it worked

A test API key added in a sandbox compartment appears in Audit with the user's name.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.