Lesson 66 — Investigating Privilege Escalation
Investigate how an identity or process may gain elevated permissions by correlating Windows group changes, privileged logons and Microsoft Entra role assignments in Microsoft Sentinel.

What you will learn
Follow the privilege change, identify the actor, and test whether elevated access was actually used.
Agent Foskett case file — The administrator nobody requested
A routine review identifies a new member of a privileged Windows group on a finance server. An Entra administrator role assignment appears in the same reporting period. Are these linked attacker actions, unrelated approved changes, or a misleading coincidence? Agent Foskett follows each audit trail before deciding whether escalation occurred.
Learning objectives
- Distinguish privilege escalation from ordinary privileged administration.
- Validate Windows Security and Microsoft Entra audit coverage.
- Hunt privileged group membership changes with KQL.
- Investigate Microsoft Entra directory role assignments.
- Correlate actor, target, time and subsequent privileged activity.
- Document alternative explanations, evidence gaps and escalation decisions.
What is privilege escalation?
Privilege escalation occurs when an actor obtains permissions beyond those previously available to them. It may involve local administrator rights, privileged domain groups, directory roles, token abuse or exploitation. A privileged event alone does not establish escalation: confirm the identity’s prior rights, the change mechanism and the resulting access.
Hypothesis and alternatives
Hypothesis: an unauthorized actor added an account to a privileged group and used the new access. Alternatives: approved change control, just-in-time access, automated identity governance, break-glass operations or legitimate server maintenance. Investigate both the authorization and any evidence of actual privilege use.
Telemetry and schema boundaries
These examples run in Microsoft Sentinel Logs. Windows examples assume relevant events are collected in SecurityEvent; other environments use WindowsEvent, with different field extraction. Entra role changes are queried from AuditLogs when the Microsoft Entra ID connector is configured. Do not assume that Defender XDR advanced hunting tables exist in Sentinel Logs.
Events and signals to investigate
| Source / event | Why it matters | Qualification |
|---|---|---|
| SecurityEvent 4728 / 4732 / 4756 | Member added to a security-enabled global, local or universal group | Verify the group, actor and member in raw fields |
| SecurityEvent 4738 | User account changed | Not all changes are privilege-related |
| SecurityEvent 4672 | Special privileges assigned to a new logon | Often expected for service and admin accounts |
| SecurityEvent 4624 | Successful logon context | Does not itself prove privileged activity |
| Entra AuditLogs | Role membership and directory changes | Inspect operation, result and target resources |
Group membership events and privileged logon events answer different questions. Correlate them carefully rather than treating a matching timestamp as proof.
Collection first, conclusions second
Confirm that relevant domain controllers, servers and workstations report to the workspace, that audit subcategories are enabled and that the chosen time range falls within retention. A missing event may mean missing telemetry rather than absence of suspicious activity.
KQL hunt 1 — Check Windows privilege event coverage
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
SecurityEvent
| where TimeGenerated >= ago(7d)
| where EventID in (4728, 4732, 4756, 4738, 4672, 4624)
| summarize Events = count(),
ReportingHosts = dcount(Computer),
LastSeen = max(TimeGenerated)
by EventID, bin(TimeGenerated, 1d)
| order by TimeGenerated asc, EventID ascThis measures observed ingestion, not the completeness of auditing. Compare reporting hosts with your expected inventory.
Understand the actor and the target
For membership changes, distinguish the account that performed the action from the account added to the group. Review the group name and domain, target member, initiating identity, reporting host and approved change ticket. Field availability varies, so inspect the raw record before relying on normalized columns.
KQL hunt 2 — Review privileged group additions
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
SecurityEvent
| where TimeGenerated >= ago(7d)
| where EventID in (4728, 4732, 4756)
| project TimeGenerated, Computer, EventID,
Account, Activity, EventData
| order by TimeGenerated desc
| take 250Start with the raw EventData to identify the actor, target member and affected group. This query intentionally avoids assuming a particular event payload layout. The row cap can omit older results.
Which groups are genuinely sensitive?
Prioritize domain-wide administrators, local Administrators on critical servers and other groups that grant high-impact access. A group name alone is not a complete risk assessment: evaluate the actual scope of permissions, asset criticality and whether the membership is temporary or permanent.
Privileged logon versus privilege escalation
Windows event 4672 reports special privileges assigned to a new logon. It is common for built-in and service identities. Use it to understand privileged sessions, not as a stand-alone escalation detection. Event 4624 provides related logon context, but correlation should use reliable identifiers and host scope where available.
KQL hunt 3 — Triage special-privilege logons
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
SecurityEvent
| where TimeGenerated >= ago(72h)
| where EventID == 4672
| summarize PrivilegedLogons = count(),
FirstSeen = min(TimeGenerated),
LastSeen = max(TimeGenerated)
by Computer, Account
| order by PrivilegedLogons desc
| take 100A high count may be routine service activity. Investigate unexpected accounts, unusual hosts and timing against normal administrative behavior.
Microsoft Entra role assignments
Directory roles can provide extensive administrative access. In Entra audit logs, examine role assignment operations, the initiating actor, the target identity, operation result and any eligible or activated access associated with Privileged Identity Management. Audit operation names and nested JSON shapes may vary, so validate them against your tenant’s records.
KQL hunt 4 — Find Entra role assignment activity
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
AuditLogs
| where TimeGenerated >= ago(7d)
| where Category =~ "RoleManagement"
| where OperationName has_any ("Add member to role", "Add eligible member")
| project TimeGenerated, OperationName, Result,
InitiatedBy, TargetResources, CorrelationId
| order by TimeGenerated desc
| take 250Operation naming varies across directory role and PIM workflows. First inspect the actual OperationName values in your tenant and broaden the filter if needed. A returned record is a lead, not proof of unauthorized escalation.
Inspect the audit operation vocabulary
- 1
- 2
- 3
- 4
- 5
- 6
AuditLogs | where TimeGenerated >= ago(30d) | where Category =~ "RoleManagement" | summarize Events = count() by OperationName, Result | order by Events desc
Use this discovery query to find your tenant’s real operation names before relying on a narrowly filtered hunt.
Correlation without inventing certainty
Build separate Windows and Entra timelines first. Compare initiating identities, target accounts, approved change windows and subsequent logons. A shared username or close timestamp does not necessarily mean the same actor or campaign. Document the confidence of every cross-platform link.
Check for actual use of elevated rights
After a membership or role change, investigate subsequent sign-ins, administrative actions, sensitive configuration changes and relevant endpoint process activity. Record the difference between rights granted and rights exercised. Validate the identity context before making a containment recommendation.
MITRE ATT&CK mapping
Relevant techniques include Account Manipulation (T1098) and Valid Accounts (T1078). Privilege escalation is also a tactic, not a single event ID. Map a specific technique only when the observed behavior supports it; an authorized group change should not be automatically classified as malicious.
Common false positives
Approved access requests, emergency response, PIM activation, automated provisioning, deployment tooling and domain maintenance can all produce privileged events. Confirm the business owner, change record, access duration and whether the new rights were necessary.
Agent Foskett investigation workflow
When should the analyst escalate?
Escalate through the incident process when a sensitive privilege change is unexplained, especially if it is followed by suspicious sign-ins, unauthorized configuration changes or misuse of elevated access. Do not remove production access or disable identities solely on the basis of an exploratory KQL result.
Case file resolution — The administrator nobody requested
The Windows group addition is traced to an approved emergency maintenance request, performed by a documented administrator. The Entra role assignment belongs to a separate, time-limited PIM workflow with an approved justification. The events are not evidence of one coordinated escalation. Agent Foskett records the distinct actors, targets and approvals and identifies a reporting improvement: privileged changes need clearer ownership in the SOC change feed.
Finding: elevated permissions were granted, but unauthorized privilege escalation was not established.
Hands-on lab — Investigate privilege changes
- Verify ingestion for group changes and privileged logons.
- Identify one group membership event and inspect its raw payload.
- Record the actor, member, group, host and timestamp.
- Review Entra RoleManagement operation names and one role event.
- Compare both changes with authorized access records.
- Look for evidence of subsequent use of elevated permissions.
- Write a conclusion with at least one alternative explanation and one telemetry gap.
Knowledge check
- Why does event 4672 not prove an attack?
- What is the difference between an actor and a target member?
- Why must you inspect Entra role operation names in your tenant?
- What evidence distinguishes rights granted from rights used?
- How could a PIM activation affect the investigation?
Operational quality checklist
- Confirm collection, retention and reporting-host coverage.
- Use the correct Windows event table and raw fields.
- Separate Windows group changes from Entra role changes.
- Treat KQL output as investigative leads, not verdicts.
- Correlate against approved changes and PIM activity.
- Keep queries read-only and time bounded.
- Do not link to unpublished Lesson 67.
Agent Foskett takeaway
Privilege is not the same as compromise. Establish who granted the access, who received it, what changed and whether the access was used before making an accusation.
The Logs Already Knew.
