macOS Release History: Security Changes From Big Sur to macOS 27

Apple has shipped seven major macOS releases since Big Sur: Big Sur 11 (November 2020), Monterey 12, Ventura 13, Sonoma 14, Sequoia 15, Tahoe 26 and macOS 27 Golden Gate (14 September 2026), which runs only on Apple silicon. Big Sur sealed the system volume with a cryptographic signature and moved kernel extensions behind a reboot and a security downgrade. Later releases added Lockdown Mode, Rapid Security Responses (now Background Security Improvements), a harder Gatekeeper override and terminal paste protections.

If you only need the support picture: as of this writing (23 October 2026), Apple's September 2026 security updates covered Golden Gate 27, Tahoe 26 and Sequoia 15. Sonoma 14 last received a security update on 6 August 2026, and Ventura, Monterey and Big Sur no longer receive security fixes. Tahoe is the last release that runs on any Intel Mac.

Key takeaways

• Apple supports roughly three releases at a time. The newest release gets every fix. The two before it get security updates, but Apple states that not all known issues are fixed in older versions because of architecture and system changes.
• Each release has been patched for a little under three years. Big Sur, Monterey, Ventura and Sonoma each received their last security update with CVE entries about two years and nine to eleven months after release.
• Big Sur was the structural change. The signed system volume (SSV) put every byte of the operating system under an Apple signature, checked at boot and on every read. On Apple silicon, startup security became a per operating system policy tied to the Mac's chip.
• Kernel extensions became a last resort. Since macOS 11, third party kexts load only at boot from an Auxiliary Kernel Collection, and on Apple silicon only after a user lowers security from recovery mode with an administrator password.
• Fast security fixes went through two designs. Rapid Security Responses arrived in the Ventura era. Background Security Improvements replaced them from macOS 26.1, delivered through sealed disk images called cryptexes that can be patched and removed without resealing the system volume.
• Gatekeeper, notarisation and XProtect are three layers, not one. Notarisation and Gatekeeper stop known malware before first launch, revocation tickets block it later, and XProtect detects and removes known malware with signatures Apple updates daily, outside of operating system updates.
• macOS 27 dropped Intel. Its compatibility page and security advisory list only Apple silicon Macs and the MacBook Neo. Intel fleets now live on Tahoe 26 or Sequoia 15, with a finite patch window.
• Everything in this post can be checked from Terminal. The walkthrough below uses sw_vers, softwareupdate, csrutil, spctl, xprotect and fdesetup to read the real state rather than the Settings summary.

This post is the macOS companion to our Windows 11 version history and security changes. If you are reinstalling an older machine, see how to install macOS on an Intel Mac. If you are retiring one, see deep clean and secure delete on macOS. How third party apps sign their own updates is covered in how Sparkle signs macOS app updates.

macOS releases since Big Sur: dates, Macs and patch windows

Three Apple pages are the authority here. The Apple security releases page and its yearly archives list every update with its date and the Macs it covers. The Find out which macOS your Mac is using page lists the latest version of each release. And each release has its own compatibility page listing the Mac models it installs on.

Apple changed its numbering partway through this period. After Sequoia 15, the next release was numbered 26 (Tahoe), and the one after that is 27. Apple's own pages name the newest release "macOS 27 Golden Gate" on some pages and "macOS Golden Gate 27" on others; they are the same release.

Timeline table

Two oddities in that table are worth explaining. Big Sur shows 11.7.11 as its latest version, but Apple's releases page lists 11.7.11 (2 February 2026) with the note "This update has no published CVE entries," alongside a Security Update 2026-001 for Catalina with the same note. Those were maintenance updates for very old releases, not a return to security support. The last Big Sur update with security content was 11.7.10 in September 2023.

The second is Sonoma. Apple never announces an end of support date for macOS. What you can see is the pattern: on 14 September 2026, the day Golden Gate 27 shipped, Apple released security updates for Tahoe (26.7) and Sequoia (15.8) but not Sonoma. On 28 September the same two older releases got 26.7.1 and 15.8.1. Sonoma's last update so far is 14.8.9 from 6 August 2026. Every earlier release followed the same pattern and never got another security update after it fell out of the top three, so plan on Sonoma being finished.

How long Apple patches each release

Measured from each release's first public build to its last update with CVE entries:

That is a working rule of thumb, not an Apple commitment. Apple publishes no lifecycle page for macOS the way some vendors do. The practical takeaway for a fleet is that any given release is safe to run for about two years after the next one ships, and only the newest release receives every fix.

Which Macs each release supports

Apple's compatibility pages list exact models. The table below gives the oldest model in each family. Big Sur, Monterey and Ventura's pages are marked by Apple as archived and no longer updated.

Golden Gate's compatibility page puts it plainly: if you have a Mac with Apple silicon, you can upgrade to macOS 27. It also lists a new model family, the MacBook Neo (13-inch, A18 Pro), and the Golden Gate security advisory lists "MacBook Neo (2026)" first in its supported devices.

What Big Sur changed: the sealed system, Apple silicon boot and kexts

Big Sur arrived in November 2020 alongside the first Apple silicon Macs. Three changes from that release still define how macOS security works.

The signed system volume

