Intune Baseline Assessment (86 controls)
Registry v2.1.0 — windows, macos, ios, android — corporate ownership
Job ID: demo-tune-0419
Generate Device-Compromise Tabletop
EnterpriseVeri-TuneA facilitator-ready scenario, injects, and scoring rubric — composed from the device-compliance gaps in this scan.
Learn more about Veri-Tech IR Tabletops
Source: demo-tune-0419
Org-shape (per drill, demo only)
Veri-Tech sizes every drill around your actual team, not a generic enterprise template. The demo lets you nudge the shape with the controls below; the real product gives you the full freedom described in the callout.
You write your own role labels — not ours.
In your real tenant, you type the role names your team actually uses: M365 Admin, Service Manager, VP IT, External IR Retainer — whatever your lexicon is. The AI uses those exact labels in drill participants, IR-plan owners, AI Coaching recommendations, and the auditor manifest’s orgShape field.
You can also add roles for a specific drill on the fly — e.g. spin up an “Inland Energy AP Clerk” row before running a BEC scenario without touching tenant-wide settings. The demo simulates this with a curated roster + slider; real customers get the full custom-label form (60-char cap, name-detection guardrail, per-role headcount).
Auditor-grade IR evidence in one click — satisfies HIPAA §164.308(a)(8), SOC 2 CC7.4, and ISO 27001 A.5.24 evaluation requirements.
Generation runs in ~3–5 minutes; output lands in Veri-Vault as a tabletop artifact.
Preview a sample tabletopbased on findings shape
Personal phone with no MAM policy leaks corporate Outlook cache
Veri-Tune · v1.0.0Your scan flagged 38 personal devices accessing corporate mail without an App Protection Policy — this scenario walks through what happens when one is stolen.
Protect (PR.PT)
60 minutes
5 timed
6 criteria
On a Friday evening, a senior engineer's personal Android phone is stolen at a transit station. The phone has Outlook for Android installed, signed in to corporate identity, with 14 days of cached mail including draft RFP responses and a board-deck PDF. The phone is unlocked when stolen (the engineer was actively using it). Your scan showed the device is enrolled in compliance reporting but has NO App Protection Policy applied — meaning the corporate data on the device is not encrypted at rest by the corporate-controlled key, and a remote wipe would only work if the device is online and we can locate it.
Threat actor: Opportunistic theft, low-skill. Phone may be wiped and resold OR data may be exfiltrated if the thief is more sophisticated than typical.
Attack chain
- 1Initial access: Phone stolen unlocked at transit station. Outlook is the front-most app.
- 2Data discovery: Thief (or buyer) explores the Outlook cache. 14 days of mail visible without re-authentication because session is active.
- 3Exfiltration: Cached attachments (board deck PDF, RFP drafts) downloadable via 'Save to Photos' → uploaded to attacker cloud storage.
- 4Persistence (optional): If thief is sophisticated: install a forwarding rule from the device, gaining persistent visibility into mail until detected.
Affected assets
- Senior engineer's corporate mailbox (90 days mail history accessible via cache + reauth)
- Board deck PDF (revenue projections + planned acquisitions)
- RFP response drafts (competitive intelligence)
- Cached calendar with attendee names + meeting subjects
Linked scan findings
| Control ID | Severity | Finding |
|---|---|---|
| INT-AP-001 | High | App Protection Policy not applied to BYOD Android devices accessing corporate Outlook |
| INT-CA-014 | High | Conditional Access does not require app-protection state for Outlook mobile |
| INT-CMP-007 | Medium | Device compliance reporting enabled but no policy enforcement |
Generated from Veri-Tune scan demo-tune-0419 on 2026-05-07. This is facilitator material — verify scenario specifics against your tenant before use. Veri-Tech does not warrant scenario fitness for any specific audit framework; pair with the source scan job (which IS auditor evidence) and your own IR plan.
Policy Insights
We found 7 settings that exist in multiple Intune policies. Including 3 value conflicts where policies disagree on the correct setting. 3 redundant settings could be consolidated. 1 unassigned duplicates are inactive and can be cleaned up.
Remediation Planner
AI analyzes your assessment results and generates a remediation plan — classifying each control for auto-deployment, runbook generation, or risk exception.
- Auto-deploy fixes for non-compliant Intune policies
- Generate runbooks for manual remediation steps
- Set risk exceptions and document justifications
Assessment Results
Assessment Score
Scanned: 4/22/2026, 3:06:12 PM — 132s
68%
ProtectionProtectionShare of controls configured correctly AND assigned to users or devices — what’s actively defending your fleet right now.passed / total
Actively enforced
76%
ReadinessReadinessShare of controls configured correctly, whether or not they’re assigned. Counts policies that exist with the right settings but haven’t been deployed to a scope yet.(passed + not-enforced) / totalThe gap between Readiness and Protection is your fastest compliance win — the work is done, it just needs an assignment.
Configured correctly
60
Passing
5
Not Assigned
3
Report-Only
14
Misconfigured
4
Missing
Score Breakdown
Control Status
8% gap from policies not enforced
5 controls correctly configured but not assigned to any device group. Assign these policies to close the gap.
Assign Existing Policies
5 controls across 5 policies are correctly configured but not assigned to any device or user group. Assigning them is a one-click fix that lifts your adjusted score immediately.
Enrollment Restriction Mismatches (1)
iOS personal enrollment is not blocked. Corporate devices ownership model is set but personal enrollments are accepted.
See how your protection score improves with each remediation step:
+8.2% gain
+13.7% gain
Control Results
86 of 86 controls
🔴 Misconfigured14
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
Policy value does not match the required baseline. Current value diverges from expected; update in place or create override.
🟡 Not Enforced5
Policy is configured correctly but not assigned to any group. Assign to target devices/users.
Policy is configured correctly but not assigned to any group. Assign to target devices/users.
Policy is configured correctly but not assigned to any group. Assign to target devices/users.
Policy is configured correctly but not assigned to any group. Assign to target devices/users.
Policy is configured correctly but not assigned to any group. Assign to target devices/users.
⚪ Missing4
No matching Intune policy found. Create a new policy from the curated Veri-Tune baseline.
No matching Intune policy found. Create a new policy from the curated Veri-Tune baseline.
No matching Intune policy found. Create a new policy from the curated Veri-Tune baseline.
No matching Intune policy found. Create a new policy from the curated Veri-Tune baseline.
✅ Passing60
Configured and assigned correctly via 'Device Compliance — Require FileVault on macOS'.
Configured and assigned correctly via 'Device Compliance — Block rooted Android devices'.
Configured and assigned correctly via 'Device Compliance — iOS minimum OS version'.
Configured and assigned correctly via 'Endpoint Security — ASR — Block Win32'.
Configured and assigned correctly via 'Endpoint Security — macOS System Integrity Protection'.
Configured and assigned correctly via 'Endpoint Security — Disk encryption — recovery'.
Configured and assigned correctly via 'Device Compliance — Require BitLocker on Windows'.
Configured and assigned correctly via 'Device Compliance — Android minimum OS version'.
Configured and assigned correctly via 'Device Compliance — Device password required (Android)'.
Configured and assigned correctly via 'Device Compliance — Valid operating system (Windows)'.
Configured and assigned correctly via 'Device Compliance — Valid operating system (macOS)'.
Configured and assigned correctly via 'Device Compliance — Require compliant device for'.
Configured and assigned correctly via 'App Protection — Android App Protection —'.
Configured and assigned correctly via 'App Protection — iOS APP — block'.
Configured and assigned correctly via 'App Protection — Android APP — block'.
Configured and assigned correctly via 'App Protection — Android APP — offline'.
Configured and assigned correctly via 'App Protection — Android APP — block'.
Configured and assigned correctly via 'Endpoint Security — Windows Defender — real-time'.
Configured and assigned correctly via 'Endpoint Security — Windows Defender — cloud-delivered'.
Configured and assigned correctly via 'Endpoint Security — macOS XProtect — latest'.
Configured and assigned correctly via 'Endpoint Security — Disk encryption — BitLocker'.
Configured and assigned correctly via 'Device Configuration — Disable AutoPlay on all'.
Configured and assigned correctly via 'Device Configuration — Android — block debugging'.
Configured and assigned correctly via 'Enrollment — Autopilot deployment profile —'.
Configured and assigned correctly via 'Enrollment — Enrollment restrictions — require'.
Configured and assigned correctly via 'Device Compliance — macOS minimum OS version'.
Configured and assigned correctly via 'Device Compliance — Device password required (Windows)'.
Configured and assigned correctly via 'Device Compliance — Device password required (macOS)'.
Configured and assigned correctly via 'Device Compliance — Device password required (iOS)'.
Configured and assigned correctly via 'Device Compliance — Defender ATP risk score'.
Configured and assigned correctly via 'Device Compliance — Android Google Play Protect'.
Configured and assigned correctly via 'App Protection — iOS App Protection —'.
Configured and assigned correctly via 'App Protection — iOS APP — require'.
Configured and assigned correctly via 'App Protection — Android APP — require'.
Configured and assigned correctly via 'App Protection — iOS APP — offline'.
Configured and assigned correctly via 'App Configuration — Edge — block personal'.
Configured and assigned correctly via 'App Configuration — Outlook mobile — block'.
Configured and assigned correctly via 'App Configuration — Microsoft Authenticator — require'.
Configured and assigned correctly via 'Endpoint Security — ASR — Block obfuscated'.
Configured and assigned correctly via 'Endpoint Security — ASR — Block persistence'.
Configured and assigned correctly via 'Endpoint Security — Windows Defender — PUA'.
Configured and assigned correctly via 'Device Configuration — Block USB mass storage'.
Configured and assigned correctly via 'Device Configuration — Require TPM 2.0 present'.
Configured and assigned correctly via 'Device Configuration — Secure Boot enabled'.
Configured and assigned correctly via 'Device Configuration — Screen lock timeout —'.
Configured and assigned correctly via 'Device Configuration — Screen lock timeout —'.
Configured and assigned correctly via 'Device Configuration — Block guest account access'.
Configured and assigned correctly via 'Device Configuration — Android — require Work'.
Configured and assigned correctly via 'Update Rings — Windows 10/11 Update Ring'.
Configured and assigned correctly via 'Update Rings — Windows 10/11 Update Ring'.
❓ report-only3
Policy is deployed in report-only mode. Flip to enforced when ready.
Policy is deployed in report-only mode. Flip to enforced when ready.
Policy is deployed in report-only mode. Flip to enforced when ready.
Registry v2.1.0 | Tenant: demo-ver... | Powered by Veri-Tune
