<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>opensearch on Raúl Pastor</title><link>https://pixelotes.com/tags/opensearch/</link><description>Recent content in opensearch on Raúl Pastor</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://pixelotes.com/tags/opensearch/index.xml" rel="self" type="application/rss+xml"/><item><title>Sigma Rules Bring Community Detections to Any SIEM</title><link>https://pixelotes.com/blog/sigma-rules/</link><pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate><guid>https://pixelotes.com/blog/sigma-rules/</guid><description>&lt;p&gt;In the &lt;a href="https://pixelotes.com/blog/supply-chain-security/"&gt;previous article&lt;/a&gt; I wrote a handful of KQL queries to hunt for a backdoored IDE extension. They work in Microsoft Sentinel and Defender. They are useless in Splunk, Elastic or OpenSearch.&lt;/p&gt;&#10;&lt;p&gt;That is the core problem of detection engineering: every SIEM speaks its own language, and detection knowledge gets locked inside whichever product you happen to run. Sigma fixes that.&lt;/p&gt;&#10;&lt;h2 id="what-sigma-is"&gt;What Sigma is&lt;/h2&gt;&#10;&lt;p&gt;&lt;a href="https://github.com/SigmaHQ/sigma"&gt;Sigma&lt;/a&gt; is an open, generic signature format for log events. A Sigma rule is a YAML file that describes &lt;em&gt;what&lt;/em&gt; to look for (which log source, which fields, which values) without saying &lt;em&gt;how&lt;/em&gt; a specific SIEM should query it. A converter then translates the rule into the target query language.&lt;/p&gt;</description></item></channel></rss>