Catalina (10.15) had already split the system into a read-only volume. According to Apple's Platform Security guide page on the signed system volume, macOS 11 added strong cryptographic protection on top of it. Here is how it works in Apple's own description:

1. Every piece of system file data is hashed with SHA-256, and the hashes are stored in the file system metadata tree.
2. That tree is itself hashed, node by node, like a Merkle tree. The root hash is called the seal, and it covers every byte on the system volume.
3. Apple signs the seal. During install and update, macOS recomputes the seal on the Mac and checks it against the signed value.
4. On Apple silicon, the bootloader checks the seal before handing control to the kernel. On an Intel Mac with a T2 chip, the bootloader passes the measurement and signature to the kernel, which checks the seal before mounting the root file system.
5. At run time, data is hashed on every read and compared with the expected value. A mismatch means the data is treated as tampered with and is not returned to the program that asked for it.

If verification fails at boot, startup halts and the user is asked to reinstall macOS. The guide also notes two side effects that matter to administrators. Because the system volume is now protected at rest by the seal, it no longer needs to be encrypted; FileVault still encrypts the user's data volume. And macOS refuses to let a user turn off the SSV while FileVault is on, because an unsealed system could be tampered with to steal encrypted data on the next boot.

The SSV is also why macOS updates look the way they do now. Updates use APFS snapshots, so a failed update can fall back to the old system without a reinstall, and the system you boot is a snapshot rather than a writable volume. Code signing still applies on top: the SSV protects bytes as they are read, and code signing protects code as it is mapped into memory to run.

Apple silicon boot security

On Intel Macs, firmware and boot security settings applied to the whole machine. On Apple silicon, Apple's Startup Disk security policy page explains that security policies are set per installed operating system, so two copies of macOS on the same Mac can have different policies. There are three levels:

Full Security works like iOS. When an update is prepared, macOS asks Apple's signing server for a signature that includes the Mac's Exclusive Chip Identification (ECID). The result is valid only on that Mac. Apple's secure software updates page explains why: the server can refuse to sign old versions with known vulnerabilities, so an attacker cannot take a vulnerable older macOS from one Mac and install it on another. It is also why a Mac with Apple silicon, or an Intel Mac with a T2 chip, always needs a network connection to Apple to update.

Changes that would weaken security need physical presence. You enter recoveryOS by holding the power button at startup, which software cannot fake. Apple says this is also why Apple silicon Macs do not need or support a firmware password: every critical change is already gated by user authorisation at the machine.

Kernel extensions move behind a reboot

Apple's kernel extension page describes the macOS 11 change. Third party kexts can no longer load into the kernel on demand. Instead they are merged into an Auxiliary Kernel Collection (AuxKC) that loads during boot. Rebuilding it needs the user's approval and a restart.

On Apple silicon the bar is higher:

• The user must boot into recovery (Apple calls this One True Recovery, or 1TR) by holding the power button, lower the policy to Reduced Security, tick the box to allow kernel extensions and enter an administrator password.
• A SHA-384 hash of the user approved kext list is stored in the LocalPolicy, and only kexts on that list are built into the AuxKC.
• If System Integrity Protection is on, each kext's signature is checked. If SIP is off, it is not.
• The AuxKC's measurement is signed by the Secure Enclave and verified by iBoot at startup.

Apple's guidance is blunt: kexts are no longer recommended for macOS. Since Catalina, developers have had user space alternatives, namely DriverKit for drivers, Endpoint Security for security agents and Network Extension for VPN and network tools. Apple says third party security agents should only be used if they use these APIs or have a clear plan to move to them.

System Integrity Protection still underpins all of it

SIP predates Big Sur (it has been on by default since OS X 10.11), but it is worth restating because so much depends on it. According to Apple's SIP page, SIP uses mandatory access controls to make critical system locations read-only for every process, including those running as root. On Apple silicon it sits alongside Kernel Integrity Protection, a hardware feature that stops the kernel being modified in memory. On an Intel Mac, turning off SIP removes protection for every partition on the drive.

What each release added

The list below covers the security changes that Apple documents for each release. Where Apple's documentation does not tie a feature to a specific version, we say so rather than guess.

Monterey 12 (October 2021)

Monterey kept Big Sur's architecture. It dropped the 2013 and 2014 MacBook Air, MacBook Pro and iMac models, while keeping the Mac mini (Late 2014) and Mac Pro (Late 2013). Its security story is mostly continuity: SSV, AuxKC and per OS boot policies carried forward to a wider range of Apple silicon Macs, including the 14-inch and 16-inch MacBook Pro models from 2021. Monterey was also the last release where Mac settings lived in System Preferences; Apple's secure software updates page notes that from macOS 13, updates are found in System Settings.

Ventura 13 (October 2022)

Ventura was a large security release.

• Lockdown Mode. Apple's About Lockdown Mode page describes it as an optional, extreme protection for the very few people who may be personally targeted by sophisticated threats such as mercenary spyware. It is available in macOS Ventura or later. When it is on, most message attachment types are blocked, some complex web technologies are switched off, incoming FaceTime calls from people you have not called in the last 30 days are blocked, configuration profiles cannot be installed and the Mac cannot be enrolled in device management. On a Mac laptop with Apple silicon, connecting an accessory needs the Mac to be unlocked and an explicit approval.
• Rapid Security Responses. Apple's 2022 to 2023 security archive lists Rapid Security Responses for Ventura, for example "macOS Ventura 13.4.1 (a)" on 10 July 2023 and "13.4.1 (c)" on 12 July 2023. These were small fixes that could be applied between point releases. They are covered in detail below because they were later replaced.
• System Settings. System Preferences became System Settings, which moved where admins and users find security controls.
• Newer hardware floor. Ventura dropped every Mac older than 2017, including the Mac Pro (Late 2013) and the 2015 and 2016 laptops that Monterey still supported.

