QuestionQ120

Detection engineering

A Google Security Operations (SecOps) detection rule is producing frequent false-positive alerts. The rule was created to detect suspicious Cloud Storage enumeration by alerting whenever the storage.objects.list API operation is invoked through the api.operation UDM field. However, a legitimate backup automation tool uses the same API, which causes the rule to fire unnecessarily. You need to reduce these false positives from this trusted backup tool while continuing to detect potentially malicious use. How should you change the rule to improve its accuracy?

  • A Add principal.user.email != "[email protected]" to the rule condition to exclude the automation account.
  • B Replace api.operation with api.service_name = "storage.googleapis.com" to narrow the detection scope.
  • C Convert the rule into a multi-event rule that looks for repeated API calls across multiple buckets.
  • D Adjust the rule severity to LOW to deprioritize alerts from automation tools.
Explanation

Excluding the known trusted automation account from the operation-based condition suppresses its expected backup activity while retaining alerts for storage.objects.list calls made by every other principal. Cloud Audit Logs map the authenticated principal email into a principal user email UDM field, so an actor-specific exclusion is an appropriate way to tune a false-positive-prone detection.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!