Join our Newsletter — 33% off our NHI Course
Home› Guides› Apple Security Updates in the Enterprise: Enforce Patches…
Guide Vulnerability Management

Apple Security Updates in the Enterprise: Enforce Patches with Declarative Management

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 14 min read
On this page

Apple devices patch themselves well when left alone, but enterprise controls such as deferrals, user choice and legacy update payloads can quietly hold a fleet weeks behind Apple's security releases. This guide covers how to enforce Apple security updates across iPhone, iPad and Mac using declarative device management (DDM): the software update settings and enforcement declarations, deferral design, Background Security Improvements, deadline behaviour, status reporting and the retirement of older update payloads. It is written for endpoint, mobility and vulnerability management teams who already run an Apple fleet through a device management service and need a measurable patch deadline. Wider DDM architecture, attestation and console security are covered in the Apple Declarative Device Management and Managed Device Attestation Guide; this page stays on updates.

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

  • One enforcement declaration sets the deadline. com.apple.configuration.softwareupdate.enforcement.specific installs a named OS version at a local date and time, regardless of deferrals.
  • Settings and enforcement are separate jobs. com.apple.configuration.softwareupdate.settings controls deferrals, automatic actions, Background Security Improvements and notifications; enforcement declarations set deadlines.
  • Background Security Improvements follow the minor release. They ignore the managed deferral but apply only to the latest minor OS version, so a long minor-update delay also holds them back.
  • Legacy update controls are retiring. Apple's schema marks the com.apple.SoftwareUpdate payload and the restriction-based deferral keys deprecated in 26.0 and removed in 27.0.
  • Measure from device status, not policy. The softwareupdate.* status items and the supplemental version keys show what each device actually runs.

The Apple update model in brief

Apple ships four kinds of release that matter to a patch programme, and DDM treats them differently. Apple lists security content for software updates and for Background Security Improvements on its Apple security releases page, and states that it does not disclose or confirm security issues until an investigation is complete and patches are generally available. In practice that means you learn about a fix at the moment it ships, so the enforcement process has to be ready in advance.

Release typeExampleManaged deferral appliesDDM control
Major upgradeA new major versionYes: MajorPeriodInDays on macOS; CombinedPeriodInDays on iOS and iPadOSDeferral, RecommendedCadence, enforcement
Minor updatex.y to x.y+1Yes: MinorPeriodInDays on macOS; CombinedPeriodInDays on iOS and iPadOSDeferral, automatic install, enforcement
Background Security ImprovementVersion with a letter suffix, such as (a)NoRapidSecurityResponse dictionary (Enable, EnableRollback), enforcement with TargetBuildVersion
Non-OS update (macOS)Safari, XProtect, printer drivers, Xcode command line toolsYes: SystemPeriodInDaysInstallSecurityUpdates for security data such as XProtect and Gatekeeper

Apple notes that over-the-air updates are typically available for up to 180 days after release, which bounds how long an older approved version can stay deployable. Apple's schema describes the Background Security Improvements dictionary under the key name RapidSecurityResponse, carried over from the earlier Rapid Security Response mechanism; the setting names are what you will see in management consoles.

The software update settings declaration

The settings declaration requires iOS 18, iPadOS 18 or macOS 15 and supervision, except for the enforcement-related keys and the beta OfferPrograms keys. It is a combined declaration: when several apply, Apple's rules decide which value wins, so design one baseline and a small number of override rings rather than stacking many.

