writing-sigma-detection-rules
Converts hunt findings into portable Sigma detection rules: choosing the right
v1.0.03 instalaciones+3 en 7 días24 EstrellasApache-2.0sincronizado hace 10 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install meltedinhex/writing-sigma-detection-rulesEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquetefbe8ec0e…4714f248
fbe8ec0e9c7d…cc1f4714f2484 archivos · 3.0 KBEscaneoMedio3 hallazgos
- Script ejecutable incluido con la skillscripts/analyst.py
- command.base64_execscripts/analyst.py:34
- Enlaces a dominios externos
Fuentegithub.com/meltedinhex/analyst-ai-pack/tree/main/skills/writing-sigma-detection-rules@da7600a
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When to Use
- A hunt produced reliable logic and you want a portable, SIEM-agnostic detection.
- You need to share or version a detection in a standard format and tag it to ATT&CK.
- You are translating a vendor query into Sigma for reuse across backends.
Do not use Sigma for stateful/correlation logic it cannot express well (complex sequence or statistical detections) — keep those in the SIEM's native correlation engine.
Prerequisites
- The
sigmaCLI /sigma-cli(pysigma) for validation and conversion. - Knowledge of the target log source's field names and the Sigma taxonomy.
Workflow
Step 1: Define the logsource
Pin category/product/service precisely (e.g., product: windows,
category: process_creation) so the rule maps to the right pipeline.
Step 2: Write robust selection logic
Express the detection on stable fields. Prefer multiple ANDed conditions over a single brittle
string; use contains/endswith modifiers thoughtfully to resist evasion.
python scripts/analyst.py scaffold --title "Encoded PowerShell" --category process_creation \
--technique T1059.001 --level highStep 3: Add filters to cut false positives
Use a filter block (negated in the condition) to exclude known-good processes/paths rather
than narrowing selection until it misses variants.
Step 4: Tag and document
Add tags (ATT&CK technique), level, status, references, and a falsepositives list so
consumers can tune.
Step 5: Validate and convert
Lint the rule, then convert to the target backend and test against true/false-positive data before deploying.
sigma convert -t splunk rules/encoded_powershell.ymlValidation
- The rule passes Sigma schema validation (
sigma check). - It fires on the hunt's true positives and not on the documented benign cases.
- Conversion to the target backend produces a sensible, runnable query.
Pitfalls
- Over-narrow selection that matches one sample and misses the technique.
- Wrong logsource, so the rule never sees the relevant events.
- No
falsepositives/filter, producing a noisy alert that gets ignored.
References
- See
references/api-reference.mdfor the Sigma scaffolder. - Sigma specification and rules repository (linked in frontmatter).
Archivos de esta versión
references/11.2 KB
- api-reference.md1.2 KB
scripts/12.0 KB
- analyst.py2.0 KB
- LICENSE340 B
- SKILL.md3.1 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | Sí | Sí |
| Usa la red | Sí | Sí |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
- MediaArchivo · Script ejecutable incluido con la skillscripts/analyst.py
- MediaComando · command.base64_execscripts/analyst.py:34
- InfoEnlace · Enlaces a dominios externos
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v1.0.0 | 13 nov 2026 | da7600a | fbe8ec0e | Firmada | – |
Más de meltedinhex
Todo de este publicador- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- validating-detections-with-atomic-testsmeltedinhex/validating-detections-with-atomic-tests4
- writing-suricata-and-snort-rulesmeltedinhex/writing-suricata-and-snort-rules3
- writing-a-malware-analysis-reportmeltedinhex/writing-a-malware-analysis-report3
Más en Análisis de malware y ransomware
Ver la categoría- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
- testing-ransomware-recovery-proceduresmukul975/testing-ransomware-recovery-procedures3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login