Sonoma 14 (September 2023)

• More Lockdown Mode protections. Apple's Lockdown Mode security page states that additional protections arrived in iOS 17, iPadOS 17 and macOS 14. The categories Lockdown Mode affects include background services, connectivity, device management, FaceTime, Game Center, Mail, Messages, Photos, Safari, System Settings and WebKit.
• Minimum OS at enrolment. Apple's software update enforcement page says that from macOS 14, a device management service can require a minimum macOS version during Automated Device Enrollment. A new Mac that is behind is walked through an update before Setup Assistant finishes, so it never reaches a user unpatched.

Sequoia 15 (September 2024)

• Gatekeeper override moved into Settings. Apple's developer news post on runtime protection in macOS Sequoia says users can no longer Control-click to override Gatekeeper when opening software that is not signed correctly or notarised. They have to go to System Settings, then Privacy and Security, review the security information and choose to open it there. Apple's Safely open apps on your Mac page describes the current flow: try to open the app, then use the Open Anyway button in Privacy and Security, then confirm.
• Gatekeeper bypass events for security tools. Apple's malware protection page says that from macOS 15, developers using the Endpoint Security API can receive an event when a user bypasses Gatekeeper to run a program. The same API also reports XProtect detections, including the file and the signature involved. The built in eslogger tool shows the same events locally.

Tahoe 26 (September 2025)

• Last release for Intel. Tahoe still installs on four Intel Mac models (the 16-inch MacBook Pro from 2019, the 13-inch 2020 MacBook Pro with four Thunderbolt 3 ports, the 27-inch iMac from 2020 and the Mac Pro from 2019). Golden Gate 27 does not.
• Background Security Improvements (from 26.1). Apple's Background Security Improvements support page says they are supported and enabled starting with iOS 26.1, iPadOS 26.1 and macOS 26.1. They deliver lightweight security fixes for Safari, WebKit and other system libraries between software updates. The design is explained in the next section.
• Terminal and script protections (from 26.4). Apple added a Terminal and script protections page to the Platform Security guide in August 2026. On macOS 26.4 or later, three independent features target attacks that trick users into pasting commands or running scripts:
  • Terminal paste protection shows a warning when text is pasted into the Terminal app from a browser, Messages, Mail, Preview or common messaging apps. It only applies when the user has not opened Terminal in more than 30 days and no common developer tools such as Xcode are detected, with a 24 hour grace period after first setup.
  • Pasteboard command blocking applies to any terminal emulator, including third party ones. XProtect follows the process tree started by a pasted command, checks its network destinations against Apple's Safe Browsing service and blocks known malicious sources or behaviour that matches known malware techniques.
  • AppleScript scanning inspects every AppleScript and JavaScript for Automation script through the OpenScripting framework, whether it runs from a file or from memory. A blocked script stored on disk can be overridden from Finder; one run from memory cannot.

Golden Gate 27 (September 2026)

Golden Gate is the first macOS since the Apple silicon transition that runs only on Apple silicon. Its security advisory, About the security content of macOS Golden Gate 27, lists 242 distinct CVE IDs by our count, all fixed in the 27.0 release. Fixes that large are normal for a major release; it is also a reminder of the patching policy below, because not every one of those fixes is guaranteed to reach Tahoe or Sequoia. Background Security Improvements continue in 27. The 27.0.1 update (28 September 2026) lists no published CVE entries.

Passkeys

Passkeys are the Apple feature most often asked about alongside these releases. Apple's passkeys developer page explains what they are: credentials based on FIDO Alliance and W3C standards that replace passwords with a key pair, where the server keeps only the public key. Apple lists three security properties: every passkey is strong and never reused, a server breach exposes only public keys, and a passkey is bound to the site or app it was created for, so it cannot be phished. Passkeys sync through iCloud Keychain, where they are end-to-end encrypted. The current page adds that passkeys can sync through external providers, be shared in groups, work with Managed Apple Accounts in managed environments, and be imported and exported between password managers. Apple's documentation we reviewed does not tie the original passkey launch to a single macOS version, so we do not list it in a specific row of the comparison table.

App sandbox and privacy prompts (TCC)

The prompts you see when an app wants your camera, screen or files come from macOS's privacy controls, often called TCC after the subsystem that enforces them. Apple's Protecting app access to user data page lists the protected categories on macOS: calendars, camera, contacts, microphone, photos, reminders and speech recognition, plus Mac-only categories for input monitoring (keystrokes), screen recording (screenshots and video) and access to System Settings. Apple's Gatekeeper and runtime protection page adds that every App Store app is sandboxed, so it can reach another app's data only through system APIs. Apps distributed outside the store can opt in to the sandbox, and many developer tools do not.

