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-purple-teamDFIR and threat hunting

defense-purple-team

⁨Run a purple-team exercise — emulate specific attacker techniques and validate detection/response end to end. Load for "purple team", detection validation, ATT&CK coverage testing, "can we detect X", or turning red-team findings into blue-team improvements. Signals: detection gaps, ATT&CK mapping, c⁩

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-purple-team

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

SignatureSigned, ed25519
Iu0EvKsxJq…gAUpyFCA==The CLI checks the SHA-256 and the signature before it writes a file.
Package8a281cfa…c8f38317
8a281cfa3b7c…d1b9c8f383171 file · ⁦1.3 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-purple-team@ee0e0c5

When it applies

You want to measure and improve detection, not just find bugs. Purple teaming runs known attacker techniques in a controlled way and checks whether each is prevented, detected, and responded to — closing the loop between offense and defense.

Why it works

Detections are only real if they fire on the actual technique. Emulating each technique and watching the telemetry proves coverage, exposes blind spots, and produces tuned detections — turning "we think we'd catch it" into evidence.

Method

  1. Pick techniques from real risk: map to MITRE ATT&CK, prioritized by your threat model (→ defense-threat-modeling) and recent red-team/pentest findings.
  2. Emulate safely: run controlled tests — Atomic Red Team (per-technique atomics) or CALDERA (chained) in a lab/segmented env. One technique at a time, documented.
  3. Observe the pipeline: for each, check — was it prevented (EDR/control)? logged (right source/fields)? detected (alert fired)? responded (triaged in time)? Record the gap at each stage.
  4. Fix the gaps: add/tune detections (→ defense-detection-sigma), fix logging coverage, harden the control (→ defense-hardening-baseline), and improve the runbook.
  5. Re-test to confirm the detection fires and is low-FP; track ATT&CK coverage over time.

Anti-patterns

  • Running noisy tools blindly instead of specific, mapped techniques — you learn nothing measurable.
  • Declaring "detected" without checking the alert actually fired and was actionable.
  • One-and-done — coverage decays; re-run after infra/detection changes.

Verify

For each emulated technique: a documented prevent/detect/respond result, a new or tuned detection for every gap, and a re-test showing it now fires cleanly.

References

MITRE ATT&CK; Atomic Red Team; MITRE CALDERA; "purple team exercise framework" (SCYTHE).

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, 2026ee0e0c58a281cfaSigned–

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