DemoContoso Ltd is a fictional company. The grade, the findings and the attack paths came from Tenant Strike’s engine reading made-up data.

Run it on your own tenant →
← All attack paths in this snapshot

Attacker’s View™ / Modeled attack path

Endpoint compromise → OneDrive sync fanout → org-wide ransomware

critical potential impacthigh modeled likelihood4 findings to fix

Modern SMB ransomware no longer needs to traverse a Windows domain — OneDrive's Known Folder Move (now default for new tenants) silently mirrors user folders to the cloud, where changes fan out to every other synced device. A single phished user with no EDR, no compliance enforcement, and no sync restriction becomes a company-wide encryption incident. Defender for Endpoint + a 'require compliant device' CA policy + sync-to-managed-devices-only is the standard mitigation triad.

Follow the possible attack.

Saved model · not observed activity
  1. Get in

    Modeled progression

    Phishing email with malicious attachment reaches a user; user opens it, payload executes.

    Technique & evidence details

    Phishing: Spearphishing Attachment T1566.001 ↗

    This is a modeled continuation with no directly linked check.

  2. Run code

    A finding to fix

    Payload spawns PowerShell, downloads ransomware loader. Without Defender for Endpoint onboarded, the behavioral chain (Office spawning PowerShell, PS downloading executable) generates no EDR alert. Built-in AV may flag the final payload signature — but only after persistence.

    Technique & evidence details

    Command and Scripting Interpreter T1059 ↗

  3. Move across

    A finding to fix

    Attacker uses captured credentials from the endpoint to sign in to M365 — from their own attacker-controlled machine. No CA policy requires a compliant device, so the unmanaged-device sign-in succeeds.

    Technique & evidence details

    Valid Accounts: Cloud Accounts T1078.004 ↗

  4. Collect data

    A finding to fix

    Attacker installs OneDrive on an unrestricted device, signs in as the compromised user, and pulls a full local copy of OneDrive + every SharePoint library the user has synced. The data is now on attacker-controlled storage.

    Technique & evidence details

    Exfiltration to Cloud Storage T1567.002 ↗

  5. Business impact

    A finding to fix

    Ransomware encrypts the local endpoint (no BitLocker means no recovery-key escrow either). For users with OneDrive Known Folder Move, the encryption syncs UP to OneDrive and ripples out to every other endpoint syncing from the same library — multiplying the blast radius.

    Technique & evidence details

    Data Encrypted for Impact T1486 ↗

Scenario, not incident evidence.

The sequence models what could happen. Findings show observed settings or signals; they do not prove that an attacker completed a step. A passing check, accepted risk or missing observation does not independently establish that a path is closed.

Where to intervene

Review the contributing findings

Open this scan’s action plan →

