Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
macOS forensics works with APFS snapshots, unified logs, and the property lists and databases behind Apple’s own features, on hardware where acquisition is increasingly a live-system exercise.

What Is macOS Forensics?
Apple hardware is now common enough in UK organisations that an intrusion investigation stands a reasonable chance of involving a Mac, usually belonging to a developer or an executive. The artefacts are rich, well documented by the research community, and almost entirely different from their Windows equivalents.
On Apple silicon, the storage controller is part of the system on a chip and the drive cannot be removed. Target disk mode has been replaced by Mac Sharing Mode, which exposes a read-only view of the data volume over a cable to another Mac, and full acquisition typically means booting into the recovery environment with valid credentials or performing a live collection on the running system.
FileVault complicates the picture further, since a locked volume yields nothing useful. The practical guidance is the same as for mobile devices: if the machine is running and unlocked, work with it live. Collect memory where the tooling supports the hardware, then run a triage collection before considering shutdown. Jamf’s open-source Aftermath tool and the mac_apt framework both automate a broad artefact sweep.
log collect; what remains afterwards may cover only days.Look at launch agents and launch daemons in both the system and user library directories, login items, configuration profiles, browser extensions, and periodic scripts. Malware families targeting macOS have overwhelmingly favoured launch agents, and a property list in a user’s library directory pointing at a binary in a temporary folder is a strong signal. Check code signing and notarisation status on every binary of interest, since legitimate applications are almost always signed.
The filesystem is copy-on-write, and snapshots are cheap, so local Time Machine snapshots accumulate automatically on most machines. Each one is a point-in-time view of the volume, which may predate an attacker’s clean-up by days. Mounting and comparing snapshots is one of the most productive things an examiner can do on a Mac and has no equivalent on a default Windows installation beyond volume shadow copies.
System Integrity Protection restricts access to protected locations even for root, which affects what a live collection can read. Timestamps use the Apple epoch of 1 January 2001 in many property lists and databases, so check conversions before building a timeline — the same class of error described in browser forensics.
Treat the Mac as one source among several: the unified log explains the endpoint, but identity logs, email trace data, and cloud audit trails explain what the account did elsewhere. Our digital forensic incident response services cover macOS endpoints alongside Windows and Linux, which matters in mixed estates where the Mac population is small enough to be overlooked in monitoring.
Not by removing the drive, which is soldered and tied to the system on a chip. The available routes are Mac Sharing Mode, which presents a read-only view of the data volume to another Mac over a cable, booting into the recovery environment with valid credentials, or performing a live collection on the running system. FileVault makes live collection the preferred option.
A per-volume log of filesystem change notifications that macOS keeps for applications such as Spotlight and Time Machine. It records that changes occurred in a directory rather than exact operations, but it survives deletion of the files themselves and can show activity on external volumes that are no longer attached, which is valuable in data theft cases.
Days to a few weeks, depending on activity and disk space, because the store is a rolling buffer. That makes early collection essential: run log collect during triage rather than waiting until a full image is taken. Once the buffer has rolled, the detail it contained about process launches and authentication cannot be recovered from anywhere else.
Launch agents and launch daemons, in the user and system library directories. Login items, configuration profiles, and browser extensions follow. Check the code signing and notarisation status of every referenced binary, because legitimate software is almost always signed, and an unsigned executable in a temporary directory referenced by a property list is rarely benign.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.