Identity Attack Investigation Runbook

SOC & DFIR Operations Guide

Environment: Windows AD | Microsoft 365 | Defender XDR | Sentinel | Entra ID | Palo Alto Prisma Access


Overview & Scope

This runbook provides standardised procedures for investigating identity-based attacks across the hybrid enterprise environment. It covers detection, investigation, containment, and remediation workflows for both on-premises Active Directory and cloud identity platforms.

Identity Attack Categories

Category
Techniques

Credential Theft

Password spraying, brute force, credential stuffing, phishing

Token/Session Attacks

Pass-the-Hash, Pass-the-Ticket, Golden/Silver Ticket, Token theft

Privilege Escalation

Kerberoasting, AS-REP Roasting, DCSync, AdminSDHolder abuse

Lateral Movement

RDP hijacking, SMB relay, DCOM/WMI abuse

Persistence

Skeleton Key, DCShadow, Federation trust abuse, App consent grants

Cloud Identity Attacks

OAuth abuse, consent phishing, MFA fatigue, device code phishing


Detection Sources & Data Mapping

Log Sources Matrix

Platform
Log Table
Key Events

On-Prem AD

SecurityEvent

4624/4625, 4768/4769, 4672, 4720-4738

Entra ID

SigninLogs, AADNonInteractiveUserSignInLogs

Sign-ins, MFA, CA policies, risk events

Entra ID

AuditLogs

User/group changes, app registrations, PIM

Defender for Identity

IdentityDirectoryEvents, IdentityLogonEvents

LDAP queries, Kerberos activity, recon

Defender XDR

AlertEvidence, IdentityInfo

Correlated alerts, entity context

Cloud Apps

CloudAppEvents

SaaS activity, OAuth grants, file access

Prisma Access

PaloAltoPrismaAccess

VPN connections, GlobalProtect, ZTNA

Critical Windows Event IDs

Event ID
Description
Investigation Relevance

4624

Successful logon

Baseline normal access, identify anomalies

4625

Failed logon

Brute force, password spray detection

4648

Explicit credential logon

RunAs usage, lateral movement

4672

Special privileges assigned

Privileged access tracking

4768

Kerberos TGT requested

AS-REP roasting, initial auth

4769

Kerberos service ticket

Kerberoasting, service access

4776

NTLM authentication

Pass-the-Hash, legacy auth

4720

User account created

Persistence, rogue accounts

4732

Member added to group

Privilege escalation

4662

Directory object accessed

DCSync detection


Investigation Workflows

Compromised Account Investigation

Objective: Determine scope of compromise, identify threat actor activity, and contain the account.

Step 1: Initial Triage

  1. Document the alert source, timestamp, and affected account(s)

  2. Check Defender XDR for correlated incidents and alerts

  3. Verify account type: standard user, service account, admin, or privileged

  4. Assess business criticality and data access level

Step 2: Sign-In Analysis

  1. Query Entra ID SigninLogs for last 30 days of activity

  2. Identify anomalous locations, devices, or IP addresses

  3. Check for impossible travel scenarios

  4. Review MFA challenge results and authentication methods

  5. Examine Conditional Access policy evaluations

Step 3: Activity Timeline

  1. Build timeline from first suspicious activity

  2. Query AuditLogs for configuration changes

  3. Check CloudAppEvents for M365 and SaaS activity

  4. Review EmailEvents for mailbox rules and forwarding

  5. Examine OfficeActivity for file access and sharing

Step 4: Lateral Movement Check

  1. Query IdentityLogonEvents for on-prem authentication

  2. Check DeviceLogonEvents for endpoint access

  3. Review SecurityEvent for network logons (Type 3, 10)

  4. Identify accessed systems and potential pivot points

Step 5: Containment Actions

  1. Revoke all refresh tokens via Entra ID

  2. Disable account if active threat confirmed

  3. Reset password and require MFA re-registration

  4. Review and revoke OAuth app consents

  5. Remove any suspicious mailbox rules


Credential Attack Investigation

Objective: Identify credential-based attacks including password spray, brute force, and credential stuffing.

Detection Indicators

  • High volume of failed authentications from single/multiple IPs

  • Multiple accounts targeted with same password

  • Authentication attempts during unusual hours

  • Legacy protocol usage (POP3, IMAP, SMTP AUTH)

  • TOR exit node or VPN/proxy IP addresses

Investigation Steps

  1. Aggregate failed sign-ins by IP, user, and error code

  2. Calculate authentication failure rates and patterns

  3. Correlate with successful authentications post-failure

  4. Check IP reputation via threat intelligence

  5. Identify affected accounts requiring password reset

  6. Review Conditional Access to block attack vectors


Kerberos Attack Investigation

Objective: Detect and investigate Kerberoasting, AS-REP Roasting, Pass-the-Ticket, and Golden/Silver Ticket attacks.

Kerberoasting Indicators

  • Event 4769 with RC4 encryption (0x17) for service tickets

  • High volume of service ticket requests from single user

  • Requests for SPNs associated with service accounts

  • MDI alerts for Kerberos encryption downgrade

Golden/Silver Ticket Indicators

  • TGT with abnormally long lifetime

  • Missing or inconsistent PAC data

  • TGT used without corresponding AS-REQ

  • Service ticket without prior TGT request