KeyPlatformValues (Apple default)Security baseline suggestion
AutomaticActions.DownloadAllAllowed, AlwaysOn, AlwaysOff (Allowed)AlwaysOn, so updates are staged before a deadline
AutomaticActions.InstallOSUpdatesAllAllowed, AlwaysOn, AlwaysOff (Allowed)AlwaysOn for general fleets; Allowed for rings where enforcement dates control timing
AutomaticActions.InstallSecurityUpdatesmacOSAllowed, AlwaysOn, AlwaysOff (Allowed)AlwaysOn
RapidSecurityResponse.EnableAlltrue or false (true)true
RapidSecurityResponse.EnableRollbackAlltrue or false (true)false for most users; true in the IT pilot ring
Deferrals.CombinedPeriodInDaysiOS, iPadOS, tvOS1 to 907 or less for minor updates in the general ring
Deferrals.MinorPeriodInDaysmacOS1 to 907 or less
Deferrals.MajorPeriodInDaysmacOS1 to 90Set by application compatibility testing, commonly 30 to 90
Deferrals.SystemPeriodInDaysmacOS1 to 90Short, so Safari fixes are not held
AllowStandardUserOSUpdatesmacOStrue or false (true)true, unless shared Macs need an administrator to authorise
NotificationsAlltrue or false (true)true for most fleets; false only for kiosks and shared devices

For the AutomaticActions keys, Apple states that when several declarations set the same key the last value in the order Allowed, AlwaysOn, AlwaysOff takes precedence, so an AlwaysOff anywhere wins. The RapidSecurityResponse values are combined with a logical AND, so a single declaration setting Enable to false switches Background Security Improvements off for that device. Audit every declaration that reaches a device, not only the baseline.

Deferral design

  • Separate major from minor: on macOS, a 60 day MajorPeriodInDays for compatibility testing can coexist with a short MinorPeriodInDays. On iOS and iPadOS one CombinedPeriodInDays value covers both, so pair it with RecommendedCadence set to Oldest to keep users on the current major version while still receiving its minor updates.
  • Remember the knock-on effect: Apple states that Background Security Improvements apply only to the latest minor OS version, so delaying that minor update effectively delays them too. A 30 day minor deferral means a 30 day wait for any improvement built on that release.
  • Use deferrals for visibility, enforcement for deadlines: a deferral only hides an update for a period; it never installs anything. A deadline needs an enforcement declaration.

Enforcing an update by deadline

The softwareupdate.enforcement.specific declaration is available from iOS 17, iPadOS 17, macOS 14, tvOS 18.4 and visionOS 26. On macOS it requires a supervised device; on iOS and iPadOS it also works with Device Enrollment.

KeyRequiredPurpose
TargetOSVersionYesThe OS version to reach, for example 26.1
TargetBuildVersionNoA specific build, which can include a supplemental identifier such as a trailing letter; needed to enforce a Background Security Improvement
TargetLocalDateTimeYesDeadline in yyyy-mm-ddThh:mm:ss, device local time, no offset
DetailsURLNoYour page explaining the update to users

Behaviour to plan around

  • Local time: the deadline is relative to each device's time zone, so a 17:00 deadline rolls round the world. Choose a local time outside working hours.
  • Notifications: users are told in Settings or System Settings and can install early. Do Not Disturb is ignored during the 24 hours before enforcement. With Notifications set to false, only the one hour warning and the restart countdown appear.
  • At the deadline: iOS and iPadOS ask for the passcode if one is set; macOS force quits all open apps, including those with unsaved documents, and restarts if needed. Apple silicon Macs use the bootstrap token if available, otherwise they prompt for credentials. Tell users this before the first enforced Mac deadline.
  • Missed deadlines: if the device is off at the deadline, Apple's schema says enforcement happens one hour after restart, or once conditions such as minimum battery are met.
  • Exact versions only: the device installs the version you name and will not install a later patch if only a minor version is set. If the target is not available from Apple's GDMF service (gdmf.apple.com/v2/pmv), the configuration stays active but cannot update. Remove declarations for versions Apple no longer offers.
  • Supplemental releases need the base: a build with a letter suffix installs only on a device already at its base version. To move an older device, use two declarations: one to the base version, then one to the supplemental build.

Enforcing Background Security Improvements

Apple's guidance is to set both TargetOSVersion and TargetBuildVersion in the enforcement declaration, taking the build number from Apple's Software Lookup Service page. The enforcement declaration can install an improvement even where Enable is false. Mac laptops must be on power or have at least 10% battery on Apple silicon or 20% on Intel. Improvements that touch the OS need a restart; on a Mac, Safari may pick up content after a relaunch. Later minor updates include all improvements issued for the prior version, so a fleet that keeps up with minor releases also stays current on improvements.