For developers, the practical effect of each release has been more prompts and more categories rather than one big change. Expect to re-approve terminal apps, screen recording tools and anything that reads files in protected folders after a major upgrade.

From Rapid Security Responses to Background Security Improvements

Fast security fixes have had two designs on the Mac.

Rapid Security Responses (Ventura era). These were versioned with a letter after the point release, for example 13.4.1 (a). Apple's archive shows them alongside regular updates in 2023. The support page Apple used for Rapid Security Responses now covers Background Security Improvements, and device management still uses the older name: the declarative configuration that controls Background Security Improvements is called SoftwareUpdateSettingsRapidSecurityResponseObject.

Background Security Improvements (from 26.1). Apple's Platform Security guide page on Background Security Improvements explains what changed under the hood:

• Content that can be patched this way now lives in cryptexes, cryptographically sealed disk images stored on the preboot volume next to the boot firmware. A cryptex can be updated by applying a binary patch to its disk image.
• Each cryptex's measurement, seal and trust cache are covered by a separate signed ticket bound to the device, so applying a fix does not change the main boot ticket and the system volume does not need to be resealed.
• On a Mac, a Safari fix becomes active as soon as Safari is relaunched. The rest of the system picks up the new content at the next restart.
• Every Background Security Improvement ships with a patch and an "antipatch," so it can be removed. Removing them returns the device to the last full software update.
• Apple can remove a faulty one through automatic updates. If a specific app starts crashing more after an improvement is installed, macOS can tell the user and offer to remove it.

Apple's deployment guide page on Background Security Improvements adds the operational rules. They are lettered a, b, c relative to the base version, each one includes the previous ones, and the next point release includes all of them. Administrators can stop users installing them manually or removing them with the Enable and EnableRollback keys, and can read the installed letter from the StatusDeviceOperatingSystemSupplementalExtraVersion status key. The support page adds one limitation: a Mac gets them only when it boots from its internal storage.

The first one Apple published with a security advisory came on 17 March 2026. According to Apple's advisory, it fixed a cross-origin issue in WebKit's Navigation API (CVE-2026-20643) for iOS 26.3.1, iPadOS 26.3.1 and macOS 26.3.1 and 26.3.2, labelled "(a)".

How Apple's patching policy works

Apple's model is simpler than most operating system vendors' and less documented. These are the rules you can confirm from Apple's own pages.

The newest release gets everything. Apple's About software updates page in the deployment guide carries the key sentence. Because of architecture and system changes in the current version, "not all known security issues are addressed in previous versions." Apple uses iOS 27 and macOS 27 as the example of current versions and iOS 26 and macOS 26 as previous ones.

Two older releases get security updates. The releases page shows Golden Gate, Tahoe and Sequoia receiving updates in September 2026. Every year the oldest of the three drops off when the new release ships.

Safari is updated separately on older releases. On 18 August 2026, Apple shipped Safari 26.6.1 for Sonoma and Sequoia. On 14 September 2026, Safari 27 shipped for Sequoia and Tahoe. Browser fixes for older macOS arrive as a Safari update rather than inside a macOS point release.

Background Security Improvements apply only to the latest minor version. The deployment guide states they do not follow managed update deferrals, but because they apply only to the latest point release, deferring that point release also defers them.

Updates are personalised and old versions stop being signed. As covered above, on Apple silicon and T2 Macs with Full Security, Apple signs updates for one device and stops signing versions with known vulnerabilities.

Organisations can delay, but not forever. The enforcement page says managed devices can defer updates by 1 to 90 days, and on a Mac you can set different deferrals for operating system updates, major upgrades and non-OS updates (Safari, XProtect, printer drivers and Xcode Command Line Tools). Over the air updates normally stay available for up to 180 days so a 90 day deferral can always be satisfied. Administrators can also enforce a specific update by a date and time in the device's local time zone, which overrides deferrals and also overrides a user who has turned off automatic Background Security Improvements.

The consequence is simple and often missed: "still getting updates" is not the same as "fully patched." A Mac on Sequoia in October 2026 receives security updates, but some issues fixed in Golden Gate may never be fixed on Sequoia.

How XProtect, notarisation and Gatekeeper work together

Apple's malware protection page describes three layers:

1. Prevent launch. The App Store, or Gatekeeper combined with notarisation, aims to stop malware launching even once.
2. Block it if it appears. Gatekeeper, notarisation and XProtect identify and block malware that reaches a Mac.
3. Remediate. XProtect removes malware that has already run.

Each piece has a distinct job:

The Gatekeeper and runtime protection page adds two details people often miss. Gatekeeper tracks the provenance of files written by downloaded software, and it can open apps from a randomised read-only location to stop a harmless looking app from silently loading a malicious plug-in shipped next to it.

When Apple finds new malware, the malware page lists what can happen: associated Developer ID certificates are revoked, revocation tickets are issued for the files, and XProtect signatures are released, including against software that was previously notarised. Notarisation is effective against known files and hashes; XProtect's rules are more generic and can catch variants Apple has not seen.

Two points matter for anyone who manages Macs. First, XProtect and notarisation catch known malware. They do not judge whether an open source library inside a signed app has a known vulnerability. Second, the 26.4 terminal protections show where Apple sees the current threat: social engineering that gets users to paste commands, which bypasses Gatekeeper entirely because nothing is "opened" in the usual sense.

