PIVTR-D
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

LogSearch for
Audit, Cloud Guard and Security ZonesChanges 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 HubLogs, log groups, agent configurations and connectors turned off or deleted: UpdateLog, DeleteLog, DeleteLogGroup, DeleteUnifiedAgentConfiguration, DeactivateServiceConnector, UpdateServiceConnector, DeleteServiceConnector
Audit, Events and quotasEvents rules and quotas deleted or changed: DeleteRule, UpdateRule, DeleteQuota, RemoveQuotaLock
Current state, Cloud GuardThe status of the Cloud Guard configuration: oci cloud-guard configuration get -c <tenancy-ocid>
Current state, logsThe is-enabled value of each log in the group: oci logging log list --log-group-id <ocid>
Current state, connectorsConnectors that are inactive: oci sch service-connector list -c <compartment-ocid> --lifecycle-state INACTIVE

Contain

#Item
1Re-enable Cloud Guard: oci cloud-guard configuration update -c <tenancy-ocid> --reporting-region <region> --status ENABLED
2Re-enable each log: oci logging log update --log-group-id <ocid> --log-id <ocid> --is-enabled true
3Reactivate each connector: oci sch service-connector activate --service-connector-id <ocid>
4Block the identity that made the changes, as in credential leak or account takeover

Eradicate and recover

#Item
1Restore targets, detector rules and responder recipes to baseline
2Put removed compartments back in their Security Zones and recreate deleted Events rules
3Rebuild the gap from Audit, which records API calls on its own, and from flow logs that stayed on
4Record the gap in coverage for each log and tell the Incident Commander what it rules out
5Limit who can manage Cloud Guard, log groups, connectors and Events rules to a security group
Watch out
  • UpdateConfiguration is the event name in more than one service, including Cloud Guard and Audit. Read the event type to 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.

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.