BEC and phishing investigation — MDO + MDCA + MDE
Scenario: A phishing email lands, the user clicks a Safe Links URL, credentials harvest to an attacker domain, the attacker signs into Microsoft 365 from a foreign IP, sets a mailbox forwarding rule, and exfiltrates contacts from OneDrive. MDO flags the phishing email, MDCA flags the impossible-travel sign-in and forwarding rule, MDE flags the credential entry on the user device, and Defender XDR fuses all signals into a single incident with a unified timeline.
EPC Group outcome: EPC Group ships standardized BEC runbooks — auto-quarantine the email, revoke active Entra sessions, disable forwarding via Graph API, isolate the endpoint via MDE Live Response. Mean time to contain on the runbook is under 15 minutes.
Ransomware lateral movement — MDE + MDI + MDVM
Scenario: Initial access through an unpatched VPN appliance MDVM had flagged as a critical CVE. Attacker drops Cobalt Strike (MDE detects), runs DCSync against the domain controller (MDI detects), then attempts lateral movement using stolen credentials. The MDI lateral movement path graph had already flagged the compromised account as reachable to Tier 0 — the posture finding becomes the root cause.
EPC Group outcome: AIR playbooks isolate the endpoint, disable the user through MDI action accounts, force credential rotation through Entra, and hand off to a Sentinel SOAR playbook. The combined MDE + MDI + MDVM signal stops ransomware before file servers are touched in 80 percent of EPC Group red-team simulations on the platform.
Supply chain compromise — MDE + MDCA + MDVM + MDO
Scenario: A SaaS vendor consumed by 12,000 employees through OAuth SSO is breached. Attacker uses the compromised consent to read mailbox data, and a malicious npm package enters the CI/CD pipeline. MDCA flags the OAuth app risk score change, MDVM flags the npm package in software inventory, MDO flags suspicious forwarding tied to the app, and MDE flags the package on developer endpoints.
EPC Group outcome: EPC Group ships an OAuth app governance baseline that pre-blocks high-risk consent patterns, runs weekly OAuth risk reviews in MDCA, integrates MDVM with the customer SBOM, and configures custom detection rules that fire when MDVM finds a known-malicious package on an endpoint with CI/CD pipeline access.
Insider risk and data exfiltration — MDCA + MDE + Microsoft Purview
Scenario: A departing employee downloads sensitive engineering files from SharePoint and uploads them to a personal cloud service. MDCA detects the mass download, MDE detects the upload to an unmanaged cloud, Microsoft Purview Insider Risk correlates with the resignation event, and Defender XDR fuses all three signals into a single insider-risk incident.
EPC Group outcome: EPC Group integrates Defender XDR with Purview Insider Risk policies, configures MDCA Conditional Access App Control session policies that block download to unmanaged devices, and ships automated response that revokes the Entra session and triggers a legal-hold workflow in Purview eDiscovery.
AKS container runtime threat — MDE + Defender for Cloud bidirectional XDR
Scenario: A vulnerable container image pulls to AKS, executes a privilege escalation, mounts the node file system, drops a crypto-miner, and beacons out. Defender for Cloud detects the container runtime threat, the underlying AKS node MDE sensor detects the malicious process at the kernel layer, and Defender XDR correlates the container-level and node-level signals into one incident with image lineage attached.
EPC Group outcome: EPC Group configures the bidirectional Defender for Cloud and Defender XDR integration so AKS runtime alerts surface as XDR incidents and endpoint alerts on AKS nodes return to Defender for Cloud attack path analysis. See the EPC Group Defender for Cloud CNAPP hub for the workload-side configuration.
M&A tenant consolidation and cross-tenant XDR
Scenario: A Fortune 500 acquirer integrates a Fortune 1000 target post-close. The target carries a separate Microsoft 365 tenant with its own Defender XDR. SOC teams need cross-tenant visibility during the 9-to-18-month tenant migration window — but two separate XDR portals exist without configuration.
EPC Group outcome: EPC Group configures Microsoft 365 multi-tenant organization (MTO) and the Defender XDR multi-tenant view (GA 2024) so analysts see consolidated incidents across both tenants in one portal. Acquired-tenant MDE, MDO, MDCA, MDI, and MDVM signal all surface alongside the acquirer. EPC Group has executed this pattern across 200+ M&A engagements and is the dominant U.S. practice for Microsoft-anchored post-close security integration.