opensearch-detection-engineer

Translate SIGMA rules into OpenSearch Security Analytics detectors with field validation.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/vexjoy-agent --skill opensearch-detection-engineer
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: opensearch-detection-engineer
Source: https://github.com/notque/vexjoy-agent/tree/main/skills/engineering/opensearch-detection-engineer
Command: npx skills add https://github.com/notque/vexjoy-agent --skill opensearch-detection-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents broken or unsafe SIEM detections by enforcing OpenSearch Security Analytics methodology, strict field validation, MITRE ATT&CK completeness, and production-grade safety checks before any detector or monitor is created.

Core Features & Use Cases

  • SIGMA-first detection authoring with OpenSearch Security Analytics translation patterns to produce deterministic, vendor-neutral rules.
  • Field existence and schema validation using OpenSearch mapping checks (GET index/_mapping) to avoid silent failures from missing or mis-typed fields.
  • MITRE ATT&CK mapping and escalation-ready packages that require technique ID + tactic and a validated 9-field SOC escalation payload for Tier-1/Tier-2 workflows.
  • OpenSearch detection safety guardrails that detect chained findings index flood risk and field alias bootstrap conflicts, with concrete remediation steps.

Quick Start

Use the opensearch-detection-engineer skill to translate a given SIGMA rule into OpenSearch Security Analytics detector and verify every referenced field exists in the target index mapping before you propose creation.

Frequently Asked Questions about opensearch-detection-engineer

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

FAQPage Schema
How do I translate SIGMA rules into OpenSearch queries safely?โ–ผ

Translating SIGMA rules into OpenSearch queries safely requires mapping-based field validation via GET {index}/_mapping and detection-safety checks to prevent broken detectors or silent failures from missing fields.

Why do my OpenSearch SIEM detections fail silently after creation?โ–ผ

OpenSearch SIEM detections fail silently when fields are missing or mis-typed. Applying OpenSearch mapping checks via GET index/_mapping validates field existence against the target index before creating detectors.

What is included in a MITRE ATT&CK escalation-ready SOC package?โ–ผ

A MITRE ATT&CK escalation-ready package requires a technique ID plus a tactic, and generates a validated 9-field SOC escalation payload to support Tier-1 and Tier-2 incident response workflows.

How do I prevent a chained findings index flood in OpenSearch Security Analytics?โ–ผ

Prevent a chained findings index flood by applying OpenSearch detection safety guardrails that identify flood risks and field alias bootstrap conflicts, then executing concrete remediation steps before detector creation.

Can I use this approach for false-positive tuning and anomaly rule design?โ–ผ

Yes, this methodology applies to SIEM detection authoring, anomaly and correlation rule design, detector failure diagnosis, and false-positive tuning workflows within OpenSearch Security Analytics environments.

Do I need OpenSearch mapping checks before creating SIEM detectors?โ–ผ

Yes, mapping-based field validation using GET {index}/_mapping is required to verify every referenced field exists in the target index mapping before creating OpenSearch Security Analytics detectors.