Feature by release comparison

Rows marked "Yes" after a feature's introduction mean Apple's documentation describes the feature as available in that version or later. "Expanded" for Lockdown Mode in Sonoma reflects Apple's statement that additional protections arrived in macOS 14.

How to check version, update state and SIP from Terminal

Every command below is read only unless marked. Run them in Terminal on the Mac you want to check. Commands that need administrator rights use sudo and say so.

Step 1: find the macOS version and build

sw_vers
sw_vers --productVersion
sw_vers --buildVersion
sw_vers --productVersionExtra

sw_vers prints the product name, version and build. The --productVersionExtra option prints the letter of any installed Background Security Improvement, for example (a); it prints nothing if none is installed. For a fuller summary that also shows the kernel version and SIP state:

system_profiler SPSoftwareDataType

Compare the version against the "latest version" column on Apple's Find out which macOS your Mac is using page. A Mac on Sequoia showing anything older than 15.8.1, or Tahoe older than 26.7.1, is behind as of this writing.

Step 2: list pending updates and update history

softwareupdate --list
softwareupdate --history
system_profiler SPInstallHistoryDataType

--list asks Apple's servers for updates available to this Mac and prints their labels. --history shows what was installed and when, but by default only for updates installed by softwareupdate itself. system_profiler SPInstallHistoryDataType lists every install the Mac recorded, including updates from System Settings and background data updates such as XProtect payloads. Command Line Tools updates appear here with labels such as "Command Line Tools for Xcode."

To check the automatic update settings that Software Update stores:

defaults read /Library/Preferences/com.apple.SoftwareUpdate

Look for AutomaticDownload, AutomaticallyInstallMacOSUpdates, CriticalUpdateInstall and ConfigDataInstall. The last two relate to automatic security updates and system data files, which is how XProtect and related data updates arrive. A value of 0 means that category is off. On a managed Mac, these may be overridden by a configuration profile. Background Security Improvements have their own Automatically Install switch under System Settings, Privacy and Security, according to Apple's support page.

To install everything available (this restarts the Mac if needed, so save work first):

sudo softwareupdate --install --all --restart

Step 3: check System Integrity Protection and the sealed system

csrutil status
csrutil authenticated-root status

csrutil status should print "System Integrity Protection status: enabled." csrutil authenticated-root status reports whether the sealed, authenticated system volume is enforced; it should print "enabled." Neither can be changed from a normal macOS session. On Apple silicon, changing them requires booting into recovery by holding the power button, which is the physical presence check described earlier. If either shows disabled on a machine that is not a deliberate kernel development box, treat it as a finding.

Step 4: check Gatekeeper, XProtect and FileVault

spctl --status
xprotect version
fdesetup status

spctl --status should print "assessments enabled," which means Gatekeeper is on. xprotect version prints the installed XProtect version and install time. On current releases, xprotect check prints the XProtect update currently available from Apple and xprotect update performs an update (it may need administrator rights). If the install time is weeks old, check the ConfigDataInstall setting from Step 2. fdesetup status should report "FileVault is On." Remember the SSV protects the system volume; FileVault protects your data.

Step 5: check kernel and system extensions

systemextensionsctl list
kmutil showloaded --list-only | grep -v com.apple

systemextensionsctl list shows user space system extensions (Endpoint Security, Network Extension and DriverKit). The kmutil line lists loaded kernel extensions that are not Apple's. On a modern Apple silicon Mac this should normally be empty. If it is not, the Mac is running at Reduced Security, so confirm that was intended and that the vendor has a plan to move to system extensions.

Step 6: check device management enrolment and profiles

profiles status -type enrollment
sudo profiles list

The first command shows whether the Mac is enrolled through Automated Device Enrollment and whether MDM is active. The second lists installed configuration profiles, which is where deferral settings, Background Security Improvement controls and update enforcement come from. Remember that Lockdown Mode blocks profile installation and MDM enrolment, so a Lockdown Mode Mac will show no new profiles by design.

Step 7: check the hardware architecture

uname -m
sysctl -n sysctl.proc_translated

uname -m prints arm64 on Apple silicon and x86_64 on Intel. If you run it from a shell under Rosetta 2 on Apple silicon, it prints x86_64, so the second command helps: it prints 1 when the current process is translated by Rosetta and 0 when it runs natively. A fleet script that decides upgrade eligibility from uname -m alone can misclassify Macs.

Putting it together

A short script that prints one line per check is enough for most teams:

#!/bin/zsh
echo "macOS:        $(sw_vers --productVersion) $(sw_vers --productVersionExtra) build $(sw_vers --buildVersion)"
echo "Arch:         $(uname -m) (translated: $(sysctl -n sysctl.proc_translated 2>/dev/null))"
echo "SIP:          $(csrutil status | awk -F': ' '{print $2}')"
echo "Sealed root:  $(csrutil authenticated-root status | awk -F': ' '{print $2}')"
echo "Gatekeeper:   $(spctl --status)"
echo "XProtect:     $(xprotect version 2>/dev/null | head -1)"
echo "FileVault:    $(fdesetup status | head -1)"
echo "Third party kexts: $(kmutil showloaded --list-only 2>/dev/null | grep -vc com.apple)"

