defensive-ssti

Identify SSTI patterns in HTTP parameters across templating engines.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/riparino/Claude-Cyber --skill defensive-ssti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defensive-ssti
Source: https://github.com/riparino/Claude-Cyber/tree/main/Claude-Blue/Skills/defensive-ssti
Command: npx skills add https://github.com/riparino/Claude-Cyber --skill defensive-ssti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SSTI detection across common templating engines to identify unsafe template rendering and potential code execution surfaces in web applications.

Core Features & Use Cases

  • Engine-agnostic SSTI patterns across Jinja2, Twig, Freemarker, Velocity, and ERB.
  • Sigma and KQL-based detections for WAF logs and SIEM alerting.
  • SOC-focused triage guidance and hardening recommendations.

Quick Start

Run SSTI detection against the latest web logs to surface template injection signals.

Frequently Asked Questions about defensive-ssti

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect SSTI vulnerabilities across multiple templating engines in HTTP logs?

Detect SSTI vulnerabilities by scanning HTTP parameters for engine-agnostic injection patterns across Jinja2, Twig, Freemarker, Velocity, and ERB. The Skill generates Sigma rules and KQL queries to surface template injection signals in WAF logs and SIEM alerts.

What is the best way to write KQL or Sigma rules for server-side template injection triage?

The best way to write KQL or Sigma rules for server-side template injection is to map engine-specific syntax patterns to MITRE ATT&CK techniques. This provides SOC-focused triage guidance and identifies unsafe template rendering surfaces in web application logs.

Can I use this to detect Jinja2 and Twig template injection patterns in my WAF logs?

Yes, you can detect Jinja2 and Twig template injection patterns in WAF logs. The Skill identifies unsafe template rendering across these engines, leveraging Sigma rules and KQL queries to alert on potential code execution surfaces.

How do I get hardening recommendations after identifying SSTI patterns during SOC triage?

You get hardening recommendations by running SSTI detection against your latest web logs. The Skill maps findings to MITRE ATT&CK and provides actionable hardening recommendations alongside SOC triage guidance to secure unsafe template rendering.

Does SSTI detection work for Freemarker and Velocity template rendering engines?

SSTI detection works for Freemarker and Velocity by scanning HTTP parameters for engine-agnostic template injection patterns. It applies Sigma and KQL-based detections to identify potential code execution surfaces across these specific templating engines.