Skip to content
Install Core free
ProductsCompare Core, Hub, Connect and MDM pricing
Solutions
Docs
ResearchPricing
CompareCompare all AI data-leak tools
TrustBenchmarks
Start 30-day free trial

Shadow Hub for your business

Tell us about your team and we'll help you get started.

We use these details only to reply to your enquiry. No newsletter, no cookies, no trackers.

Compliance blueprints: framework minimums for every laptop

A blueprint is the set of settings Shadow MDM enforces on your devices. You do not write it rule by rule: you pick the frameworks your organisation follows, and Shadow compiles the blueprint from each framework’s minimum, plus any stricter Proposals you approved, minus exceptions you accepted. Every approved change makes a new, signed blueprint version.

Shadow groups rules into two building blocks, then adds framework-specific requirements.

  • Endpoint baseline (ISO 27001, SOC 2, GDPR; also part of PCI DSS and HIPAA): disk encryption, screen lock after 15 minutes, host firewall, automatic OS updates, OS supported and patched (critical patches within 14 days, at most one major version behind), anti-malware with current definitions, no day-to-day admin account, local passwords of at least 8 characters, removable storage reported, remote-wipe readiness, software inventory, CIS Level 1 hardening.
  • AI blueprint (ISO 42001, EU AI Act): Shadow agent installed and tamper-protected, AI traffic through Shadow, personal data masked before AI, only approved AI tools, extensions and MCP servers, local model runtimes reported, software inventory.
RuleISO 27001SOC 2GDPRPCI DSS v4.0.1HIPAAISO 42001EU AI Act
Disk encryption, recovery key escrowed✓✓✓✓✓
Screen lock after idle15 min15 min15 min15 min10 min
Host firewall on✓✓✓✓✓
Automatic OS updates✓✓✓✓✓
Critical patches within14 days14 days14 days14 days14 days
Anti-malware definitions at most3 days old3 days old3 days old1 day old3 days old
No daily admin account✓✓✓✓✓
Local password length888128
Removable storagereportreportreportreportreport
Remote lock and wipe ready✓✓✓✓✓
Software inventory✓✓✓✓✓✓✓
CIS benchmark hardeningLevel 1Level 1Level 1Level 1Level 1
Shadow agent tamper-protected✓✓
AI traffic through Shadow✓✓
Personal data masked before AIstandardstandard
Approved AI tools only✓✓
Local model runtimesreportreport

PCI DSS also allows critical patches within 30 days; because the merge keeps the strictest value, the endpoint baseline’s 14 days applies when PCI DSS is combined with it.

When you follow more than one framework, Shadow merges them per rule and keeps the strictest value: the shortest idle time and patch window, the longest password, block over report for removable storage, strict over standard masking, approve over report for local model runtimes. A workspace on ISO 27001, HIPAA and PCI DSS gets a 10-minute screen lock, 12-character passwords and daily anti-malware definitions.

When you select ISO/IEC 42001, the AI blueprint is always on. It is where Shadow MDM differs most from a traditional MDM: the same agent that masks data going to AI enforces the AI controls, so you can show that AI traffic goes through Shadow, that personal data is masked, and that only approved AI tools and MCP servers are in use. See ISO 42001 for AI on laptops.

The CIS Benchmarks define two hardening profiles.

CIS Level 1 (default)CIS Level 2 (“Strict”, optional)
GoalPractical hardening with little impact on daily workDefence in depth for high-security environments
macOS examplesGatekeeper on, System Integrity Protection on, guest account off, sharing services offLevel 1, plus Bluetooth sharing and AirDrop off, and more
Windows examplesSmartScreen on, guest account off, SMBv1 offLevel 1, plus further restrictions
Proposed as a minimumYes, for ISO 27001, SOC 2, GDPR, PCI DSS and HIPAANever; an admin chooses it
DisruptionLowCan break everyday workflows

Shadow proposes Level 1 because the frameworks ask for a hardening baseline, not for the strictest profile. If your risk assessment calls for Level 2, choose the Strict option; Shadow then writes Proposals for the extra settings, rolled out like any other change.

On top of the minimum, Shadow proposes tighter settings where the data says so. Laptops whose AI traffic is the most sensitive can get, for example, a 5-minute screen lock, blocked removable storage and strict masking. These are Proposals too: you approve them, scoped to those devices only.

Each rule maps to native settings on macOS, Windows and Linux. Two limits today:

  • macOS remote lock and wipe need the Apple MDM protocol; Shadow’s Apple MDM certificate is pending. Until then, the remote-wipe check on Macs reports as not ready and lock uses the Shadow agent’s lock screen.
  • Linux disk encryption (LUKS) is report-only. Some other Linux checks, such as password policy and anti-malware, are report-only as well.

Next: the Enforcement Map and the rule-to-control mapping.

Frequently asked questions

Can a model lower a framework minimum?

No. The minimum comes from the frameworks your workspace follows and is fixed. Models only decide how, when and for which devices a setting lands, and can propose stricter settings, never weaker ones.

Why is CIS Level 1 the default and not Level 2?

CIS Level 1 is the practical hardening baseline that rarely gets in people's way. Level 2 adds settings, such as turning off Bluetooth sharing and AirDrop, that can break everyday work. Shadow never proposes Level 2 as a minimum; an admin can choose it as the Strict option.

What if we need an exception for one laptop?

Decline the Proposal for that device with a reason. Shadow records it as an exception (a risk acceptance) with who decided and when, removes it from that device's blueprint and shows it on the Enforcement Map.

Do blueprints cover every control in ISO 27001 or SOC 2?

No. A device MDM covers endpoint controls only. Controls it cannot cover are marked out of scope on the Enforcement Map, so coverage is stated honestly.