Run it after every upgrade and keep the output with your change record.

What happened to Intel Mac support, and what it means for fleets

Apple began moving the Mac to its own chips with Big Sur in 2020. For six releases, macOS supported both architectures. Golden Gate 27 ends that: its compatibility page lists only Apple silicon models and the MacBook Neo, and its security advisory lists the same.

For an Intel fleet in October 2026 the picture is:

If the past pattern holds, Sequoia will stop receiving updates when macOS 28 ships, likely in the second half of 2027, and Tahoe a year after that. That is an inference from Apple's history, not an Apple announcement. Plan hardware replacement on that basis:

• Inventory by architecture and release, not by model year. The Step 7 check, combined with sw_vers, gives you both.
• Treat Sequoia Intel Macs as the most urgent. They are on the oldest supported release, and they cannot move to Tahoe unless they are among the four models listed above.
• Expect older releases to miss some fixes. Because of Apple's stated policy, even a supported older release does not get everything.
• Check Intel-specific security features. On Intel, the boot chain depends on the T2 chip where present. Apple's SSV page notes that on T2 Macs only macOS itself is protected by the SSV, while the software on the T2 is protected by secure boot. Intel Macs without a T2 chip do not get the personalised update signing described above.
• Watch Rosetta. Apple silicon Macs run Intel software through Rosetta 2. Build pipelines and developer tools that still ship Intel only binaries will need updating as Intel support ends across the ecosystem.

What developers and admins should change after each upgrade

A major macOS upgrade replaces the system volume, refreshes privacy decisions for some categories and can update or invalidate the developer tool chain. These are the checks we recommend after every upgrade.

Xcode Command Line Tools

The Command Line Tools provide clang, git, make and the macOS SDK headers that Homebrew, Python packages with native extensions and many language toolchains depend on. They are updated separately from macOS, and Apple's deployment guide lists them among the "non-OS updates" that managed Macs can defer independently.

xcode-select -p
pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
softwareupdate --list

xcode-select -p shows which developer directory is active (either full Xcode or /Library/Developer/CommandLineTools). pkgutil prints the installed Command Line Tools version. If softwareupdate --list shows a newer "Command Line Tools for Xcode" label, install it. If the tools are missing entirely after an upgrade, xcode-select --install reinstalls them.

Homebrew and other package managers

Homebrew installs prebuilt packages for each macOS version and architecture. After a major upgrade, update Homebrew itself, then the packages, then check for problems:

brew update
brew upgrade
brew doctor
brew config

brew config shows the macOS version, architecture and prefix Homebrew is using. On Apple silicon the prefix is normally /opt/homebrew; on Intel it is /usr/local. If a Mac was migrated from Intel to Apple silicon with Migration Assistant, it can end up with both, and the Intel copy will run under Rosetta. Remove or migrate the old prefix rather than running two package trees with different patch levels.

The same applies to language toolchains installed outside Homebrew. Rebuild Python virtual environments, node_modules folders with native add-ons, and Ruby gems with C extensions after a major upgrade, because they are compiled against the old SDK. A rebuild is also the moment every dependency is resolved again, which is when a known vulnerable version can come back in if your lockfiles allow it.

Device management profiles and update policy

• Re-check deferrals. A 90 day upgrade deferral set for the previous release is still in force. Decide whether the new release is approved, then adjust.
• Set a minimum OS for enrolment. On macOS 14 or later, Automated Device Enrollment can require a minimum version, so new Macs are patched before first use.
• Decide on Background Security Improvements. Leave automatic installation on unless you have a specific compatibility reason, and use EnableRollback to decide whether users can remove them.
• Re-approve system extensions and privacy permissions. Security agents, VPN clients and screen sharing tools may need fresh approvals. Pre-approve them with configuration profiles rather than asking users to click through.
• Remove kext approvals you no longer need. Each kext on Apple silicon keeps the Mac at Reduced Security. If a vendor now offers a system extension, switch and return the Mac to Full Security.

Developer workflows affected by recent releases

• Gatekeeper on Sequoia and later. Internal tools distributed as unsigned or un-notarised apps can no longer be opened with Control-click. Sign them with a Developer ID and notarise them, or install them through device management.
• Terminal protections on 26.4 and later. Developers with Xcode or common IDEs installed will not see the paste warning, but pasteboard command blocking and AppleScript scanning apply to everyone. Scripts flagged by XProtect from memory cannot be overridden; save them to a file first if you have a legitimate need.

Common mistakes

