GCP Cloud Audit Logs can be used to identify resource deletion events. These logs contain the account that performed the action (within the Principal field), a timestamp, and more detailed information depending on what resource was deleted. Some query examples include; resource.type="gcs_bucket" and protoPayload.methodName="storage.buckets.delete" for bucket deletion and resource.type="gce_instance" and protoPayload.methodName="v1.compute.instances.delete" for computer instance deletion.

Sections

ID	Name	Description
IF014.005	Deletion of Cloud Resources	A subject deletes cloud resources, resulting in harm to the organization's operations.
AF018.002	Environment Tripwires	The subject develops a custom API that monitors specific activities, network traffic, and system changes within the target environment. The API could monitor HTTP/HTTPS requests directed at sensitive endpoints, track modifications to security group settings (such as firewalls or access policies), and identify administrative actions like changes to user accounts, data access requests, or logging configurations. This tripwire API is embedded within various parts of the environment: Cloud Services: It hooks into serverless functions, containers, or virtual machines to monitor access and activity. Applications: It integrates into custom-built web applications to observe access to certain URLs, paths, or endpoints. Infrastructure Services: It monitors cloud management APIs (e.g., AWS, Azure, Google Cloud) for unusual activities indicative of an investigation. Once deployed, the tripwire API continuously monitors network traffic, API calls, and system changes for indicators of an investigation. It looks for: Known Security Tools: Scanning for network traffic signatures from common security tools (like Nessus or nmap) or patterns associated with incident response teams. Unusual Access: Detecting attempts from IP ranges linked to internal security teams or cloud provider security operations centers. System Changes: Watching for actions typical of an investigation, such as new logging mechanisms, alterations to IAM roles, or the activation of cloud monitoring services. The API can use whitelists for expected IP addresses or user accounts, triggering alerts if unexpected access occurs. Upon detecting activity, the API tripwire can take immediate evasive actions: Alert the Subject: It sends covert alerts to an external server controlled by the subject, through an HTTP request, encrypted email, or messaging platform. Suspend Malicious Activity: If integrated into a malicious workflow, the API can halt ongoing data exfiltration or malware processes. Clean Up Evidence: It triggers scripts to delete logs, clear files, or reset system configurations to hinder forensic analysis. Feign Normalcy: It restores access controls and system settings to their default state, masking any signs of unusual activity.

References