ROracle Cloud playbook · Evasion and guardrails
Cloud Guard, logging or guardrails disabled
The attacker disables Cloud Guard or individual detector rules, turns off or deletes service logs, deactivates the connectors that ship logs out, deletes Events rules, or removes a compartment from a Security Zone. Turn the controls back on first, then record the gap in each log.
Look here
| Log | Search for |
|---|---|
| Audit, Cloud Guard and Security Zones | Changes to Cloud Guard, its targets, detector rules and responders, and to Security Zones: UpdateConfiguration, DeleteTarget, UpdateTarget, DeleteTargetDetectorRecipe, UpdateTargetDetectorRecipeDetectorRule, UpdateDetectorRecipeDetectorRule, UpdateResponderRecipe, RemoveCompartment, UpdateSecurityZone, DeleteSecurityZone |
| Audit, Logging and Connector Hub | Logs, log groups, agent configurations and connectors turned off or deleted: UpdateLog, DeleteLog, DeleteLogGroup, DeleteUnifiedAgentConfiguration, DeactivateServiceConnector, UpdateServiceConnector, DeleteServiceConnector |
| Audit, Events and quotas | Events rules and quotas deleted or changed: DeleteRule, UpdateRule, DeleteQuota, RemoveQuotaLock |
| Current state, Cloud Guard | The status of the Cloud Guard configuration: oci cloud-guard configuration get -c <tenancy-ocid> |
| Current state, logs | The is-enabled value of each log in the group: oci logging log list --log-group-id <ocid> |
| Current state, connectors | Connectors that are inactive: oci sch service-connector list -c <compartment-ocid> --lifecycle-state INACTIVE |
Contain
| # | Item |
|---|---|
| 1 | Re-enable Cloud Guard: oci cloud-guard configuration update -c <tenancy-ocid> --reporting-region <region> --status ENABLED |
| 2 | Re-enable each log: oci logging log update --log-group-id <ocid> --log-id <ocid> --is-enabled true |
| 3 | Reactivate each connector: oci sch service-connector activate --service-connector-id <ocid> |
| 4 | Block the identity that made the changes, as in credential leak or account takeover |
Eradicate and recover
| # | Item |
|---|---|
| 1 | Restore targets, detector rules and responder recipes to baseline |
| 2 | Put removed compartments back in their Security Zones and recreate deleted Events rules |
| 3 | Rebuild the gap from Audit, which records API calls on its own, and from flow logs that stayed on |
| 4 | Record the gap in coverage for each log and tell the Incident Commander what it rules out |
| 5 | Limit who can manage Cloud Guard, log groups, connectors and Events rules to a security group |
Watch out
UpdateConfigurationis the event name in more than one service, including Cloud Guard and Audit. Read the eventtypeto tell them apart.- Each Logging Search query spans at most 14 days. Run consecutive windows, or use
oci audit event list, for longer ranges.
OCI CLI 3.94.2 help for cloud-guard configuration, logging log and sch service-connector. Checked October 2026.