Skip to content
Back to search

SITF

A comprehensive framework for analyzing and defending against attacks targeting Software Development Life Cycle Infrastructure.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/wiz-sec-public--sitf/badge.svg)](/listings/wiz-sec-public--sitf)

HTML

<a href="/listings/wiz-sec-public--sitf"><img src="/api/listings/wiz-sec-public--sitf/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

🌐 Try Online (No Installation Required)

**[Launch the Flow Builder](https://wiz-sec-public.github.io/SITF/visualizer.html)** - Interactive tool for mapping attack flows

**[Explore Techniques Visually](https://wiz-sec-public.github.io/SITF/techniques-library.html)** - Interactive visual explorer with filtering and search

πŸ€– Use with Claude AI

**Install as a Claude Code plugin** (works in any project):

/plugin marketplace add wiz-sec-public/SITF
/plugin install sitf@sitf

**Automated Attack Flow Generation** - Use Claude skills to automatically generate SITF-compliant attack flows and technique proposals:

| Skill | Purpose | |-------|---------| | `/attack-flow` | Generate flows from public incidents and breach reports | | `/red-team-flow` | Generate flows from red team/pentest engagement reports | | `/technique-proposal` | Create new technique definitions when gaps are identified |

See **[SKILLS.md](SKILLS.md)** for detailed usage instructions and examples.

πŸ“ Use Locally

**Launch builder locally** - Download [visualizer.html](app/visualizer.html) locally, open and build offline

**Explore techniques** - Download [techniques-library.html](app/techniques-library.html) locally, open and browse techniques offline

πŸ“– Documentation

**[Read the Implementation Guide](IMPLEMENTATION_GUIDE.md)** - Complete methodology, case studies, and usage instructions

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json Β· Manifest Β· 17 lines
  1. {
  2. "name": "sitf",
  3. "owner": {
  4. "name": "Wiz",
  5. "url": "https://github.com/wiz-sec-public"
  6. },
  7. "description": "SITF (SDLC Infrastructure Threat Framework) skills for analyzing software supply chain and CI/CD attacks.",
  8. "plugins": [
  9. {
  10. "name": "sitf",
  11. "source": "./",
  12. "description": "Map supply chain, CI/CD, and SDLC incidents and red team engagements to SITF techniques; generate attack flows; propose new techniques.",
  13. "category": "security",
  14. "tags": ["security", "supply-chain", "ci-cd", "threat-modeling", "incident-response"]
  15. }
  16. ]
  17. }
README.md Β· README Β· 142 lines
  1. # SDLC Infrastructure Threat Framework (SITF)
  2. A comprehensive framework for analyzing and defending against attacks targeting Software Development Lifecycle infrastructure: developer endpoints and IDEs, version control (VCS), CI/CD pipelines, artifact and container registries, and production cloud.
  3. **Website:** [wiz-sec-public.github.io/SITF](https://wiz-sec-public.github.io/SITF/) Β· **[Technique reference](https://wiz-sec-public.github.io/SITF/techniques/index.html)** Β· **[Incidents mapped to SITF](https://wiz-sec-public.github.io/SITF/incidents/index.html)**
  4. ## Quick Start
  5. ### 🌐 Try Online (No Installation Required)
  6. **[Launch the Flow Builder](https://wiz-sec-public.github.io/SITF/visualizer.html)** - Interactive tool for mapping attack flows
  7. ![Project Demo](app/demo-visualizer.gif)
  8. **[Explore Techniques Visually](https://wiz-sec-public.github.io/SITF/techniques-library.html)** - Interactive visual explorer with filtering and search
  9. ![Project Demo](app/demo-library.gif)
  10. ### πŸ€– Use with Claude AI
  11. **Install as a Claude Code plugin** (works in any project):
  12. ```
  13. /plugin marketplace add wiz-sec-public/SITF
  14. /plugin install sitf@sitf
  15. ```
  16. **Automated Attack Flow Generation** - Use Claude skills to automatically generate SITF-compliant attack flows and technique proposals:
  17. | Skill | Purpose |
  18. |-------|---------|
  19. | `/attack-flow` | Generate flows from public incidents and breach reports |
  20. | `/red-team-flow` | Generate flows from red team/pentest engagement reports |
  21. | `/technique-proposal` | Create new technique definitions when gaps are identified |
  22. See **[SKILLS.md](SKILLS.md)** for detailed usage instructions and examples.
  23. ### πŸ“ Use Locally
  24. **Launch builder locally** - Download [visualizer.html](app/visualizer.html) locally, open and build offline
  25. **Explore techniques** - Download [techniques-library.html](app/techniques-library.html) locally, open and browse techniques offline
  26. ### πŸ“– Documentation
  27. **[Read the Implementation Guide](IMPLEMENTATION_GUIDE.md)** - Complete methodology, case studies, and usage instructions
  28. ## What is SITF?
  29. SITF helps security teams analyze supply chain attacks by:
  30. - Visualizing attack stages across SDLC components (Endpoint, VCS, CI/CD, Registry, Production)
  31. - Identifying the risks that enabled each attack technique
  32. - Mapping risks to appropriate security controls
  33. - Understanding attack paths and lateral movement patterns
  34. ## Framework Components
  35. - **5 Infrastructure Components**: Endpoint/IDE, VCS, CI/CD, Registry, Production/Cloud
  36. - **80+ Attack Techniques**: Pre-mapped with enabling risks and security controls
  37. - **Dual Control Types**: Protective controls (prevent attacks) and Detective controls (detect attacks)
  38. - **Framework Mappings**: Controls mapped to industry frameworks (OWASP SPVS)
  39. - **Interactive Visualizer**: Drag-and-drop interface for building attack flow diagrams
  40. - **Real-World Case Studies**: CircleCI breach, Shai-Hulud-2, TrustWallet, tj-actions, CodeBreach, s1ngularity
  41. ## Documentation
  42. - [IMPLEMENTATION_GUIDE.md](IMPLEMENTATION_GUIDE.md) - Start here for complete framework overview
  43. - [TECHNIQUE_LIBRARY.md](TECHNIQUE_LIBRARY.md) - Reference catalog of all techniques
  44. - [techniques.json](techniques.json) - Machine-readable source of truth for all techniques
  45. - [Technique reference](https://wiz-sec-public.github.io/SITF/techniques/index.html) - One web page per technique (e.g. [SITF T-C003](https://wiz-sec-public.github.io/SITF/techniques/T-C003.html))
  46. - [app/README.md](app/README.md) - Visualizer setup and usage
  47. - [SKILLS.md](SKILLS.md) - Claude AI skills documentation and usage examples
  48. ## Claude AI Skills
  49. SITF includes Claude AI skills for automated attack flow generation. See **[SKILLS.md](SKILLS.md)** for complete documentation.
  50. | Skill | Input | Output |
  51. |-------|-------|--------|
  52. | `/attack-flow` | Incident name, URL, or web search | `flows/incidents/<name>.json` |
  53. | `/red-team-flow` | Engagement report (file/URL/text) | `flows/red-team/<name>.json` |
  54. | `/technique-proposal` | Gap description | `technique-proposals/<id>.md` |
  55. ## Using SITF Data
  56. SITF content is published in machine-readable forms for tools, RAG pipelines, and AI agents:
  57. | Resource | URL |
  58. |----------|-----|
  59. | Full dataset (techniques, risks, controls, framework mappings) | https://wiz-sec-public.github.io/SITF/techniques.json |
  60. | Per-technique pages | `https://wiz-sec-public.github.io/SITF/techniques/<ID>.html` |
  61. | LLM index ([llms.txt](https://llmstxt.org)) | https://wiz-sec-public.github.io/SITF/llms.txt |
  62. | All techniques as plain text | https://wiz-sec-public.github.io/SITF/llms-full.txt |
  63. | Attack flows (incidents and red team) | [flows/](flows/) |
  64. Technique IDs are prefixed by component: `T-E` Endpoint/IDE, `T-V` VCS, `T-C` CI/CD, `T-R` Registry, `T-P` Production/Cloud.
  65. ## Citing SITF
  66. When referencing a technique, include the framework name, e.g. **"SITF technique T-C003 (PWN Request / Poisoned Pipeline Execution)"**, and link to its page. To cite the framework itself, use [CITATION.cff](CITATION.cff) (GitHub's "Cite this repository" button).
  67. ## Contributing
  68. ### Adding or Modifying Techniques
  69. **Manual Method:**
  70. 1. Edit [`techniques.json`](techniques.json) - the source of truth
  71. 2. Run `python3 build-techniques.py` to regenerate documentation and web app
  72. 3. Commit all changes (JSON, Markdown, and HTML)
  73. 4. Submit PR or use locally
  74. **Automated Method (with Claude):**
  75. 1. Use `/technique-proposal` to generate a complete technique definition
  76. 2. Add the generated JSON to [`techniques.json`](techniques.json)
  77. 3. Run `python3 build-techniques.py` to regenerate documentation
  78. 4. Submit PR with the proposal rationale
  79. The build script generates:
  80. - `TECHNIQUE_LIBRARY.md` - Human-readable documentation
  81. - `app/techniques-library.html` - Visual technique explorer with filtering and search
  82. - `app/visualizer.html` - Interactive attack flow builder
  83. - `app/techniques/`, `app/incidents/` - Static, crawlable per-technique and per-incident pages (via `build_site.py`)
  84. - `app/llms.txt`, `app/llms-full.txt`, `app/sitemap.xml`, `app/techniques.json` - Machine-readable and search-engine outputs
  85. New flows in `flows/incidents/` or `flows/red-team/` get an incident page automatically on the next build; add a display name to `FLOW_TITLES` in `build_site.py`.
  86. ### Creating Attack Flows
  87. **Manual Method:**
  88. - Use the [online visualizer](https://wiz-sec-public.github.io/SITF/visualizer.html) to build flows interactively
  89. **Automated Method (with Claude):**
  90. - Use `/attack-flow <attack-name> websearch` to automatically generate flows from incident reports
  91. ---
  92. **Target Audience**: Incident Response Teams, Security Architects, Threat Intelligence Teams, Security Engineers
  93. **Focus**: Protecting producer organizations (software vendors, OSS maintainers) who create supply chain components
  94. ---
  95. Starting April 14 2026, SITF is licensed under CC BY-NC 4.0. Versions prior to this date remain under CC BY-NC-ND 4.0.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.