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.

Enforcement Map: every device setting traced to the control that requires it

The Enforcement Map answers the auditor’s question, “show me that this control is in place on every laptop”, in one view. It is part of Shadow MDM, in Shadow Hub and in Meridian.

Each row traces a requirement all the way down to the devices:

Framework → control → rule → setting → devices → evidence

For example: ISO/IEC 27001 → A.8.1 User endpoint devices → disk encryption → FileVault on macOS, BitLocker (XTS-AES-256) on Windows, LUKS on Linux (reported) → 41 of 43 devices passing → posture history and signed receipts for each change.

The device counts are an illustration.

FieldWhat it tells you
CIA impactHow much the rule protects confidentiality, integrity and availability (0–3 each), and a CIA score for the whole workspace
Required byEvery framework control that asks for it, for example ISO 27001 A.8.1, SOC 2 CC6.1, PCI DSS 3.5.1
ModeEnforced on devices, or report-only (the minimum is known but not yet approved)
StrictnessAt the framework minimum, or stricter because you approved a tighter Proposal
DevicesPassing, failing and unknown, per platform
Approved byWho approved it, when, and through which Proposal (in Hub or Meridian)
ExceptionsDevices excluded, the reason, who accepted the risk, and when it expires
HistoryEvery blueprint version that changed it, by whom

Each control in a framework gets one status: enforced, partial, not enforced or out of scope. A device MDM cannot cover HR screening or supplier contracts; those controls are marked out of scope rather than quietly left off, so the map never overstates coverage.

Pick any past date to see the map as it was: blueprint version, device posture, exceptions in force. Useful for audit periods (“was disk encryption enforced from 1 January?”) and for incident reviews.

Invite an auditor from Shadow Hub with their name and email. They get a one-time sign-in link, valid for 72 hours, and a read-only role: they can open the map, device evidence, history and exports, and cannot approve, decline or change anything.

Export the map per framework as JSON or CSV. Exports are signed by Shadow Hub (Ed25519, the same key that signs blueprints and activity receipts), so the file your auditor receives can be verified as the one Hub produced.

The same results feed the Evidence API as six endpoint controls, SHD-08 to SHD-13 (disk encryption; lock and authentication; patching; malware protection and firewall; baseline and approved changes; AI tools governed). Posture-based evidence is included in Shadow Hub; it is marked as enforced by Shadow MDM once you approve and roll out the matching settings.

See the full rule-to-control mapping.

Frequently asked questions

Can our auditor see the map without an admin account?

Yes. Invite the auditor by email from Shadow Hub; they get a one-time sign-in link and a read-only auditor role. They can view the map, history and exports, and cannot approve or change anything.

Can we show the state on a past date?

Yes. Hub keeps a daily history of each device's posture and every blueprint version, so you can view the map as it was on any past date, for example the first day of the audit period.

How do we know an export has not been edited?

Exports (JSON or CSV, per framework) are signed by Shadow Hub with the same Ed25519 key that signs blueprints and receipts, so anyone can check that the file is the one Hub produced.

Does the map claim we are compliant?

No. It shows which endpoint controls are enforced, partly enforced, not enforced or out of scope for a device MDM. Compliance depends on your whole programme; the map is evidence for the endpoint part.