• Assuming "supported" means "fully patched." Apple says older releases do not get every fix. Tahoe and Sequoia are supported, but only Golden Gate receives everything.
• Waiting for an end of support notice. Apple does not publish one for macOS. Read the security releases page each September and see which releases were left out.
• Mistaking a no-CVE update for security support. Big Sur 11.7.11 and Catalina's Security Update 2026-001 shipped in February 2026 with no published CVE entries. They did not restart security support.
• Turning off automatic security updates and system data files. If ConfigDataInstall is 0, XProtect data may not arrive, and if the Background Security Improvements switch is off, those fixes wait for the next point release. A Mac can be on the latest point release and still have stale malware signatures.
• Disabling SIP to get a tool working and forgetting to re-enable it. On Apple silicon this is a recovery mode change, so it is rarely done by accident. Check csrutil status in your fleet report so you notice the exceptions.
• Leaving Macs at Reduced Security for one old kext. It also allows older, signed macOS versions to boot, which removes rollback protection.
• Using uname -m alone to find Intel Macs. Under Rosetta it reports x86_64 on Apple silicon. Check sysctl.proc_translated too.
• Deferring point releases for too long. Background Security Improvements apply only to the latest point release, so a long deferral delays them as well.
• Treating XProtect as a dependency scanner. XProtect finds known malware. It does not tell you that a signed app or your own project ships a library with a known vulnerability.
• Forgetting the developer tool chain after an upgrade. Command Line Tools, Homebrew and native modules have their own versions and their own vulnerabilities, separate from macOS.

Where Safeguard fits, honestly

Most of this post is outside what Safeguard does. Safeguard does not manage Macs, install macOS updates, enforce Gatekeeper or Lockdown Mode, check SIP, FileVault or boot policies, inspect firmware, or provide endpoint protection or malware detection. Those jobs belong to macOS itself and to your device management tools.

The honest link is the software built on and shipped from Macs. A developer Mac that has just been upgraded rebuilds its projects, reinstalls Homebrew packages and pulls container images, and those open source dependencies change far more often than macOS does. Safeguard's CLI can scan a repository, a container image or an SBOM file (safeguard scan --dir ., --image <name>, --sbom <file>), match components against vulnerability databases and apply reachability analysis, and the platform shows which projects contain a given component and version. Policies and gates can stop a known vulnerable dependency from shipping, and autonomous remediation can open fix pull requests (it ships switched off). None of that touches macOS servicing itself, and none of it replaces XProtect or Gatekeeper.

FAQ

What is the latest version of macOS?

As of 23 October 2026, Apple's security releases page lists macOS 27.0.1 (Golden Gate) as the latest version, released on 28 September 2026. The latest versions of the older supported releases are Tahoe 26.7.1 and Sequoia 15.8.1, released the same day.

Which macOS versions still get security updates?

Golden Gate 27, Tahoe 26 and Sequoia 15 received security updates in September 2026. Sonoma 14's last update was 14.8.9 on 6 August 2026, and Apple's pattern suggests it will not receive more. Ventura, Monterey and Big Sur no longer get security fixes.

How long does Apple support each version of macOS?

Apple does not publish a fixed lifecycle. In practice, Big Sur, Monterey, Ventura and Sonoma each got security updates for about two years and ten months after release, and only the newest release gets every fix.

Is macOS Tahoe the last version for Intel Macs?

Yes, in practice. Golden Gate 27's compatibility page and security advisory list only Apple silicon Macs and the MacBook Neo. Tahoe 26 still supports four Intel models: the 16-inch MacBook Pro (2019), the 13-inch MacBook Pro (2020, four Thunderbolt 3 ports), the 27-inch iMac (2020) and the Mac Pro (2019).

What is a signed system volume in macOS?

It is the read-only system volume introduced with macOS 11, sealed with a hash tree whose root is signed by Apple. The bootloader verifies the seal before the kernel starts, and every read is checked against the expected hash. If the check fails, the Mac will not boot and asks you to reinstall macOS.

What replaced Rapid Security Responses?

Background Security Improvements, starting with macOS 26.1. They deliver fixes for Safari, WebKit and system libraries between point releases through sealed, patchable disk images called cryptexes, can be removed to return to the last full update, and do not require the system volume to be resealed.

How do I check if SIP is enabled on my Mac?

Run csrutil status in Terminal. It should print "System Integrity Protection status: enabled." Run csrutil authenticated-root status to confirm the sealed system volume is enforced as well.

How do I check the XProtect version on a Mac?

On current releases, run xprotect version in Terminal. It prints the installed version and when it was installed. xprotect check shows the update currently available from Apple, and xprotect update performs an update.

Why can't I Control-click to open an app on macOS Sequoia?

Apple removed the Control-click Gatekeeper override in macOS Sequoia. To open software that is not signed correctly or notarised, try to open it, then go to System Settings, Privacy and Security, and click Open Anyway. Only do this for software you trust from a known source.

What is Lockdown Mode on a Mac?

An optional, extreme protection, available from macOS Ventura, for people who may be personally targeted by sophisticated attacks such as mercenary spyware. It blocks most message attachments and some web technologies, blocks unknown FaceTime callers, prevents configuration profiles and device management enrolment, and needs explicit approval to connect accessories on Apple silicon laptops.

Each macOS release has hardened the operating system, but the Macs it runs on still build and ship software made mostly of open source dependencies. A freshly upgraded developer Mac reinstalls packages, rebuilds native modules and pulls container images, and those components need their own fixes on their own schedule, separate from Apple's.

Fix it without waiting for upstream

Whatever the vulnerability, most of the risk sits in two gaps. The first is the time between a fix being published and that fix actually running in your production builds. The second, and worse, is the time before any fix exists at all, while a maintainer works out a patch and a release schedule. Waiting through both gaps is a habit, not a requirement. Safeguard gives teams three ways to close them.

1. Autonomous remediation: pull requests, not tickets

