Apple is removing the MDM commands and profiles that many Apple fleets still depend on, and replacing them with declarative device management (DDM) and hardware-backed attestation that most security teams have not yet designed around. In Apple's 2026 schema, the ScheduleOSUpdate command is marked removed in iOS and macOS 27, and several configuration profiles are deprecated in favour of declarations. Managed Device Attestation (MDA) lets a device prove, with a certificate chain rooted in Apple, that it is genuine, which device it is and that its key lives in the Secure Enclave. This guide explains how DDM and MDA work from a security point of view, the privileged roles and tokens around them, what to monitor, and a hardening baseline. It is for endpoint, identity and zero trust engineers running Apple devices through any MDM product, and goes deeper than our Device Trust and Posture Guide.
This is an independent guide from NHI Mgmt Group, based on Apple's public documentation as of November 2026. It is not sponsored or reviewed by Apple. Product features change, so confirm settings against Apple's current documentation.
Key takeaways
- DDM changes who does the work. The server publishes declarations and the device enforces them and reports status on its own, so compliance data arrives as status reports rather than as answers to polling.
- Legacy MDM paths are closing. Apple's device-management schema marks ScheduleOSUpdate deprecated in 26.0 and removed in 27.0, replaced by the software update enforcement declaration; plan the migration now rather than at the next OS release.
- Attestation turns self-reported posture into evidence. MDA returns a certificate chain rooted in the Apple Enterprise Attestation Root CA containing serial number, UDID, OS and Secure Enclave versions and, on macOS 14.2 and later, SIP and secure boot state.
- Hardware-bound ACME certificates stop key theft. An ACME payload with HardwareBound and Attest set to true gives a client certificate whose private key cannot leave the device, which is the strongest device credential Apple offers for Wi-Fi, VPN and zero trust access.
- The MDM console is now a policy engine with wipe rights. Whoever controls declarations controls every enrolled device, so MDM administrator accounts and API credentials need privileged access controls.
How identity and access work in Apple DDM
DDM is an extension of the existing Apple MDM protocol, introduced with iOS 15 and macOS 13, not a separate enrolment. The device enrols with MDM as before, receives a device identity certificate, and then synchronises declarations over the DDM channel. Apple's Platform Deployment guide describes four declaration types.
| Declaration type | What it carries | Security relevance |
|---|---|---|
| Configurations | Settings, accounts, restrictions; for example com.apple.configuration.passcode.settings, softwareupdate.enforcement.specific, security.passkey.attestation | The policy itself; the equivalent of profile payloads |
| Assets | Reference data used by configurations, such as credentials (ACME, SCEP, certificate, identity, user name and password) and user identity | Credentials are fetched by the device from a URL, optionally with a SHA-256 hash and MDM authentication |
| Activations | Groups of configurations and assets applied atomically, with an optional predicate | Predicates on status items (OS version, model, enrolment type) decide where policy applies |
| Management | Organisation information, server capabilities, custom management properties | Custom properties feed predicates, so changing them changes scope |
Status channel. Devices report changes to status items as they happen, send a full report every 24 hours, and the server can subscribe to specific items through a status subscriptions declaration. Security-relevant status items in Apple's schema include passcode.is-compliant, passcode.is-present, diskmanagement.filevault.enabled, security.lockdown-mode, device.operating-system.version, softwareupdate.failure-reason, mdm.enrollment-type and security.certificate.list.
Credential assets. An asset's Authentication type can be MDM, which sends the device identity certificate and any user authentication with the request, or None, a plain GET. Schema documentation states that asset URLs must start with https://. Use MDM authentication for anything secret: an asset URL served with None is retrievable by anyone who learns it.
Managed Device Attestation
MDA is available on iOS 16, iPadOS 16.1, macOS 14 and tvOS 16 or later, on iPhone, iPad and Apple TV with an A11 Bionic chip or later and on Macs with Apple silicon. It works in two ways.
| Mechanism | How it works | Use it for |
|---|---|---|
DeviceInformation query (DevicePropertiesAttestation) | The MDM server requests an attestation, optionally with a DeviceAttestationNonce of up to 32 bytes. The device returns a DER certificate chain rooted in the Apple Enterprise Attestation Root CA. A fresh attestation is generated at most once every 7 days; otherwise the cached one is returned. | Proving to the MDM that the device is genuine and is the device it claims to be; detecting spoofed or cloned enrolments |
ACME device-attest-01 challenge | The device generates a key in the Secure Enclave, answers the ACME challenge with a WebAuthn-style attestation statement, and the CA issues a certificate bound to that key. The attestation freshness value is the SHA-256 hash of the challenge token. | Hardware-bound client certificates for 802.1X, VPN, mutual TLS and zero trust access proxies |
The attestation leaf certificate carries Apple OIDs: serial number (1.2.840.113635.100.8.9.1), UDID (.8.9.2), sepOS version (.8.10.2), freshness code (.8.11.1), and from the 17.2 and 14.2 releases OS version, LLB version and Software Update Device ID. On macOS 14.2 and later it adds SIP status (.8.13.1), secure boot status (Full, Reduced or Permissive Security, .8.13.2) and whether third-party kernel extensions are allowed (.8.13.3). Under User Enrollment, serial number and UDID are omitted to protect privacy. Apple notes that a failed attestation does not say why it failed, because the device is the only source of that information.
Decision guidance. Use DeviceInformation attestation to validate inventory, for example after an OS update or at random intervals, respecting the 7-day limit. Use ACME attestation wherever a device certificate gates access. Small fleets can start with ACME attestation for Wi-Fi and VPN only; large fleets with a zero trust proxy should feed attested properties into a device trust score, and treat a missing or stale attestation as a reason to step down access. See the ACME and Automated Certificate Management Guide.
Enrolment type matters. Several declarations are limited by enrolment: the software update enforcement declaration on macOS is available only to supervised devices, and passkey enterprise attestation on macOS is user-scoped on supervised devices. Personally owned devices in User Enrollment still attest, but without serial number or UDID, so inventory matching has to rely on the enrolment record instead.
Admin roles and privileged access
DDM concentrates control: one declaration with a broad activation predicate reaches every matching device, and the same console usually holds lock, wipe and Activation Lock bypass functions. An administrator account on a device management console can use legitimate wipe actions at scale, so protect those accounts as highly privileged. MITRE ATT&CK tracks this class of abuse as T1072 Software Deployment Tools.
- Apple Business or Apple School Manager: Apple Business Manager is now Apple Business. Its administrator roles can assign devices to MDM servers and download server tokens, so treat them as tier 0, use Managed Apple Accounts federated to your identity provider, and keep the number of holders small.
- MDM roles: separate declaration authors from approvers, and separate both from roles that can issue Erase, Lock or Clear Passcode commands. Require a second approver for bulk destructive actions where the product supports it.
- Scope changes are privileged: editing a management property or predicate can move a fleet in or out of a policy. Put these through the same change control as the declarations themselves.
- Break-glass: keep one emergency MDM administrator account, vaulted, with phishing-resistant MFA and alerting on every use. See the Mobile Device Management Security Guide.
Integrations, API tokens and service accounts
A DDM deployment depends on several non-human credentials, each of which can enrol rogue devices, push policy or issue certificates if stolen.
| Credential | What it allows | Control |
|---|---|---|
| APNs MDM push certificate | Lets the MDM server wake devices; expires and must be renewed with the same Apple account | Hold in a shared, owned organisational account, not a personal one; calendar renewal well before expiry |
| Automated Device Enrollment server token | Links the MDM server to devices assigned in Apple Business or Apple School Manager | Restrict who can download it; rotate when administrators leave |
| MDM product API credentials (OAuth clients, API roles) | Automation of declarations, inventory and commands | Least-privilege API roles, no wipe rights for reporting integrations, short-lived tokens, secrets in a vault |
| ACME and SCEP endpoints and their CA | Issue device certificates trusted by Wi-Fi, VPN and proxies | Require attestation for ACME; for SCEP, use dynamic challenges; restrict issuance to the MDM |
| Identity provider connectors | User lookup, conditional access compliance signals | Dedicated service principals with read scopes; monitor sign-ins |
Inventory these in your non-human identity register with owners and expiry dates. See the Machine Identity, PKI and Certificate Lifecycle Guide.
Logging and detection
- MDM audit log: forward administrator sign-ins, role changes, declaration and activation changes, management property changes and every Erase, Lock, Clear Passcode and Activation Lock bypass action to the SIEM.
- Status reports: alert on transitions that matter:
diskmanagement.filevault.enabledfalse,passcode.is-compliantfalse,softwareupdate.failure-reasonpresent after an enforcement deadline, unexpectedmdm.enrollment-type. - Attestation results: log each attestation validation (chain, freshness, serial match against inventory) and alert on failures, serial mismatches, Reduced or Permissive Security on Macs where Full Security is expected, and SIP disabled.
- Certificate issuance: alert on ACME orders without attestation, SCEP issuance outside the MDM, and certificates issued to serial numbers not in inventory.
- Bulk actions: alert on more than [n] destructive commands in [m] minutes from any account.
Metrics: percentage of devices on DDM-capable OS versions; percentage of access certificates that are hardware-bound and attested; median days from OS release to enforced update; attestation failure rate by model; number of MDM administrators with standing wipe rights; legacy profiles still deployed with a DDM equivalent.
Hardening baseline
Roll out in phases, testing each one on a pilot group defined by an activation predicate before widening it.
- Inventory and readiness: list OS versions, chip families and enrolment types (supervised, device, user). Note devices that cannot attest (pre-A11, Intel Macs) and plan for their replacement or reduced access.
- Lock down the console: privileged roles, phishing-resistant MFA, audit forwarding and API least privilege, before any new policy.
- Software updates: replace ScheduleOSUpdate and older software update profiles with
softwareupdate.enforcement.specific(TargetOSVersion and TargetLocalDateTime). On macOS this declaration requires supervision. Pilot with an IT ring first. - Passcode and encryption: move passcode policy from the deprecated
com.apple.mobiledevice.passwordpolicyprofile topasscode.settings, and subscribe to FileVault and passcode status items. - Attested certificates: deploy ACME assets with HardwareBound and Attest true, have the CA validate attested serials against inventory, then switch Wi-Fi, VPN and access proxies to require them.
- Attestation in posture: add DeviceInformation attestation checks to compliance, starting in report-only mode, then gate access.
- Retire legacy profiles: where the
legacydeclaration wraps an old profile, track it as debt and replace it when a native declaration exists.
Rollback: because activations apply atomically, removing a pilot activation removes its configurations as a group. Keep the previous profile-based policy assigned, but inactive, until the declaration has run cleanly through one OS update cycle.
| Framework | Reference | Fit |
|---|---|---|
| NIST SP 800-53 Rev. 5 | IA-3 Device Identification and Authentication; CM-2, CM-6; CM-8; SI-2; SI-7 | Attested device identity; declarative baseline; inventory; enforced updates; boot integrity evidence |
| NIST CSF 2.0 | PR.AA-03, ID.AM-01, DE.CM-09 | Hardware authenticated; hardware inventory; computing hardware monitored |
| CIS Controls v8.1 | Control 1, Control 4, Control 7 | Asset inventory, secure configuration, continuous vulnerability management |
| MITRE ATT&CK | T1072 Software Deployment Tools | Abuse of the management console itself |
Common misconfigurations
- Treating DDM status as attested: status reports are self-reported by the device. Only an attestation chain validated to Apple's root, with a fresh nonce, is evidence.
- Attest without HardwareBound: the schema requires HardwareBound true when Attest is true; teams that leave keys exportable lose the main protection against certificate theft.
- Requesting fresh attestations constantly: because fresh DeviceInformation attestations are limited to one per 7 days, a check that expects a new one every hour silently receives cached results and may block healthy devices.
- Broad predicates on first deployment: an activation without a predicate applies everywhere; pilot with predicates on a management property.
- Credential assets with Authentication None: anyone with the URL can fetch the payload.
- Personal Apple accounts holding the APNs certificate: when the person leaves, renewal fails and every device must be re-enrolled.
Practitioner checklist
- Inventory OS versions, chips and enrolment types, and flag devices that cannot attest.
- Put Apple Business or Apple School Manager and MDM administrator roles under privileged access controls with phishing-resistant MFA.
- Forward MDM audit logs and alert on bulk destructive commands.
- Register the APNs certificate, ADE server token, API clients and CA endpoints as owned non-human identities with expiry dates.
- Replace ScheduleOSUpdate with the software update enforcement declaration before devices reach 27.0.
- Move passcode policy to the passcode settings declaration and subscribe to FileVault and passcode status.
- Issue hardware-bound, attested ACME certificates and require them for Wi-Fi, VPN and access proxies.
- Validate attestation chains, nonces and serials against inventory, and alert on Reduced Security or SIP disabled on Macs.
- Pilot every new activation with a predicate, and keep the previous policy available for rollback for one update cycle.
Standards and references
- Apple: Intro to declarative device management (Apple Platform Deployment)
- Apple: Managed Device Attestation (Apple Platform Deployment)
- Apple: device-management schema repository (declarations, status items, MDM commands)
- Apple: Apple Business Manager is now Apple Business
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
- NIST: Cybersecurity Framework 2.0
- MITRE ATT&CK: Software Deployment Tools
Related NHI Mgmt Group resources: Device Trust and Posture Guide · iOS and iPadOS Enterprise Security Guide · macOS Security Guide for Enterprises · Jamf Guide · macOS Platform SSO and Directory Binding Guide