Uncoder IO is an open-source version of it's SaaS counterpart https://uncoder.io and its AI co-pilot version Uncoder AI. Since 2018, Uncoder IO has been a fast, private, and easy-to-use online translator for Sigma Rules, maintaining 100% privacy of its users. An open-source Uncoder IO expands use cases into the following:
- Translation from Sigma Rules, a generic rule format for SIEM systems, to specific SIEM, EDR, and Data Lake languages
- IOC packaging from any non-binary format such as PDF, text, STIX, or OpenIOC to specific SIEM, EDR, and Data Lake languages
- Translation from Roota Rules, the newly released language for collective cyber defense, to specific SIEM, EDR, and Data Lake languages.
Uncoder is developed by a team of Detection Engineers, Threat Hunters, and CTI Analysts from Ukraine, Europe, USA, Argentina, and Australia to perform their daily job and nightly cyber defense hobbies faster & better, making their outcomes easier to share for the collective good.
Table of Contents:
- Why Uncoder IO
- Supported Language Formats
- Installation
- How to Use
- How to Contribute
- Questions & Feedback
- Maintainers
- Credits
- Licenses
- Resources & Useful Links
Uncoder IO supports automated translation of Roota and Sigma rules into multiple SIEM, EDR, XDR, and Data Lake formats.
-
Sigma is a generic and open signature format that allows you to describe relevant log events in a straightforward manner, which received industry adoption across 155 countries by over 8000 organizations according to SOC Prime's download and translation statistics.
-
Roota is an open-source language that supports query definition directly in specific SIEM languages, vendor-agnostic correlation syntax, MITRE ATT&CK 14.0 for code autocompletion, and log source taxonomy autocomplete function based on Amazon's OCSF or Sigma. Roota+Uncoder serve as the first bridge towards full cyber security languages compatibility, where one day, knowing one specific language (say SPL or KQL) or generic language (say Roota or Sigma) would mean that you have master expertise in them all. This way, your complex detection logic can be rendered in other languages in an automated fashion. In case a native rule or query contains functions unsupported by Roota or target technology, those functions won’t be translated, with a corresponding note appended to the code translation. This is done so that experts can either manually complete translations if they know both source and destination languages, or use Uncoder AI to manually take care of such scenarios. If sharing with Sigma was easy, sharing with Roota is natural and future-proof.
Uncoder IO supports a built-in Sigma and Roota rules autocompletion wizard suggesting code enhancements with latest MITRE ATT&CK and log source dictionaries to streamline the rule creation process. AI or not, Uncoder is here to make it easier to code.
Uncoder IO acts as an open-source IOC packager helping CTI and SOC analysts as well as Threat Hunters to quickly parse any number of IOCs directly from any digital non-binary format (a simple copy-paste of a web page, CSV, OpenIOC, PDF, STIX etc.) and convert them into performance-optimized IOC queries ready to run in a chosen security analytics platform. As Indicators of Compromise sharing is regulated by TLP, it is not advised to share them in Sigma or Roota rules, as the latter are not part of threat intelligence and thus are shared easily without borders. Yet, we need IOC matching just as we need Threat Behavior detections, so Uncoder IO is made to help solve both tasks in an easy-to-use and intuitive manner.
Uncoder IO can be run on-prem without a need for an internet connection, thus supporting air-gapped network operation. We do however suggest checking for updates and deploying them regularly. Meanwhile, a SaaS version still ensures 100% privacy with no cookie tracking, no data or code logging, or sharing with third parties. Even with options for Uncoder AI functions, you are always in control of your code and data.
Roota and Sigma Rules can be translated into the following formats:
- AWS OpenSearch Query -
opensearch-lucene-query - AWS Athena Query (Security Lake) -
athena-sql-query - Falcon LogScale Query -
logscale-lql-query - Falcon LogScale Rule -
logscale-lql-rule - Splunk Query -
splunk-spl-query - Splunk Alert -
splunk-spl-rule - Microsoft Sentinel Query -
sentinel-kql-query - Microsoft Sentinel Rule -
sentinel-kql-rule - Microsoft Defender for Endpoint Query -
mde-kql-query - IBM QRadar Query -
qradar-aql-query - CrowdStrike Query -
crowdstrike-spl-query - Elasticsearch Query -
elastic-lucene-query - Elasticsearch Rule -
elastic-lucene-rule - ElastAlert Rule -
elastalert-lucene-rule - Sigma Rule -
sigma-yml-rule - Chronicle Security Query -
chronicle-yaral-query - Chronicle Security Rule -
chronicle-yaral-rule - Graylog Query -
graylog-lucene-query - FortiSIEM Rule -
fortisiem-rule - LogRhythm Axon Rule -
axon-ads-rule - LogRhythm Axon Query -
axon-ads-query
IOC-based queries can be generated in the following formats:
- Microsoft Sentinel Query -
sentinel-kql-query - Microsoft Defender for Endpoint Query -
mde-kql-query - Splunk Query -
splunk-spl-query - CrowdStrike Endpoint Security Query -
crowdstrike-spl-query - Elastic Stack Query -
elastic-lucene-query - AWS OpenSearch Query -
opensearch-lucene-query - Falcon LogScale Query -
logscale-lql-query - IBM QRadar Query -
qradar-aql-query - AWS Athena Query (Security Lake) -
athena-sql-query - Chronicle Security Query -
chronicle-yaral-query - ArcSight Query -
arcsight - FireEye Query -
fireeye_helix - Graylog Query -
graylog-lucene-query - Logpoint Query -
logpoint - Qualys IOC Query -
qualys - RSA NetWitness Query -
rsa_netwitness - Securonix Query -
securonix - SentinelOne Query (Events) -
s1-events - Snowflake Query -
snowflake - Sumo Logic Query -
sumologic - VMware Carbon Black Query (Cloud) -
carbonblack
The following types of IOCs are supported:
- Hash
- Domain
- URL
- IP
TODO list of languages we will support shortly:
LogRhythm Axon✅Graylog✅- Devo
- LimaCharlie
- Sumo Logic
- Sumo Logic CSE
- ArcSight
- Databricks
- Cribl
FortiSIEM✅- Exabeam
- Palo Alto Cortex XSOAR
ElastAlert✅- FireEye OpenIOC
- SentinelOne
- Datadog
- FireEye Helix
- Logpoint
- RSA NetWitness
- PowerShell
- Snowflake
- SQL
- VMware Carbon Black
- Apache Kafka ksqlDB
- HawkSearch
- Regex Grep
- Logiq
- Qualys
- Securonix
- STIX
- StreamAlert
- Sysmon
- UberAgent ESA
Uncoder IO can be installed in a following manner:
- Docker container with web server and UI Launch Instructions for Docker container
- Docker container API and CLI only (work in progress)
- Build from source code directly (for advanced users, can be done following instructions from docker files)
- Ready to use as SaaS, privately with no registration or cookies at https://uncoder.io/
- Ready to use at SOC Prime SaaS with private AI augmentation, SOC 2 Type II certified environment and supporting ToS on data privacy, GDPR etc. at https://tdm.socprime.com/uncoder-ai
Below are the requirements and launch instructions for the Docker container with web server and UI.
- Host with Windows, Linux, or other operating system supported by Docker
- These packages should be installed on the host:
- Docker v23.0.1 or newer
- Docker Compose v2.21.0 or newer
- Download the
UncoderIO-mainarchive and unpack it. - In the CLI, go to the folder where the unpacked files are:
cd UncoderIO-main/
- Run the following command to launch a Docker container:
docker-compose up -d
- Open
http://localhost:4010/in your browser and you are ready to go.
- Select input type:
- Roota rule
- Sigma rule
- Paste or upload a rule in the selected language into the input panel.
- Select the output (language, content type, and data schema)
- Click Translate.
If the input rule cannot be translated, you'll see an error message. When translating a Roota rule, any functions that are not supported in the target language or are not yet supported by Uncoder IO will be listed in the output as a comment.
- Select IoCs as the input type.
- Paste or upload text with Indicators of Compromise in the left panel.
- Make parsing configurations:
- Select all: all listed options are applied
- Replace (.) [.] {.} with dot
- Replace hxxp with http: this functionality is case insensitive, so hXXp, HXXP, HXXp, and hXXP are replaced as well
- Exclude Private & Reserved Networks: private and reserved IP addresses like 224.0.0.0/4 or 127.0.0.0/8 are ignored during IOC recognition
- Select the output language.
- Make generation settings:
- Select what IOC types to use for queries:
- Hash
- Domain
- URL
- IP
- Set the number of IOCs per query to take into account the performance of your platform
- Define exceptions: specify hashes, domains, IPs, or URLs (in full or only partially) you want to exclude from your queries
- Select what IOC types to use for queries:
- Click Translate.
Write a Roota or Sigma rule in the input panel. Benefit from code templates, syntax highlighting, autocomplete suggester with MITRE ATT&CK, and other nice little features that improve coding experience.
Thank you for your interest in the Uncoder IO open-source project! Your contribution really matters in evolving the project and helping us make Uncoder IO even more useful for the global cyber defender community.
We encourage you to commit renders into new platforms. Start with reading these Instructions on Adding New Renders.
To submit your pull request with your ideas or suggestions for changes, take the following steps:
- Fork the Uncoder repository and clone your fork to your local environment.
- Create a new feature branch, in which you’re going to make your changes.
- Сommit your changes to your newly created feature branch.
- Push the changes to your fork.
- Create a new Pull Request
a. Clicking the New Pull Request button.
b. Select your fork along with a feature branch.
c. Provide a title and a description of your changes. Make sure they are both clear and informative.
d. Finally, submit your Pull Request and wait for its approval.
Thank you for your contribution to the Uncoder IO project!
Please submit your technical feedback and suggestions to [email protected] or the dedicated Uncoder channel in SOC Prime’s Discord. Also, refer to the guidance for contributors to support the Uncoder IO project or simply report issues.
Since 2018, the SOC Prime team has been developing Uncoder from the ground up. The first steps were our support of Sigma rules and the Uncoder IO project, an online yet fully private IDE for detection engineering. Now, the SOC Prime Team shares Uncoder IO as an open-source project.
Uncoder IO project is maintained by SOC Prime, and while any suggestions and reported issues are welcome, the ultimate decision to accept a pull request or not, will be up to SOC Prime's R&D team.
We are genuinely grateful to security professionals who contribute their time, expertise, and creativity to evolve the Uncoder open-source project.
Uncoder IO Comunity Edition is licensed under Apache 2.0. Commercial Edition features that are released as open-source can be used non-commercially if you do not have a paid SOC Prime subscription. Commercial use rights are complimentary with SOC Prime SaaS license. Please see LICENSE for details on the Uncoder IO licensing.
Uncoder IO - free online translation engine for Roota, Sigma, and IOC-based queries
Uncoder AI - SaaS version of Uncoder acting as advanced IDE for detection engineering
Roota.IO - the main website page of the single language for threat detection & response
SOC Prime Platform - the industry-first platform for collective cyber defense
About SOC Prime - learn more about SOC Prime and its mission