> For the complete documentation index, see [llms.txt](https://manuals.blusapphire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.blusapphire.io/blusapphire/untitled.md). # Detections ## Overview: BluSapphire SIEM platform enables support for writing and deploy custom SIGMA rules from within BluSapphire Portal. This document is meant for Security Analysts & IT/System Administrators to help answer queries that he/she may have while writing Sigma rule. ## What is Sigma? While we've Snort rules for detecting Network Traffic, Yara Signatures for identifying suspicious files, consider Sigma rules for searching/pattern matching through log data. Sigma is a generic and open signature format that allows analysts to write & describe searches on log data in a straightforward manner. These rules can be converted and applied to many log management or SIEM systems. Writing Sigma rules is easy and follows the YAML format, which is quite flexible to accommodate custom fields. **Note**: Sigma specifications may change over time with versions, in case of any missing or new attribute, please refer to the official SIGMA specifications wiki available at SIGMAHQ with frequent updates. The following pages will help empower your abilities in understanding Sigma format and use them effectively to write/edit Detections. ### --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://manuals.blusapphire.io/blusapphire/untitled.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.