KQL Query Cheat Sheet

Entra ID Sign-In Analysis

User Sign-In Summary (Last 7 Days)

Failed Sign-Ins with Error Details

Impossible Travel Detection


Password Spray Detection

Password Spray Pattern Detection

Successful Auth After Spray


Defender for Identity Queries

Kerberoasting Detection

DCSync Detection


On-Premises AD Queries

NTLM Authentication Analysis

Suspicious Service Ticket Requests (Kerberoasting)

Privileged Group Membership Changes


Prisma Access Queries

VPN Authentication Anomalies

Concurrent Session Detection


Response Actions & Remediation

Immediate Containment Actions

Scenario
Action
Command/Location

Compromised Cloud Account

Revoke sessions

Entra ID → Users → Revoke Sessions

Active Attack

Disable account

Set-AzureADUser -AccountEnabled $false

Token Theft

Revoke refresh tokens

Revoke-AzureADUserAllRefreshToken

On-Prem Account

Disable AD account

Disable-ADAccount -Identity <user>

Malicious OAuth App

Remove app consent

Remove-AzureADOAuth2PermissionGrant

Golden Ticket

Reset KRBTGT (2x)

Reset-KrbtgtKeyInteractive.ps1

Post-Incident Hardening

Action
Details

Enable MFA

Enforce phishing-resistant MFA (FIDO2, Windows Hello)

Conditional Access

Block legacy authentication, require compliant devices

Password Policy

Implement Azure AD Password Protection, banned password list

Privileged Access

Implement PIM for just-in-time admin access

Service Accounts

Migrate to gMSA, implement credential rotation

Monitoring

Enable Sign-in Risk and User Risk policies in Identity Protection


Quick Reference Cards

Attack Type Quick Identification

Attack Type
Key Indicators
Primary Data Source

Password Spray

Many accounts, few attempts each, same time window

SigninLogs (50126)

Brute Force

Single account, many attempts, sequential

SigninLogs, SecurityEvent 4625

MFA Fatigue

Multiple MFA prompts, user finally approves

SigninLogs (MFA required)

Kerberoasting

Bulk TGS requests, RC4 encryption, service SPNs

SecurityEvent 4769, MDI

Pass-the-Hash

NTLM auth from unusual source, no interactive logon

SecurityEvent 4776, MDI

DCSync

DS replication from non-DC, GetNCChanges

SecurityEvent 4662, MDI

Consent Phishing

OAuth grant to unknown app, excessive permissions

AuditLogs, CloudAppEvents

Entra ID Error Code Reference

Error Code
Description
Investigation Notes

50126

Invalid username or password

Common in spray attacks

50053

Account locked

Result of brute force

50074

MFA required

Check if followed by success

50076

MFA denied

User rejected - may indicate awareness

53003

Blocked by CA policy

CA working correctly

50158

External security challenge

Third-party MFA in use

50140

Keep me signed in interrupt

Normal behavior

50097

Device authentication required

Device compliance check


Escalation Matrix

Severity Classification

Severity
Criteria
Response Time

🔴 Critical

Domain Admin compromise, Golden Ticket, active data exfiltration

Immediate - 15 min response

🟠 High

Privileged account compromise, lateral movement detected

30 min - 1 hour response

🟡 Medium

Standard user compromise, ongoing password spray

4 hour response

🟢 Low

Failed attack attempts, reconnaissance activity

Next business day

Escalation Path

Tier
Responsibility

Tier 1 SOC

Initial triage, alert validation, basic containment

Tier 2 SOC

Deep investigation, advanced hunting, incident coordination

DFIR Team

Forensic analysis, malware analysis, evidence preservation

Identity Team

AD/Entra configuration changes, KRBTGT reset

CISO/Security Leadership

Critical severity incidents, breach notification decisions

Documentation Requirements

All identity incidents must include:

  1. Initial detection timestamp and alert source

  2. Affected account(s) and account type(s)

  3. Attack vector and techniques (MITRE ATT&CK mapping)

  4. Timeline of attacker activity

  5. Systems accessed and potential data exposure

  6. Containment actions taken with timestamps

  7. Evidence preserved (logs, screenshots, exports)

  8. Remediation actions and hardening recommendations


MITRE ATT&CK Mapping

Tactic
Technique
ID
Detection

Initial Access

Valid Accounts

T1078

SigninLogs

Credential Access

Brute Force

T1110

4625, SigninLogs

Credential Access

Kerberoasting

T1558.003

4769, MDI

Credential Access

DCSync

T1003.006

4662, MDI

Lateral Movement

Pass the Hash

T1550.002

4776, MDI

Lateral Movement

Pass the Ticket

T1550.003

4768/4769, MDI

Persistence

Golden Ticket

T1558.001

4768, MDI

Persistence

Application Access Token

T1550.001

AuditLogs

Defense Evasion

Modify Authentication Process

T1556

AuditLogs, 4657


Appendix: PowerShell Commands

Entra ID / Azure AD (Microsoft Graph)

On-Premises Active Directory

Microsoft Graph API (REST)


Note: This runbook should be reviewed and updated regularly or after significant incidents to incorporate lessons learned and emerging attack techniques.

Last updated