CtrlK
BlogDocsLog inGet started
Tessl Logo

building-detection-rules-with-sigma

Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Low

Low-risk findings.

1 low severity finding. Worth noting, but not necessarily harmful.

Low

W011: Third-party content exposure detected (indirect prompt injection risk).

What this means

The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.

Why it was flagged

The required runtime workflow ingests Sigma rule YAML files from a user-supplied directory (`--directory` / `Path(directory).rglob("*.yml")`), and those YAMLs are free-form text authored by outsiders (e.g., community Sigma rules or downloaded rule sets), which the agent parses into LLM-readable strings (e.g., `rule.title`, `rule.tags`, and error messages) and includes in the generated JSON report (`sigma_output.json`).

Report incorrect finding
Repository
mukul975/Anthropic-Cybersecurity-Skills
Audited
Security analysis
Snyk

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.