Skip to content
Home » Articles » Employee Phish Clicked? The 15-Minute Triage Guide

Employee Phish Clicked? The 15-Minute Triage Guide

The Anatomy of a Modern Phishing Attack

Today’s phishing attacks extend far beyond simple credential harvesting. Adversaries now deploy sophisticated reverse-proxy phishing kits, such as Evilginx or Modlishka, to conduct Adversary-in-the-Middle (AiTM) attacks. These toolkits intercept legitimate authentication flows, capturing not only usernames and passwords but also active session cookies and multi-factor authentication (MFA) tokens.

When an employee clicks a malicious link from an AiTM phishing site, the attacker’s proxy sits between the user and the legitimate service (e.g., Microsoft 365, Salesforce). The user enters their credentials and completes their MFA challenge as usual, unaware that the attacker is simultaneously relaying these details to the real service and capturing the resulting session cookie. This allows the attacker to bypass MFA and hijack the legitimate user session, gaining immediate access to cloud applications and data. The objective is no longer just a password, but a live, authenticated session.

The 15-Minute First-Responder Runbook

When an employee reports clicking a suspicious link or entering credentials on a potentially malicious site, immediate and decisive action is critical. The following runbook outlines the essential steps for IT administrators and security analysts within the first 15 minutes to contain a potential credential compromise.

T+0 to T+2m: Initial Verification & Network Disconnect

The first two minutes are about verifying the report and isolating the immediate threat.

  1. Verify the Report: Quickly confirm with the employee that they clicked a link or entered credentials. Ask for the exact URL if possible.
  2. Immediate Network Disconnect: Instruct the user to disconnect their device from the network. This means disabling Wi-Fi, unplugging Ethernet, or powering down the device. This prevents immediate lateral movement or data exfiltration from the endpoint.
  3. Identify Compromised Account: Determine the specific user account and associated services (e.g., Microsoft 365, VPN, line-of-business applications) that may have been compromised.

T+2 to T+5m: Emergency Session Invalidation & Password Reset

Once the immediate network threat is contained, focus on invalidating the stolen session and securing the account.

  1. Revoke All Active User Sessions: This is a critical step to invalidate any session tokens an attacker may have stolen via AiTM phishing. For Microsoft 365/Entra ID, use PowerShell:
# Connect to Microsoft Graph PowerShell
Connect-MgGraph -Scopes "User.ReadWrite.All", "Directory.ReadWrite.All"

# Replace 'user@yourdomain.com' with the actual UPN of the compromised user
$UserPrincipalName = "user@yourdomain.com"
$UserId = (Get-MgUser -UserId $UserPrincipalName).Id

# Revoke all active sessions for the specified user
Revoke-MgUserSignAndSession -UserId $UserId
Write-Host "All active sessions revoked for $($UserPrincipalName)."
This command forces the user (and any attacker) to reauthenticate across all services using Entra ID.
  1. Enforce Emergency Password Reset: Immediately initiate a password reset for the compromised user account. For Entra ID, this can be done via the Azure portal or PowerShell:
# Reset user password (will prompt for new password)
Set-MgUserPassword -UserId $UserId
Write-Host "Password reset initiated for $($UserPrincipalName)."
Ensure the new password meets strong complexity requirements and the user is instructed to not reuse it. Temporarily enforce a lockout if suspicious activity persists.

T+5 to T+10m: Endpoint Quarantine & Persistence Sweep

With the account secured, shift focus to the compromised endpoint and checking for persistence mechanisms.

  1. Endpoint Quarantine: If not already done, ensure the affected device is physically or logically isolated. This might involve moving it to a network quarantine segment or blocking its MAC address at the switch level.
  2. Check for Malicious Inbox Rules: Attackers often create inbox forwarding rules to maintain access to emails or redirect sensitive communications. Audit and remove any suspicious rules:
# Connect to Exchange Online PowerShell
Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com

# Replace 'user@yourdomain.com' with the actual UPN
$Mailbox = "user@yourdomain.com"

# Get all inbox rules for the user
Get-InboxRule -Mailbox $Mailbox | Format-List Name, Description, Enabled, ForwardTo, RedirectTo

# To remove a suspicious rule (replace 'Rule Name' with the actual rule name)
# Remove-InboxRule -Mailbox $Mailbox -Identity "Rule Name" -Confirm:$false
  1. Audit OAuth Application Grants: Attackers can trick users into granting illicit consent to malicious OAuth applications. Review the user’s granted applications in Entra ID and remove any unauthorized ones.
    • Navigate to the Azure portal > Entra ID > Users > (Compromised User) > Applications.
    • Review granted applications and revoke consent for any suspicious or unknown entries.

T+10 to T+15m: Incident Documentation & Sign-in Log Review

The final minutes are for documentation and initial forensic data collection.

  1. Incident Documentation: Start an incident response ticket. Log all actions taken, timestamps, and observations. This forms the chain of custody and helps in post-incident analysis.
  2. Review Sign-in Logs: Examine the Entra ID sign-in logs for the compromised user account for any anomalous activity immediately before or after the reported click. Look for:
    • Sign-ins from unusual geographic locations or IP addresses.
    • Successful sign-ins after the reported click, especially from non-corporate devices.
    • Unusual user agent strings.
    • Failed sign-in attempts indicating brute-force or credential stuffing.
  3. Escalate to DFIR Team: Formally escalate the incident to your Digital Forensics and Incident Response (DFIR) team for a deeper investigation into the endpoint and potential lateral movement. DFIR for Modern Enterprises is critical for thorough post-compromise analysis.

Defensive Identity Hardening

Preventing credential compromise is always more effective than reacting to it. Implement these hardening measures:

  • Phishing-Resistant MFA: Deploy FIDO2 security keys or Windows Hello for Business. These methods cryptographically bind authentication to the legitimate site, making AiTM phishing ineffective. Two-Factor Authentication Hardening is paramount.
  • Entra ID Conditional Access: Implement policies that enforce authentication strengths, require trusted locations for sensitive applications, and flag anomalous sign-ins.
  • Continuous Access Evaluation (CAE): Enable CAE in Entra ID to allow for near real-time revocation of access based on risk signals, reducing the window for session hijacking.
  • User Education: Regularly train employees on identifying phishing attempts, especially those targeting MFA. Emphasize reporting suspicious emails immediately.

Need Urgent IT Assistance or Perimeter Defense?

Is your organization vulnerable to active edge exploits, credential harvesting, or compliance audit penalties? Helpdesk.ca provides 24/7/365 managed IT support, emergency incident triage, and co-managed IT escalation for Canadian enterprises.


CANADIAN INCIDENT RESPONSE & MANAGED CYBER DEFENSE

Is Your Organization Prepared to Contain an Active Breach in Under 15 Minutes?

Helpdesk.ca delivers 24/7/365 proactive IT help desk operations, rapid incident triage, and enterprise Microsoft 365 identity hardening for Canadian organizations. Neutralize credential threats before adversaries establish persistence.

Sources & References

  • Canadian Centre for Cyber Security. “Top 10 IT Security Actions.” Government of Canada.
  • CISA. “Protecting Against Malicious OAuth Applications.” Cybersecurity and Infrastructure Security Agency.
  • Microsoft. “Revoke-MgUserSignAndSession (Microsoft.Graph.Users).” Microsoft Learn.
  • MITRE ATT&CK. “T1566.002 Phishing: Spearphishing Link.” MITRE Corporation.
Helpdesk.ca Assistant

Please enter your details to start chatting.

Hello! How can I help you today?