Azure Storage unusual spike in destructive operations

Esta página aún no está disponible en español. Estamos trabajando en su traducción.
Si tienes alguna pregunta o comentario sobre nuestro actual proyecto de traducción, no dudes en ponerte en contacto con nosotros.

Goal

Detect an unusual spike in destructive operations against Azure Storage resources.

Strategy

This rule monitors Azure Storage logs for anomalous levels of deletion events including MICROSOFT.STORAGE/STORAGEACCOUNTS/DELETE, DeleteContainer, and DeleteBlob operations with a successful outcome. A spike significantly above baseline may indicate a compromised account performing mass data destruction, which is a common pattern in cloud ransomware attacks.

Triage and response

  • Review the volume and scope of deletion operations performed from`{{@network.client.ip}}` to assess the extent of potential data loss.
  • Examine what specific storage accounts, containers, or blobs were targeted to understand the blast radius.
  • Check for other suspicious activity from the same user.
  • If the activity is not authorized, begin your organization’s incident response plan.