integrate-fuzzing-sdlclisted
Install: claude install-skill umbrasec-labs/umbra-blue
# Fuzzing in the SDLC - Defensive Methodology
> **Tier 2 - methodology skill.** No bespoke UMBRASEC detection rule ships with this skill yet. It gives the defender's method, the pipeline signals, the triage hunt, and the hardening, and it points to public, maintained sources by URL. Promotion to Tier 1 (a sourced, tuned UMBRASEC artifact) is tracked in [COVERAGE.md](https://github.com/umbrasec-labs/umbra-blue/blob/main/COVERAGE.md). Do not treat the content below as citing a UMBRASEC rule; there is none for this threat yet.
## TL;DR
Adversaries fuzz your shipped software to find the memory-corruption and parsing bugs they turn into exploits. You win by fuzzing the same code first, continuously, with sanitizers on, so the crash lands in your CI run instead of in a 0-day. Build short-running fuzz targets that run on every pull request (regression mode over the committed corpus) and long-running jobs out of band (OSS-Fuzz or a self-hosted ClusterFuzz). Treat an ASan or UBSan abort in a fuzz job exactly like a failed test: it blocks the merge. The hard part is not finding crashes, it is triaging them: dedup by sanitizer stack hash, bucket by root cause, decide exploitability, and map each live bug back to the released versions that carry it.
## What it looks like, defender view
This threat does not show up as an alert in your SOC. It shows up, if you are doing this right, as a reproducible crash inside your own build pipeline before release. The defender-side signal is a fuz