Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/defense-incident-responseDFIR and threat hunting

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 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/defense-incident-response

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
vyTrLiZBC7…5LzBtgAw==The CLI checks the SHA-256 and the signature before it writes a file.
Packaged1e00361…3c6ad423
d1e003617b20…0da73c6ad4231 file · ⁦1.4 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/defense/defense-incident-response@ee0e0c5

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)

  1. Prepare (before): comms plan, roles, logging, backups, and access ready. You don't want to build these mid-incident.
  2. 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).
  3. 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.
  4. 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.
  5. Recover: restore from known-good, monitor closely for re-entry, phase systems back.
  6. 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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5d1e00361Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login