You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/users-groups-roles/directory-emergency-access.md
+63-2Lines changed: 63 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,10 +64,71 @@ Organizations need to ensure that the credentials for emergency access accounts
64
64
65
65
If using passwords, make sure the accounts have strong passwords that do not expire the password. Ideally, the passwords should be at least 16 characters long and randomly generated.
66
66
67
+
## Monitor sign-in and audit log alerts
67
68
68
-
## Monitor sign-in and audit logs
69
+
Organizations need to monitor activity from these accounts and trigger notifications to other Administrators. When you monitor the activity on break glass accounts, you can verify these accounts are only used for testing or actual emergencies. Azure Log Analytics can monitor the sign-in logs and trigger email and SMS alerts to your admins whenever break glass accounts sign-in.
69
70
70
-
Monitor the [Azure AD sign-in and audit logs](../reports-monitoring/concept-sign-ins.md) for any sign-ins and audit activity from the emergency access accounts. Normally, these accounts should not be signing in and should not be making changes, so use of them is likely to be anomalous and require security investigation.
71
+
### Prerequisites
72
+
73
+
1.[Send Azure AD sign-in logs](https://docs.microsoft.com/azure/active-directory/reports-monitoring/howto-integrate-activity-logs-with-log-analytics) to Azure Monitor.
74
+
75
+
### Obtain Object IDs of the break glass accounts
76
+
77
+
1. Sign in to the [Azure portal](https://portal.azure.com) with an account assigned to the User administrator role.
78
+
1. Select **Azure Active Directory** > **Users**.
79
+
1. Search for the break glass account and select the user’s name.
80
+
1. Copy and save the Object ID attribute so that you can use it later.
81
+
1. Repeat previous steps for second break glass account.
82
+
83
+
### Create an alert rule
84
+
85
+
1. Sign in to the [Azure portal](https://portal.azure.com) with an account assigned to the XXXX role.
86
+
1. Select **All services**", enter "log analytics" and select **Log Analytics workspaces**.
87
+
1. Select a workspace.
88
+
1. In your workspace, select **Alerts** > **New alert rule**.
89
+
1. Under **Resource**, verify that the subscription is the one with which you want to associate the alert rule.
90
+
1. Under **Condition**, select **Add**.
91
+
1. Select **Custom log search** under **Signal name**.
92
+
1. Under **Search query**, enter the following query, inserting the object IDs of the two break glass accounts.
93
+
> [!NOTE]
94
+
> For each additional break glass account you want to include, add another "or UserId == "ObjectGuid"" to the query.
95
+
96
+

97
+
98
+
1. Under **Alert logic**, enter the following:
99
+
100
+
- Based on: Number of results
101
+
- Operator: Greater than
102
+
- Threshold value: 0
103
+
104
+
1. Under **Evaluated based on**, select the **Period (in minutes)** for how long you want the query to run, and the **Frequency (in minutes)** for how often you want the query to run. The frequency should be less than or equal to the period.
1. Select **Done**. You may now view the estimated monthly cost of this alert.
109
+
1. Select an action group of users to be notified by the alert. If you want to create one, see [Create an action group](#create-an-action-group).
110
+
1. To customize the email notification sent to the members of the action group, select actions under **Customize Actions**.
111
+
1. Under **Alert Details**, specify the alert rule name and add an optional description.
112
+
1. Set the **Severity level** of the event. We recommend that you set it to **Critical(Sev 0)**.
113
+
1. Under **Enable rule upon creation**, leave it set as **yes**.
114
+
1. To turn off alerts for a while, select the **Suppress Alerts** check box and enter the wait duration before alerting again, and then select **Save**.
115
+
1. Click **Create alert rule**.
116
+
117
+
### Create an action group
118
+
119
+
1. Select **create an action group**.
120
+
121
+

122
+
123
+
1. Enter the action group name and a short name.
124
+
1. Verify the subscription and resource group.
125
+
1. Under action type, select **Email/SMS/Push/Voice**.
126
+
1. Enter an action name such as **Notify global admin**.
127
+
1. Select the **Action Type** as **Email/SMS/Push/Voice**.
128
+
1. Select the notification methods you want to configure and enter the required contact information. For example, you could email to a distribution list of Global Admins, Security Admins, and Privileged Role Admins.
129
+
1. Select **Ok**.
130
+
1. Add any additional Actions you want to trigger.
0 commit comments