When a fixed version exists, Safeguard's Griffin models open a tested, policy gated pull request that moves the affected dependency to the safe version. You can run it on one repository or in bulk across every project that carries the vulnerable version. Remediation covers eight categories, including dependencies, licenses, security posture and findings. Reachability analysis ranks the vulnerable code paths your application actually calls first, so the first pull requests you merge are the ones that matter most. Autonomous remediation ships switched off, with every category set to Manual, so your team decides how much runs on its own and what still needs a human approval.

2. Gold Open Source: the safe version in seconds, free

gold.safeguard.sh is free and needs no login. Search any CVE or package to see affected and fixed versions, CVSS, EPSS, CISA KEV status and a recommended safe version, or use the "Am I affected?" checker. The same data is available through a free read API, README status badges and RSS threat feeds. The safeguard-sh/gold-scan-action GitHub Action can fail a build on a known exploited vulnerability, on any known vulnerability, or never, so a version you have just removed cannot quietly come back in next week's merge.

3. Gold Registry: start from components that are already fixed

registry.safeguard.sh provides hardened, drop in replacements for upstream packages and container images. Every Gold artifact is held continuously to zero exploitable critical or high CVEs, zero malware and a completed license check, with SLSA L3 or higher provenance, a Sigstore signature and a public evidence page you can hand to an auditor. An artifact loses its Gold badge if it regresses. Teams can point their own package directory at the registry so hardened equivalents resolve without changing how developers install anything.

When upstream has no fix yet, or will not ship one, Safeguard first works to get the fix accepted upstream. If the issue is severe or upstream will not move, Safeguard builds a fork, fixes the vulnerability there and publishes a hardened Gold build, so you are not stuck on a maintainer's release schedule. You can also request a hardened, compatibility tested build of a specific package. This fork and patch flow is in early access today, so ask which packages it covers before you plan around it.

One honest limit: when the vulnerable code lives in a vendor appliance, a hosted service or an operating system runtime you do not build yourself, the fix still has to come from that vendor or distribution. The steps above apply to the open source dependencies and container images you build and ship, which is where most teams carry the largest and least tracked share of their exposure.

See how Safeguard would help

None of these demos change macOS settings or install macOS updates. They show how Safeguard handles the software you build and run on a Mac.

The first demo is a real Safeguard CLI session: asked to fix a lodash CVE, the assistant reads the finding and advisory, asks before each command, edits package.json to lodash 4.17.21, runs npm install and npm test with your approval, prints a summary and pushes nothing. On a Mac you have just upgraded, the same flow applies to a project whose dependencies were resolved again during the rebuild and now include a version with a known fix available.

Click through it at your own pace, or open it full screen.

The second demo sets up the local runner on your own machine, approves it with its device code, then scans from the terminal. That is the route for scanning the repositories and container images on a developer Mac after an upgrade, alongside the macOS checks in the walkthrough above.

Click through it at your own pace, or open it full screen.

The third demo connects Claude to the Safeguard MCP server with OAuth and chooses which tools Claude can use. Once your projects are in Safeguard, the same connection lets you ask which of them contain a given component and version, for example when an advisory names a library that your Mac build tools or Homebrew packages depend on.

Click through it at your own pace, or open it full screen.

To try the CLI, download Safeguard and follow the CLI documentation.

Quick check

Sources

• Apple: Apple security releases
• Apple: Apple security updates (2020 to 2021)
• Apple: Apple security updates (2022 to 2023)
• Apple: Find out which macOS your Mac is using
• Apple: About the security content of macOS Golden Gate 27
• Apple: macOS 27 Golden Gate is compatible with these computers
• Apple: macOS Tahoe 26 is compatible with these computers
• Apple: macOS Sequoia is compatible with these computers
• Apple: macOS Sonoma is compatible with these computers
• Apple: macOS Ventura is compatible with these computers
• Apple: macOS Monterey is compatible with these computers
• Apple: macOS Big Sur is compatible with these computers
• Apple: About Background Security Improvements for iOS, iPadOS, and macOS
• Apple: Security content of Background Security Improvements for iOS 26.3.1, iPadOS 26.3.1, macOS 26.3.1 and 26.3.2
• Apple: About Lockdown Mode
• Apple: Safely open apps on your Mac
• Apple: Update macOS on Mac
• Apple Platform Security: Signed system volume security
• Apple Platform Security: Securely extending the kernel in macOS
• Apple Platform Security: Startup Disk security policy control for a Mac with Apple silicon
• Apple Platform Security: Secure software updates
• Apple Platform Security: System Integrity Protection
• Apple Platform Security: Background Security Improvements in Apple operating systems
• Apple Platform Security: Gatekeeper and runtime protection in macOS
• Apple Platform Security: Protecting against malware in macOS
• Apple Platform Security: Terminal and script protections
• Apple Platform Security: Lockdown Mode security for Apple devices
• Apple Platform Security: Protecting app access to user data
• Apple Platform Security: Document revision history
• Apple Platform Deployment: About software updates
• Apple Platform Deployment: Install and enforce software updates
• Apple Platform Deployment: Background Security Improvements
• Apple Developer: Updates to runtime protection in macOS Sequoia
• Apple Developer: Passkeys

Last reviewed: 23 October 2026. Apple does not publish end of support dates for macOS; check the Apple security releases page before planning an upgrade.