Moving off legacy update controls

Apple's device management schema marks the profile payload and restriction keys below deprecated in 26.0 and removed in 27.0, and the ScheduleOSUpdate command is on the same retirement path, as covered in the DDM guide. Plan the move while both paths still work, test it in a ring and keep the old profile available for one cycle in case of rollback.

Legacy controlPlatformReplacement
com.apple.SoftwareUpdate profile payloadmacOSsoftwareupdate.settings declaration
forceDelayedSoftwareUpdates and enforcedSoftwareUpdateDelay restrictionsiOS, iPadOS, macOS, tvOSDeferrals keys in the settings declaration
forceDelayedMajorSoftwareUpdates restrictionmacOSMajorPeriodInDays
enforcedSoftwareUpdateMinorOSDeferredInstallDelay restrictionmacOSMinorPeriodInDays
ScheduleOSUpdate MDM commandiOS, iPadOS, macOSsoftwareupdate.enforcement.specific declaration (see the DDM guide)

Two details catch teams out. First, macOS settings and enforcement through DDM need supervision, so Macs enrolled manually without Automated Device Enrollment need a re-enrolment plan before 27.0. Second, a device that still carries both a legacy deferral profile and a DDM deferral is harder to reason about; remove the legacy profile once the declaration is confirmed in status reports.

Rollout plan

  1. Inventory: list devices by OS version, supervision status and enrolment type. Flag Macs that are not supervised, because they cannot take macOS update settings or enforcement declarations.
  2. Set the minimum at enrolment: on iOS 17, iPadOS 17 and macOS 14 or later, enforce a minimum OS during Automated Device Enrollment so new and reset devices start current.
  3. Define rings: IT pilot (no deferral, rollback allowed), early adopters (short deferral), general fleet, and a small exceptions ring for devices with validated compatibility constraints, each with an owner and an expiry date.
  4. Deploy the settings baseline in the pilot ring: confirm status reports show automatic downloads and Background Security Improvement settings applied, then widen ring by ring.
  5. Write the enforcement runbook: on each Apple security release, a named person creates the enforcement declaration for each ring with dates agreed in advance, for example pilot within 2 days, general fleet within 7 to 14 days. Align the targets with your patch policy and the Patch Management Guide.
  6. Remove legacy controls: once a ring is stable on declarations, remove its legacy software update profile and restriction keys.
  7. Roll back safely: to pause, withdraw the enforcement declaration from the affected ring and raise the deferral for that ring only. Apple OS updates are not normally reversible on the device, so pausing before broad enforcement is the main rollback lever; for an improvement, a pilot ring with EnableRollback true lets users remove it while you assess.

Decision guidance

  • Small fleets without dedicated Apple staff: keep automatic download and install AlwaysOn, use short or no minor deferrals, and enforce only when a release fixes an issue you must close by a date. Apple's defaults do most of the work.
  • Large or regulated fleets: use rings, an enforcement declaration per release per ring, and the status items as audit evidence. Regulators and auditors ask for proof of patch timeliness, which the status data supplies.
  • Shared Macs and kiosks: consider AllowStandardUserOSUpdates false so an administrator authorises updates, schedule deadlines out of hours, and set Notifications false. For Shared iPad, users must be signed out before an update.
  • High-risk users: put executives and administrators in the early ring, not the exceptions ring. Pair fast updates with the protections in the Apple Lockdown Mode Guide.
  • Personally owned devices: User Enrollment limits what can be enforced. Use device compliance checks on OS version for access decisions instead. See the Conditional Access Guide.

Where identity fits

Update enforcement touches identity in three places. The bootstrap token escrowed at enrolment lets Apple silicon Macs authorise updates without user credentials, so check escrow status as part of patch readiness. The device management service's API credentials and administrator accounts can create or withdraw enforcement declarations for the whole fleet, so treat them as privileged non-human identities with owners, rotation and logging. And OS version from status reports is a useful device trust signal: block or step up access when a device misses its deadline by more than a set grace period. See the macOS Security Guide for Enterprises.

