defense-incident-response
Run an incident end to end — detect, scope, contain, eradicate, recover, learn. Load for "we've been breached", "incident response", "contain this host", "we found malware/an intrusion", or to build an IR plan. Complements defense-dfir-triage (evidence collection) with the response process around it
v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/defense-incident-responseGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacoted1e00361…3c6ad423
d1e003617b20…0da73c6ad4231 arquivo · 1.4 KBVarreduraBaixonenhum achado
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-incident-response@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When it applies
A confirmed or suspected compromise needs a coordinated response — not just analysis, but decisions about containment, eviction, and recovery under time pressure.
Why it works
A repeatable lifecycle keeps a stressful event from becoming chaos: it sequences the actions so you scope before you contain, contain before you tip off the adversary, and eradicate fully before you recover — the mistakes that turn one incident into three.
Method (NIST / PICERL lifecycle)
- Prepare (before): comms plan, roles, logging, backups, and access ready. You don't want to build these mid-incident.
- Identify & scope: what's the initial evidence, which hosts/identities/data are involved, when
did it start? Build a timeline; collect volatile evidence first (
defense-dfir-triage). - Contain: isolate affected hosts (network quarantine, not power-off — preserve memory), disable compromised accounts, revoke tokens/keys. Do it broadly enough to matter but coordinate so you don't tip off an adversary mid-scoping.
- Eradicate: remove persistence (services, tasks, startup, cloud roles), rotate all exposed credentials, patch the entry vector. Scope drives this — miss a foothold and they return.
- Recover: restore from known-good, monitor closely for re-entry, phase systems back.
- Lessons learned: timeline, root cause, what detection would have caught it sooner → feed
defense-detection-engineering.
Gotchas
- Powering off destroys memory evidence; isolate instead.
- Partial eradication (missing one C2 or one cloud role) = re-compromise within days.
- Rotate all credentials the attacker could have touched, not just the obvious one.
Verify success
The adversary is fully evicted (no persistence, all exposed creds rotated), systems restored from a trusted baseline, a timeline + root cause are documented, and a new detection covers the entry path.
References
NIST SP 800-61r2; SANS PICERL; the defense-dfir-triage and defense-detection-engineering skills.
Arquivos desta versão
- SKILL.md2.5 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Não | Não |
| Roda comandos no shell | Não | Não |
| Usa a rede | Não | Não |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
A varredura não encontrou nada para apontar nesta versão.
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | d1e00361 | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em DFIR e threat hunting
Ver a categoria- hunting-for-command-and-control-beaconingmukul975/hunting-for-command-and-control-beaconing5
- audit-context-buildingtrailofbits/audit-context-building4
- incident-response-forensicssecurityskills/incident-response-forensics3
- extracting-credentials-from-memory-dumpmukul975/extracting-credentials-from-memory-dump3
- analyzing-browser-forensics-with-hindsightmukul975/analyzing-browser-forensics-with-hindsight3
- forensics-ctfaeondave/forensics-ctf3
Pergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login