Google Cloud BigQuery - query results saved to new table

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

Goal

Detect when an attempt to export Google Cloud BigQuery results to a new table occurs.

Strategy

This rule monitors Google Cloud Audit Logs to determine when an attempt to export Google Cloud BigQuery results to a new table has occurred. An attacker who has already gained initial access may try to exfiltrate data by saving BigQuery results to a new table outside of the compromised organization.

Notes:

  • This rule triggers with a Low severity when this activity originates from an anonymizing proxy.

Triage and response

  1. Reach out to the user or owner of the service account to determine if this action is legitimate.
  2. If the action is legitimate, consider including the IP address or ASN in a suppression list. See this article on Best practices for creating detection rules with Datadog Cloud SIEM for more information.
  3. Otherwise, use the Cloud SIEM - IP Investigation dashboard to see if the IP address: {{@network.client.ip}} has taken other actions.
  4. If the results of the triage indicate that an attacker has taken the action, begin your company’s incident response process and investigate.

Changelog

  • 31 Jaunuary 2023 - Updated strategy in markdown and rule title.
  • 25 September 2024 - Updated query to replace attribute @threat_intel.results.category:anonymizer
PREVIEWING: esther/docs-9518-update-example-control-sensitive-log-data