Skip to content

New attack technique: Disable VPC Flow Logs on a Subnet (gcp.defense-evasion.remove-vpc-flow-logs)#794

Merged
christophetd merged 3 commits intomainfrom
simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs
Apr 8, 2026
Merged

New attack technique: Disable VPC Flow Logs on a Subnet (gcp.defense-evasion.remove-vpc-flow-logs)#794
christophetd merged 3 commits intomainfrom
simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs

Conversation

@Minosity-VR
Copy link
Copy Markdown
Collaborator

What does this PR do?

New attack technique: gcp.defense-evasion.remove-vpc-flow-logs

Motivation

GCP parity with existing AWS attack techniques.

Test results

  • stratus detonate gcp.defense-evasion.remove-vpc-flow-logs
  • v1.compute.subnetworks.patch appears in GCP Admin Activity audit logs (no audit log observed — may require non-default DATA_WRITE audit config)

Checklist

  • The attack technique emulates a single attack step, not a full attack chain
  • We have factual evidence & references that the attack technique was used by real malware, pentesters, or attackers
  • The attack technique makes no assumption about the state of the environment prior to warming it up

@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-project-from-organization branch from b50e60b to bab7a4c Compare March 30, 2026 14:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch from 7d31013 to 52d7f70 Compare March 30, 2026 14:53
@Minosity-VR Minosity-VR marked this pull request as ready for review April 1, 2026 07:24
@Minosity-VR Minosity-VR requested review from a team as code owners April 1, 2026 07:24
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-project-from-organization branch from bab7a4c to cf57c77 Compare April 1, 2026 08:28
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch from 52d7f70 to cb89728 Compare April 1, 2026 08:28
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-project-from-organization branch from cf57c77 to 160d7a2 Compare April 1, 2026 08:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch from cb89728 to ebe092e Compare April 1, 2026 08:53
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-project-from-organization branch from 160d7a2 to b2b868a Compare April 1, 2026 09:03
@Minosity-VR Minosity-VR force-pushed the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch from ebe092e to 9ed6f7f Compare April 1, 2026 09:03
@christophetd christophetd force-pushed the simon.marechal/gcp-defense-evasion-remove-project-from-organization branch from c7f3f03 to fc6b129 Compare April 8, 2026 09:42
Base automatically changed from simon.marechal/gcp-defense-evasion-remove-project-from-organization to main April 8, 2026 09:54
Minosity-VR and others added 3 commits April 8, 2026 11:54
…evasion.remove-vpc-flow-logs)

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>
@christophetd christophetd force-pushed the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch from 9ed6f7f to 0949c0a Compare April 8, 2026 09:55
Copy link
Copy Markdown
Contributor

@christophetd christophetd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good, tested it and working well too

@christophetd christophetd merged commit c5852c7 into main Apr 8, 2026
6 checks passed
@christophetd christophetd deleted the simon.marechal/gcp-defense-evasion-remove-vpc-flow-logs branch April 8, 2026 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants