Contain And Recover macOS
Overview
Choose actions proportionate to evidence and ongoing harm. Preserve what matters, use official lifecycle controls, and verify the system after eradication rather than declaring it clean because one artifact disappeared.
Read references/macos-response-ladder.md for containment and recovery levels.
Workflow
- Confirm assessment, confidence, affected scope, ongoing behavior, critical data, and evidence needs.
- Choose immediate containment.
- Prefer reversible network/account/session isolation when it stops harm.
- Record the effect on volatile evidence and business/user access.
- Preserve decisive evidence.
- Capture artifact, persistence, process/network/log, account, and timeline records before removal when delay is safe.
- Stop active behavior through official controls.
- End processes/services deliberately; use
launchctl bootout for approved launch service removal from a domain, app-provided uninstallers for app components, and supported profile/extension management surfaces.
- Never edit launchd's internal state directly.
- Eradicate the verified mechanism.
- Remove or quarantine confirmed artifacts, registrations, extensions, profiles, helpers, rules, and downloaded stages; preserve hashes and paths.
- Do not reset, disable, or weaken TCC, Gatekeeper, XProtect, SIP, App Sandbox, or another protection merely to make a suspicious artifact run or simplify removal.
- Respond to identity exposure.
- Rotate affected credentials/tokens from a trusted device, revoke sessions/keys, review MFA and recovery methods, and notify owners/providers as warranted.
- Recover.
- Restore from a known-good point, reinstall/erase when integrity cannot be established, apply updates, reconfigure only needed access, and avoid restoring suspect persistence.
- Verify and monitor.
- Recheck persistence, runtime/network, accounts, security updates, backups, and recurrence across a defined observation window.
Output
Return containment/impact, evidence preserved, eradication actions, credential response, recovery basis, verification results, residual uncertainty, and return-to-service decision.
1---2name: contain-and-recover-macos3description: Contain a macOS threat and verify recovery. Use for isolation, process or service containment, credential response, persistence removal, quarantine, restore, erase/reinstall, monitoring, and return-to-service decisions.4---56# Contain And Recover macOS78## Overview910Choose actions proportionate to evidence and ongoing harm. Preserve what matters, use official lifecycle controls, and verify the system after eradication rather than declaring it clean because one artifact disappeared.1112Read [references/macos-response-ladder.md](references/macos-response-ladder.md) for containment and recovery levels.1314## Workflow15161. Confirm assessment, confidence, affected scope, ongoing behavior, critical data, and evidence needs.172. Choose immediate containment.18 - Prefer reversible network/account/session isolation when it stops harm.19 - Record the effect on volatile evidence and business/user access.203. Preserve decisive evidence.21 - Capture artifact, persistence, process/network/log, account, and timeline records before removal when delay is safe.224. Stop active behavior through official controls.23 - End processes/services deliberately; use `launchctl bootout` for approved launch service removal from a domain, app-provided uninstallers for app components, and supported profile/extension management surfaces.24 - Never edit launchd's internal state directly.255. Eradicate the verified mechanism.26 - Remove or quarantine confirmed artifacts, registrations, extensions, profiles, helpers, rules, and downloaded stages; preserve hashes and paths.27 - Do not reset, disable, or weaken TCC, Gatekeeper, XProtect, SIP, App Sandbox, or another protection merely to make a suspicious artifact run or simplify removal.286. Respond to identity exposure.29 - Rotate affected credentials/tokens from a trusted device, revoke sessions/keys, review MFA and recovery methods, and notify owners/providers as warranted.307. Recover.31 - Restore from a known-good point, reinstall/erase when integrity cannot be established, apply updates, reconfigure only needed access, and avoid restoring suspect persistence.328. Verify and monitor.33 - Recheck persistence, runtime/network, accounts, security updates, backups, and recurrence across a defined observation window.3435## Output3637Return containment/impact, evidence preserved, eradication actions, credential response, recovery basis, verification results, residual uncertainty, and return-to-service decision.
gaelic-ghost