A comprehensive framework for analyzing and defending against attacks targeting Software Development Lifecycle infrastructure.
Launch the Flow Builder - Interactive tool for mapping attack flows

Explore Techniques Visually - Interactive visual explorer with filtering and search

Automated Attack Flow Generation - Use Claude skills to automatically generate SITF-compliant attack flows and technique proposals:
/attack-flow- Generate attack flow JSON from incident reports or attack descriptions/technique-proposal- Create PR-ready proposals for new techniques when gaps are identified
See Claude Skills Documentation below for detailed usage instructions.
Launch builder locally - Download visualizer.html locally, open and build offline
Explore techniques - Download techniques-library.html locally, open and browse techniques offline
Read the Implementation Guide - Complete methodology, case studies, and usage instructions
SITF helps security teams analyze supply chain attacks by:
- Visualizing attack stages across SDLC components (Endpoint, VCS, CI/CD, Registry, Production)
- Identifying the risks that enabled each attack technique
- Mapping risks to appropriate security controls
- Understanding attack paths and lateral movement patterns
- 5 Infrastructure Components: Endpoint/IDE, VCS, CI/CD, Registry, Production/Cloud
- Over 70 Attack Techniques: Pre-mapped with enabling risks and preventive controls
- Interactive Visualizer: Drag-and-drop interface for building attack flow diagrams
- Real-World Case Studies: CircleCI breach, Shai-Hulud-2, Codecov
- IMPLEMENTATION_GUIDE.md - Start here for complete framework overview
- TECHNIQUE_LIBRARY.md - Reference catalog of all techniques
- techniques.json - Machine-readable source of truth for all techniques
- app/README.md - Visualizer setup and usage
- .claude/skills/ - Claude AI skills for automated attack flow generation
SITF includes two Claude AI skills that automate attack flow generation and technique proposal creation:
Automatically generates SITF-compliant attack flow JSON files from attack descriptions or incident reports.
Usage:
/attack-flow <attack-name> [websearch|url]
/attack-flow solarwinds websearch
/attack-flow codecov https://about.codecov.io/security-update/
What it does:
- Researches the attack (via web search or provided URL)
- Maps attack steps to SITF techniques from
techniques.json - Calculates proper layout for visualization
- Generates JSON file in
sample-flows/directory - Identifies technique gaps and recommends using
/technique-proposal
See .claude/skills/attack-flow/SKILL.md for detailed documentation.
Generates PR-ready technique proposals when an attack step doesn't map to existing SITF techniques.
Usage:
/technique-proposal "<description>" [component]
/technique-proposal "Malware invokes AI CLI tools with permission-bypass flags" endpoint
What it does:
- Analyzes the gap against existing techniques
- Assigns the next sequential technique ID
- Generates complete technique definition (name, description, risks, controls)
- Produces PR-ready markdown with rationale and references
See .claude/skills/technique-proposal/SKILL.md for detailed documentation.
Manual Method:
- Edit
techniques.json- the source of truth - Run
python3 build-techniques.pyto regenerate documentation and web app - Commit all changes (JSON, Markdown, and HTML)
- Submit PR or use locally
Automated Method (with Claude):
- Use
/technique-proposalto generate a complete technique definition - Add the generated JSON to
techniques.json - Run
python3 build-techniques.pyto regenerate documentation - Submit PR with the proposal rationale
The build script generates:
TECHNIQUE_LIBRARY.md- Human-readable documentationapp/techniques-library.html- Visual technique explorer with filtering and searchapp/visualizer.html- Interactive attack flow builder
Manual Method:
- Use the online visualizer to build flows interactively
Automated Method (with Claude):
- Use
/attack-flow <attack-name> websearchto automatically generate flows from incident reports
Target Audience: Incident Response Teams, Security Architects, Threat Intelligence Teams, Security Engineers
Focus: Protecting producer organizations (software vendors, OSS maintainers) who create supply chain components