New attack technique: Delete All GCS Objects in Batch (gcp.impact.ransomware-gcs-batch-deletion)#804
Open
Minosity-VR wants to merge 3 commits into
Conversation
ce449a2 to
43077e4
Compare
1abe77e to
24d6c78
Compare
43077e4 to
9c7f9ff
Compare
24d6c78 to
cef4be3
Compare
9c7f9ff to
0575fcb
Compare
cef4be3 to
643d9d7
Compare
0575fcb to
0bd7fea
Compare
643d9d7 to
ebeb6e5
Compare
…somware-gcs-batch-deletion) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
0bd7fea to
4c60a98
Compare
ebeb6e5 to
18e15e7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a new GCP attack technique
gcp.impact.ransomware-gcs-batch-deletionthat simulates a ransomware attack by concurrently deleting all objects in a GCS bucket and uploading a ransom note.Motivation
GCP parity effort with existing AWS techniques (analogous to
aws.impact.s3-ransomware-batch-deletion).Checklist
Test results
storage.objects.delete) — there is no audit log emitted for GCS object deletions without non-default Data Access audit log configuration; a burst-based detection would yield too many false positives given typical GCS usage at scale