← ClaudeAtlas

integrate-fuzzing-sdlclisted

Defensive methodology for building fuzzing into your SDLC and CI so you find exploitable memory-safety and parsing bugs in your own code before an adversary fuzzes your released binaries to develop exploits (MITRE ATT&CK T1587.004, which names fuzzing, feeding T1190, T1203, and T1068). The log source is your build pipeline, not a SIEM: sanitizer reports (ASan, UBSan, MSan, TSan), libFuzzer and AFL++ crash output, OSS-Fuzz / ClusterFuzz / CIFuzz dashboards, coverage deltas, and crash stack-hash dedup in GitHub Actions or GitLab CI. Gives the signals, a CI gating approach, a corpus-triage hunt, and SDLC hardening mapped to ISO and NIST. Use when you want to add fuzzing to CI, triage a fuzzer crash, dedup and bug-bucket findings, decide whether a sanitizer report is exploitable and release-blocking, set up OSS-Fuzz or CIFuzz, or harden a library release process against bug-hunting attackers.
umbrasec-labs/umbra-blue · ★ 0 · AI & Automation · score 62
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