huntrule

Google Cloud DLP Re-identifies Sensitive Data via projects.content.reidentify

Detects Google Cloud DLP re-identification activity using projects.content.reidentify in audit logs.

FreeReviewedSigma · Medium · v4
Product
gcp
Service
gcp.audit
Author
Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-08-15
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Impact

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags Google Cloud audit events where the DLP re-identification operation is invoked using projects.content.reidentify. Re-identification can expose sensitive information by transforming previously anonymized or de-identified data, making it a high-impact action in data handling workflows. It relies on GCP audit telemetry capturing the API method name for content re-identification requests.

Reporting behind it

Related detections2 linkedT1565 — drag to rearrange
PowerShell Add-DnsClientNrptRule Modifies NRPT Namespaces
AWS EC2: DisableEbsEncryptionByDefault API call to turn off default EBS encryption
Google Cloud DLP Re-identifies Sensitive Data via projects.content.reidentify
Pivot detection · T1565 · 2 related

Changelog

v4
  1. v4
    Candidate ingested via manual entry.2026-07-31
  2. v3
    Candidate ingested via manual entry.2026-07-31
  3. v2
    Candidate ingested via manual entry.2026-07-31
  4. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.