PIVTR-D
RCloud playbooks

Oracle Cloud playbooks

This page covers Oracle Cloud Infrastructure tenancies that use IAM with identity domains: the logs to keep, what to search, and the playbooks for 22 incident types in seven categories. Each playbook lists where to look and the commands to contain it. Commands use the OCI CLI, and queries run against the Audit service or Logging Search.

Playbooks

Identity and access

Stolen credentials, taken-over accounts and the access an attacker leaves behind.

Compute and containers

Workloads, servers and clusters used or abused by an attacker.

Data and storage

Exposed, copied, encrypted or deleted data, and stolen secrets.

Network and edge

Attacks on availability and on names and endpoints you own.

Pipelines and supply chain

Build systems and image registries that reach production.

Evasion and guardrails

Logging and controls turned off to hide an attack.

Provider and accidental

Incidents with no attacker: a vendor's bug, a provider's or operator's mistake, or a provider outage.

First 15 minutes, any incident

#Item
1Work from a break-glass administrator account in a group the suspect identity cannot modify
2Find the home region, the only region where users, groups, policies and dynamic groups change. Check is-home-region in the output of oci iam region-subscription list
3Export Audit for each compartment and subscribed region, as in Evidence: oci audit event list -c <compartment-ocid> --region <region> --start-time <utc> --end-time <utc> --all > audit-<region>.json
4Record who made the call that raised the alert, and from where: data.identity.principalName, principalId, credentials, ipAddress and userAgent
5Pull open Cloud Guard problems: oci cloud-guard problem list -c <tenancy-ocid> --compartment-id-in-subtree true --access-level ACCESSIBLE --lifecycle-detail OPEN
6Back up the boot volumes of involved instances before any isolation: oci bv boot-volume-backup create --boot-volume-id <ocid> --display-name <case-id>
7Allow about 15 minutes before treating a missing Audit event as absent

Native detections to playbooks

Cloud Guard problems map to the playbook to open first, using the detector rule names in the Oracle documentation. Kubernetes, instance principal misuse, resource hijacking, Generative AI abuse, Vault access, DDoS, dangling DNS, CI/CD abuse, registry tampering, cross-tenancy access and the provider and accidental playbooks have no dedicated rule in this table. Start from the log searches on their pages. A problem appears only after Cloud Guard is enabled with a target that covers the compartment.

DetectionSourceOpen
IAM API keys CreatedCloud Guard, activity detectorAPI key or auth token
IAM API keys CreatedCloud Guard, activity detectorUsers, keys, federation
IAM Auth Token CreatedCloud Guard, activity detectorAPI key or auth token
IAM Customer Keys createdCloud Guard, activity detectorAPI key or auth token
IAM OAuth 2.0 credentials createdCloud Guard, activity detectorUsers, keys, federation
IAM User createdCloud Guard, activity detectorUsers, keys, federation
User added to groupCloud Guard, activity detectorUsers, keys, federation
IAM User UI password created or resetCloud Guard, activity detectorIdentity domain user
Local user authenticated without MFACloud Guard, activity detectorIdentity domain user
Suspicious Ip ActivityCloud Guard, activity detectorIdentity domain user
Security policy modifiedCloud Guard, activity detectorTenancy administrator
IAM User capabilities modifiedCloud Guard, activity detectorTenancy administrator
Bastion session createdCloud Guard, activity detectorCompute instance
VCN Security List ingress rules changedCloud Guard, activity detectorCompute instance
VCN Network Security Group ingress rule changedCloud Guard, activity detectorCompute instance
Instance terminatedCloud Guard, activity detectorDeletion and ransomware
Database System terminatedCloud Guard, activity detectorDeletion and ransomware
Tenancy admin privilege granted to groupCloud Guard, configuration detectorTenancy administrator
Policy gives too many privilegesCloud Guard, configuration detectorTenancy administrator
User does not have MFA enabledCloud Guard, configuration detectorIdentity domain user
API key is too oldCloud Guard, configuration detectorAPI key or auth token
Bucket is publicCloud Guard, configuration detectorObject Storage
Read Log access disabled for bucketCloud Guard, configuration detectorCloud Guard, logs, Security Zones
Database System is publicly accessibleCloud Guard, configuration detectorDatabases and backups
Instance is publicly accessibleCloud Guard, configuration detectorCompute instance

Oracle documentation: Cloud Guard detector recipe reference (activity and configuration detector rules). Rule names are as published, and the recipe a rule belongs to can change with a Cloud Guard update, so check the names in your tenancy's recipes. Checked October 2026: all 24 rule names, including the two Storage rules in the configuration recipe. Read Log access disabled for bucket is off in the Oracle-managed configuration recipe and works only in a clone.

Before an incident

LogDefault retentionTurn on / keep
Audit service (API calls from the Console, CLI, SDKs and other services)365 days, set at tenancy level. The Audit configuration API accepts 90 to 365 days, so confirm the value with oci audit config get -c <tenancy-ocid>Nothing to turn on. Archive the _Audit logs to Object Storage with Connector Hub to keep more than a year
Identity domain events (sign-ins, MFA, user and group changes)Written to the Audit service, so 365 daysSearch them in Audit by data.additionalDetails.eventId. The identity domain AuditEvents API stopped returning new data after December 15, 2024
Object Storage service logs, categories read and writeOff until enabled. Once enabled, 30 days by default, up to 180 in 30-day stepsEnable both categories on every sensitive bucket. read covers GET, LIST and HEAD. write covers PUT, POST and DELETE
VCN flow logsOff until enabled. Stored in a Logging log group, 30 days by default, up to 180Enable at the VCN, subnet, VNIC or resource level. A capture filter can sample traffic, so check its sampling rate
Logging SearchEach query covers at most 14 daysUse oci audit event list for longer windows. Grant responders read log-groups, read log-content and AUDIT_EVENT_READ in advance
Cloud Guard problemsNone until Cloud Guard is enabledEnable Cloud Guard with a target on the root compartment. Clone the Oracle-managed configuration, activity and threat detector recipes so you can tune them. Enable Security Zones on sensitive compartments
Connector Hub archive in Object StorageSet by the target bucketAdd a retention rule to the archive bucket and keep it in a compartment the workload administrators cannot manage
Events rules with notificationsNo log. They alert on changes as they happenCreate rules for changes to IAM policies, users, groups, identity providers, and network gateways, security lists, NSGs, route tables and VCNs, as in the CIS OCI benchmark

Oracle documentation: Audit log retention period, contents of an Audit log event, Logging overview, Logging Search, enabling logging for a resource, details for Object Storage logs, VCN flow logs, identity domain audit event APIs, Cloud Guard concepts, Security Zones, CIS 1.2 controls. Checked September 2026. Rechecked October 2026: Logging Search (a 14-day range per query), viewing Audit log events (events usually appear within 15 minutes), and the Audit configuration and every command in OCI CLI 3.94.2; the Audit configuration model (retentionPeriodDays, minimum 90, maximum 365) and creating a log (retention in 30-day increments up to 180 days). The Audit log retention period page could not be opened in October 2026.

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.