Detection and measurement

Status itemWhat it showsUse
device.operating-system.versionCurrent OS versionPatch currency per ring
StatusDeviceOperatingSystemSupplementalExtraVersion and StatusDeviceOperatingSystemSupplementalBuildVersionInstalled Background Security ImprovementImprovement coverage
softwareupdate.pending-versionPending OS and build version, and target local date-timeDevices queued for a deadline
softwareupdate.install-statenone, downloading, prepared, installing, failedProgress tracking before the deadline
softwareupdate.failure-reasonFailure count, reason and timestampAlert on repeated failures
softwareupdate.install-reasonWhat triggered the update, for example declaration, auto-update or system-settingsShows whether users or enforcement are doing the patching

Forward status changes to the SIEM or reporting store and alert on: a failure count above 2 for the same version, any device past its deadline by more than 24 hours, any declaration in scope that sets Enable false or InstallSecurityUpdates AlwaysOff, and devices that stop reporting status.

  • Time to patch: median and 95th percentile days from Apple release to installation, per ring.
  • Deadline compliance: percentage of devices on the target version within 24 hours of the enforcement deadline.
  • Improvement coverage: percentage of eligible devices on the latest Background Security Improvement within 72 hours.
  • Exception debt: number of devices in the exceptions ring and the share past their expiry date.
  • Legacy residue: devices still carrying deprecated update payloads or restriction keys, trending to zero before 27.0.
  • Unsupervised Macs: count of Macs that cannot receive macOS update declarations.

Framework mapping

Control areaNIST SP 800-53 Rev. 5NIST CSF 2.0CIS Controls v8.1ISO/IEC 27001:2022 Annex A
Timely OS and security updatesSI-2PR.PS-02, ID.RA-017.3A.8.8
Update baseline and ringsCM-2, CM-3PR.PS-024.1A.8.9, A.8.32
Device and version inventoryCM-8ID.AM-011.1A.5.9
Status monitoring and alertingRA-5, AU-2DE.CM-097.5A.8.16

Common failure patterns

  • Long minor deferrals that stall improvements: a 30 to 90 day minor delay set for compatibility also delays every Background Security Improvement on that release.
  • A stray AlwaysOff or Enable false: combined declarations mean one forgotten test declaration can switch off automatic security updates for every device it reaches.
  • Enforcing a version Apple no longer offers: the declaration stays active and devices never update. Retire declarations as new versions ship.
  • Supplemental build targeted at old devices: devices below the base version cannot take a lettered build; they need a two-step enforcement.
  • Surprise Mac restarts: users lose unsaved work at the deadline because nobody told them macOS force quits apps. Publish a DetailsURL page and use out-of-hours deadlines.
  • Unsupervised Macs left behind: manually enrolled Macs miss macOS update declarations and will lose legacy controls at 27.0.

Practitioner checklist

  • Inventory devices by OS version, supervision and enrolment type, and plan re-enrolment for unsupervised Macs.
  • Enforce a minimum OS during Automated Device Enrollment.
  • Deploy one softwareupdate.settings baseline with automatic download and security install AlwaysOn and short minor deferrals.
  • Keep RapidSecurityResponse.Enable true everywhere and EnableRollback false outside the pilot ring.
  • Run an enforcement runbook per Apple security release with ring deadlines agreed in advance.
  • Use two declarations to bring older devices to a supplemental build.
  • Remove deprecated software update payloads and restriction keys before devices reach 27.0.
  • Alert on update failures, missed deadlines and any declaration that disables security updates.
  • Report time to patch and deadline compliance per ring each month.

Standards and references

Related NHI Mgmt Group resources: Apple Declarative Device Management and Managed Device Attestation Guide · iOS and iPadOS Enterprise Security Guide · macOS Security Guide for Enterprises · Patch Management Guide · Vulnerability Management Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.