detection.wiki

Detection rules › Sigma

Azure Suppression Rule Created

Status
test
Severity
medium
Log source
product azure, service activitylogs
Author
Austin Songer
Source
github.com/SigmaHQ/sigma

Identifies when a suppression rule is created in Azure. Adversary's could attempt this to evade detection.

MITRE ATT&CK coverage

TacticTechniques
ImpactNo specific technique

Event coverage

ProviderEvent
Azure-Microsoft.SecurityMicrosoft.Security/alertsSuppressionRules/write

Rule body yaml

title: Azure Suppression Rule Created
id: 92cc3e5d-eb57-419d-8c16-5c63f325a401
status: test
description: Identifies when a suppression rule is created in Azure. Adversary's could attempt this to evade detection.
references:
    - https://learn.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations
author: Austin Songer
date: 2021-08-16
modified: 2022-08-23
tags:
    - attack.impact
logsource:
    product: azure
    service: activitylogs
detection:
    selection:
        operationName: MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE
    condition: selection
falsepositives:
    - Suppression Rule being created may be performed by a system administrator.
    - Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
    - Suppression Rule created from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
level: medium

Stages and Predicates

Stage 0: condition

selection

Stage 1: selection

selection:
    operationName: MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
operationNameeq
  • MICROSOFT.SECURITY/ALERTSSUPPRESSIONRULES/WRITE