CSA (312-39) SOC Simulation Lab

In this simulation, you will step into a high-stakes phishing investigation. You will learn how to transition from detecting an email threat to accurately scoping the user impact to drive precise containment strategies.

Scenario Context

You are a Senior SOC Analyst at Nexus Healthcare Logistics. The L1 team escalated a phishing ticket. A highly convincing, spoofed email titled "URGENT: Q3 Benefit Update" bypassed the Secure Email Gateway (SEG). A user reported it via the Phish Alarm button, but your initial message trace shows the email was successfully delivered to 50 mailboxes before the automated purge triggered.

Before you start resetting 50 passwords and isolating workstations, you need to execute precise containment. You pivot from the SIEM to your Web Proxy, EDR, and Identity logs to reconstruct the timeline.

Security Environment

You correlate the email indicators of compromise (IOCs) across multiple telemetry sources to understand the blast radius.

[O365_MESSAGE_TRACE] :: Sender: admin@nexuss-health.com (Spoofed) | Subject: "URGENT: Q3 Benefit Update" Status: Delivered to 50 mailboxes. [WEB_PROXY_ZSCALER] :: Action: ALLOW | URL: hxxps://update-nexus-health[.]com/login User: jsmith@nexushealth.com | Bytes_Out: 1240 | Bytes_In: 5420 ALERT: Phishing Domain Clicked [EDR_CROWDSTRIKE] :: Host: WKS-JS-01 | Process: chrome.exe -> No child processes spawned. Result: No malicious payloads downloaded/executed. [AZURE_AD_SIGNIN] :: User: jsmith@nexushealth.com | Result: SUCCESS | IP: 192.168.1.10 (Expected Corporate IP) [AZURE_AD_SIGNIN] :: User: jsmith@nexushealth.com | Result: SUCCESS | IP: 45.33.22.11 (Anomalous - ASN: BLNWX, VPS Provider)

Question

A security operations center (SOC) team is investigating a phishing attack that targeted multiple employees. During the Containment Phase, they need to determine how users interacted with the malicious email, whether they opened it, clicked on links, downloaded attachments, or entered credentials. This information is critical to assessing the impact and preventing further compromise. Which specific activity helps the SOC team understand user interactions with the phishing email?

SOC Hint: The question specifically asks about determining *how users interacted* (clicked, downloaded, entered credentials) with the threat. This is a scoping activity, not a remediation or validation activity.

Expert Insight: Tier 3 SOC Analysis

What is happening here?
The SOC is performing incident scoping during the Containment phase. Just because an email was delivered doesn't mean a breach occurred. By checking proxy logs and Azure AD sign-in logs, the analyst is verifying what the user actually did. In our scenario logs, we see `jsmith` didn't just receive the email—they clicked the link (Zscaler log), didn't download malware (CrowdStrike log), but likely submitted credentials which the attacker then successfully used from a VPS IP (Azure AD log).

Why Option B (User action verification) is Correct:
"User action verification" is the formal process of tracking the human element of an attack chain. Phishing investigations require a matrix of verification: Did they receive it? Did they read it? Did they click the link? Did they enter credentials? Did they run the attachment? Verifying these specific user actions dictates the exact containment response (e.g., forcing a password reset vs. just deleting the email).

Why the other options are incorrect:

SOC Mini-Lesson: The Phishing Impact Matrix

When tracking a mass phishing campaign, senior analysts build a mental (or physical) matrix to avoid containing the wrong assets. Treat every recipient differently based on verifiable telemetry:

  • Level 0 (Delivered): Purge email from inbox. (O365 Message Trace)
  • Level 1 (Clicked Link): Purge email + Warn user. (Web Proxy Logs / DNS Logs)
  • Level 2 (Submitted Creds): Purge email + Reset Password + Revoke Active Sessions. (Proxy POST data / Azure AD anomalous logins)
  • Level 3 (Executed Payload): Purge email + Isolate Host from Network + Trigger full IR. (EDR / Sysmon Logs)

Without comprehensive user action verification, you risk alert fatigue by isolating 50 hosts when only one user actually clicked the link.

Ready to validate your SOC analytical skills further?

Explore more CSA simulations at ExamRange >>