Azure Container Registry Created or Deleted
Detects when a Container Registry is created or deleted.
Sigma rule (View on GitHub)
1title: Azure Container Registry Created or Deleted
2id: 93e0ef48-37c8-49ed-a02c-038aab23628e
3status: test
4description: Detects when a Container Registry is created or deleted.
5references:
6 - https://learn.microsoft.com/en-us/azure/role-based-access-control/resource-provider-operations#microsoftkubernetes
7 - https://www.microsoft.com/security/blog/2021/03/23/secure-containerized-environments-with-updated-threat-matrix-for-kubernetes/
8 - https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/
9 - https://medium.com/mitre-engenuity/att-ck-for-containers-now-available-4c2359654bf1
10author: Austin Songer @austinsonger
11date: 2021-08-07
12modified: 2022-08-23
13tags:
14 - attack.impact
15 - attack.t1485
16 - attack.t1496
17 - attack.t1489
18logsource:
19 product: azure
20 service: activitylogs
21detection:
22 selection:
23 operationName:
24 - MICROSOFT.CONTAINERREGISTRY/REGISTRIES/WRITE
25 - MICROSOFT.CONTAINERREGISTRY/REGISTRIES/DELETE
26 condition: selection
27falsepositives:
28 - Container Registry being created or deleted may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
29 - Container Registry created or deleted from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
30level: low
References
Related rules
- Azure Kubernetes Cluster Created or Deleted
- Azure Kubernetes Network Policy Change
- Azure Kubernetes RoleBinding/ClusterRoleBinding Modified and Deleted
- Azure Kubernetes Secret or Config Object Access
- Azure Kubernetes Sensitive Role Access