iac.htora.dev · security templates

Home/Refreshers/macOS host triage: refresher

macOS host triage

What to capture first on a suspect Mac, where persistence hides, and which artifacts answer which question.

Remember

  1. Full memory capture is not practical on current Macs. Capture running state and the unified log instead.
  2. Capture the unified log first. A busy Mac may keep only days of it.
  3. Reading the system privacy database needs Full Disk Access for your terminal.
  4. A device management service can collect and isolate faster than hands on the machine.
PersistenceWhere
Launch agents and daemons~/Library/LaunchAgents/, /Library/LaunchAgents/, /Library/LaunchDaemons/
Login items and background taskssudo sfltool dumpbtm, on macOS 13 and later
Configuration profilessudo profiles list
Extensionssystemextensionsctl list
Shell start-up~/.zshrc, ~/.zshenv, /etc/zshrc
Sign-in plug-ins/Library/Security/SecurityAgentPlugins/

Collect

The unified logsudo log collect --last 3d --output host.logarchive
Processes, with start timesps -axo pid,ppid,user,lstart,command
Connectionslsof -nP -i
Where a file came fromxattr -p com.apple.quarantine <file>

Watch out

  • The download history with addresses is in ~/Library/Preferences/com.apple.LaunchServices.QuarantineEventsV2.
  • What was granted disk, camera, or screen access is in the TCC databases, one per user and one for the system.
Check it worked

The log archive, the persistence listings, and the TCC databases are copied off the Mac and hashed.

Read the full pageDownload PDF

Registry 0.23.0. Built 2026-11-17.

Made by Habibullah Tora. Source on GitHub. Code under the MIT licence, writing under CC BY 4.0.