Inspect the evidence and remediation for each control. After making changes, rescan and review fresh results before considering the risk reduced.

  • Should fixNeeds fixingWho can see your files

    Restrict OneDrive sync to domain-joined devices

    What this means

    OneDrive sync is permitted on ANY device. Users can install OneDrive on personal laptops, home desktops, or borrowed machines and pull a full local copy of all files they can access. That data then escapes all tenant controls — BitLocker, remote wipe, CA, audit logging.

    What to do

    Limit OneDrive sync to devices joined to your on-premises domains, or hold sync to compliant devices with a Conditional Access policy.

    Who does it
    Your IT person or provider
    How long
    About 15 minutes
    Before you change it
    Users on personal/BYOD devices will lose the ability to sync OneDrive locally. They can still access files via OneDrive web. For BYOD-heavy organizations, consider Intune App Protection Policies as an alternative.
    1 evidence row
    Technical detailssetting, steps, evidence

    The setting

    OneDrive sync restriction to domain-joined computers

    SharePoint admin center → Settings → Sync → 'Allow syncing only on computers joined to specific domains'

    Now: Disabled (any device can sync)→Should be: Enabled (listed domains only)

    Open in the admin portal ↗

    Steps

    1. admin.microsoft.com → SharePoint admin center → Settings → Sync
    2. 'Allow syncing only on computers joined to specific domains' OR
    3. Set 'isUnmanagedSyncAppForTenantRestricted' via Graph PATCH

    Microsoft Graph

    PATCH /beta/admin/sharepoint/settings
    { "isUnmanagedSyncAppForTenantRestricted": true }

    Evidence · 1 recorded item

    • Sync limited to domain-joined computers — Disabled

    How an attacker would use it

    Disgruntled or departing employee installs OneDrive on their personal MacBook, signs in, syncs their entire OneDrive locally (which often includes shared SharePoint libraries they have access to). When they leave the company and their account is disabled, the cloud access is cut — but the local copy on their personal device remains, untouchable.

    Learn more ↗
  • SeriousNeeds fixingLaptops and phones

    Require BitLocker on Windows

    What this means

    2 Windows devices report BitLocker disabled. Each unencrypted device is a data-breach incident waiting for a theft or loss.

    What to do

    Make BitLocker mandatory via a compliance policy setting. Devices that fail will be marked non-compliant and (with a CA policy) blocked from corp resources until encrypted.

    Who does it
    Your IT person or provider
    How long
    About 1.5 hours
    Before you change it
    Devices currently unencrypted will be marked non-compliant. Users will need to enable BitLocker (15-60 min per device depending on disk size). Push the policy with a grace period so users have time.
    2 evidence rows
    Technical detailssetting, steps, evidence

    The setting

    BitLocker / disk encryption policy

    Intune admin center → Endpoint security → Disk encryption

    Now: 2 Windows devices with BitLocker disabled, 0 with unknown status (of 4 total)→Should be: BitLocker required by compliance policy and enabled on all Windows devices

    Open in the admin portal ↗

    Steps

    1. intune.microsoft.com → Devices → Compliance policies
    2. Open your Windows compliance policy (or create one)
    3. System Security → Encryption → 'Require encryption of data storage' → Require
    4. Save
    5. Then: Devices → Configuration profiles → Create profile → Windows → Endpoint protection → BitLocker base settings → Enable

    Evidence · 2 recorded items

    • CONTOSO-LT-07 — (no user) · 10.0.19045 · BitLocker DISABLED
    • RECEPTION-PC — (no user) · 10.0.19045 · BitLocker DISABLED

    How an attacker would use it

    Laptop is stolen or lost. Without BitLocker, the attacker boots from USB or removes the disk and mounts it on another machine. All OneDrive sync content, cached Outlook items, saved attachments, and Teams data are readable as files. No password prompt, no audit signal — pure offline data theft.

    Learn more ↗
  • Should fixNeeds a lookLaptops and phones

    Onboard devices to Defender

    What this means

    4 Windows devices are enrolled in Intune but no Defender for Endpoint or Defender for Business license is detected on the tenant. Endpoints run with built-in AV only — no EDR signal feeds your security team.

    What to do

    Add Defender for Business (bundled with M365 Business Premium) or Defender for Endpoint Plan 1/2.

    Who does it
    Your IT person or provider
    How long
    Not estimated
    1 evidence row
    Technical detailssetting, evidence

    The setting

    Defender for Endpoint / Business licensing

    Microsoft 365 admin center → Billing → Purchase services (then onboard in Microsoft Defender portal → Settings → Endpoints)

    Now: 4 Windows devices enrolled; no Defender for Endpoint or Defender for Business licence detected in the tenant→Should be: Defender for Business or Defender for Endpoint P1/P2 licensed and provisioned

    Open in the admin portal ↗

    Evidence · 1 recorded item

    • Tenant Defender capability — No DefenderForBusiness / DefenderForEndpoint_P1 / DefenderForEndpoint_P2 detected
    Learn more ↗
  • SeriousNeeds fixingLaptops and phones

    Require compliant devices

    What this means

    No Conditional Access policy requires a compliant device for any application. Your compliance evaluation is purely descriptive — it tells you who's non-compliant but doesn't prevent non-compliant (or attacker-controlled, unenrolled) devices from accessing corp data.

    What to do

    Create a CA policy requiring 'Compliant device' (or 'Hybrid Azure AD joined device') for access to all cloud apps, or at minimum for sensitive apps (Exchange, SharePoint, finance apps).

    Who does it
    Your IT person or provider
    How long
    About 45 minutes
    Before you change it
    Users on non-Intune-enrolled devices will be blocked from sign-in. This is the intended behavior but will affect: BYOD users without Intune enrollment, kiosks, contractors with their own devices. Plan exceptions or alternative paths (MAM-only, App Protection Policies, etc.) before enforcing.
    1 evidence row
    Technical detailssetting, steps, evidence

    The setting

    Conditional Access — require compliant device grant

    Entra admin center → Protection → Conditional Access → Policies

    Now: 1 CA policy enabled, none requiring compliant or hybrid-joined device→Should be: At least one enabled CA policy granting access only when the device is marked compliant or hybrid-joined

    Open in the admin portal ↗

    Steps

    1. entra.microsoft.com → Protection → Conditional Access → New policy
    2. Name: 'Require compliant device — all apps'
    3. Users: All users; Exclude: break-glass account, service accounts that use modern auth from non-Intune systems
    4. Cloud apps: All cloud apps (or scope to Exchange/SharePoint first)
    5. Grant: Grant access → Require device to be marked as compliant (and/or Require Hybrid Azure AD joined device) → Require one of the selected controls
    6. Enable in Report-only for 2 weeks first, review impact, then switch On

    Evidence · 1 recorded item

    • No CA policy requires compliant device — 1 CA policies enabled, none make a compliant or hybrid-joined device mandatory for access

    How an attacker would use it

    Attacker phishes a user's password. From their own laptop (unenrolled, unmanaged, perhaps compromised) they sign in and access mail, SharePoint, Teams. Your enrolled-device controls — compliance, BitLocker, Defender — protect zero data in this scenario because the access happens from a device they were never installed on.

    Learn more ↗

Understand the pattern

Further reading