Unusual Azure Activity Logs Event for a User
A machine learning job detected Azure Activity Logs activity that, while not inherently suspicious or abnormal, is sourcing from user context that does not normally use the event action. This can be the result of compromised credentials or keys as someone uses a valid account to persist, move laterally, or exfiltrate data.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2025/10/06"
3integration = ["azure"]
4maturity = "production"
5min_stack_comments = "New job added"
6min_stack_version = "9.3.0"
7updated_date = "2025/11/21"
8
9[rule]
10anomaly_threshold = 75
11author = ["Elastic"]
12description = """
13A machine learning job detected Azure Activity Logs activity that, while not inherently suspicious or abnormal, is sourcing from
14user context that does not normally use the event action. This can be the result of compromised credentials or keys as
15someone uses a valid account to persist, move laterally, or exfiltrate data.
16"""
17false_positives = [
18 """
19 New or unusual user event activity can be due to manual troubleshooting or reconfiguration; changes in cloud
20 automation scripts or workflows; adoption of new services; or changes in the way services are used.
21 """,
22]
23from = "now-2h"
24interval = "15m"
25license = "Elastic License v2"
26machine_learning_job_id = "azure_activitylogs_rare_event_action_for_a_username"
27name = "Unusual Azure Activity Logs Event for a User"
28setup = """## Setup
29
30This rule requires the installation of associated Machine Learning jobs, as well as data coming in from Azure Activity Logs.
31
32### Anomaly Detection Setup
33
34Once the rule is enabled, the associated Machine Learning job will start automatically. You can view the Machine Learning job linked under the "Definition" panel of the detection rule. If the job does not start due to an error, the issue must be resolved for the job to commence successfully. For more details on setting up anomaly detection jobs, refer to the [helper guide](https://www.elastic.co/guide/en/kibana/current/xpack-ml-anomalies.html).
35
36### Azure Activity Logs Integration Setup
37The Azure Activity Logs integration allows you to collect logs and metrics from Azure with Elastic Agent.
38
39#### The following steps should be executed in order to add the Elastic Agent System integration "Azure Activity Logs" to your system:
40- Go to the Kibana home page and click “Add integrations”.
41- In the query bar, search for “Azure Activity Logs” and select the integration to see more details about it.
42- Click “Add Azure Activity Logs”.
43- Configure the integration.
44- Click “Save and Continue”.
45- For more details on the integration refer to the [helper guide](https://www.elastic.co/docs/reference/integrations/azure/activitylogs).
46"""
47references = ["https://www.elastic.co/guide/en/security/current/prebuilt-ml-jobs.html"]
48risk_score = 21
49rule_id = "81892f44-4946-4b27-95d3-1d8929b114a7"
50severity = "low"
51tags = [
52 "Domain: Cloud",
53 "Data Source: Azure",
54 "Data Source: Azure Activity Logs",
55 "Rule Type: ML",
56 "Rule Type: Machine Learning",
57]
58type = "machine_learning"
59
60[[rule.threat]]
61framework = "MITRE ATT&CK"
62
63[rule.threat.tactic]
64id = "TA0001"
65name = "Initial Access"
66reference = "https://attack.mitre.org/tactics/TA0001/"
67
68[[rule.threat.technique]]
69id = "T1078"
70name = "Valid Accounts"
71reference = "https://attack.mitre.org/techniques/T1078/"
72
73[[rule.threat.technique.subtechnique]]
74id = "T1078.004"
75name = "Cloud Accounts"
76reference = "https://attack.mitre.org/techniques/T1078/004/"
77
78[[rule.threat]]
79framework = "MITRE ATT&CK"
80
81[rule.threat.tactic]
82id = "TA0008"
83name = "Lateral Movement"
84reference = "https://attack.mitre.org/tactics/TA0008/"
85
86[[rule.threat.technique]]
87id = "T1021"
88name = "Remote Services"
89reference = "https://attack.mitre.org/techniques/T1021/"
90
91[[rule.threat.technique.subtechnique]]
92id = "T1021.007"
93name = "Cloud Services"
94reference = "https://attack.mitre.org/techniques/T1021/007/"
95
96[[rule.threat]]
97framework = "MITRE ATT&CK"
98
99[rule.threat.tactic]
100id = "TA0003"
101name = "Persistence"
102reference = "https://attack.mitre.org/tactics/TA0003/"
103
104[[rule.threat]]
105framework = "MITRE ATT&CK"
106
107[rule.threat.tactic]
108id = "TA0010"
109name = "Exfiltration"
110reference = "https://attack.mitre.org/tactics/TA0010/"
111
112[[rule.threat.technique]]
113id = "T1041"
114name = "Exfiltration Over C2 Channel"
115reference = "https://attack.mitre.org/techniques/T1041/"
References
Related rules
- Rare Azure Activity Logs Event Failures
- Spike in Azure Activity Logs Failed Messages
- Unusual City for an Azure Activity Logs Event
- Unusual Country for an Azure Activity Logs Event
- Rare GCP Audit Failure Event Code