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
- Audit records every supported API call, reads included, for 365 days. The period cannot be changed.
- principalId names who called. An instance acting as itself shows its own OCID.
- A user can have three API keys, two auth tokens, two secret keys, and two SMTP credentials. Deleting one ends it at once.
- Terminating from the CLI deletes the boot volume unless you pass --preserve-boot-volume true.
- Boot volume backups are crash-consistent while the instance runs.
Commands
| Audit events for a day | oci audit event list --compartment-id <ocid> --start-time <from> --end-time <to> |
| A user's API keys | oci iam user api-key list --user-id <ocid> |
| Back up a boot volume | oci bv boot-volume-backup create --boot-volume-id <ocid> --type FULL |
| Clone it for analysis | oci 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.