Skip to main content
Data products

Sigma rules with their provenance

Third-party Sigma rules from public repositories, checked against the attribute rules pySigma applies and deduplicated across sources. Each rule keeps its source, upstream commit and declared licence, and its author when one is named.

Try the rules in my tool, 7 days

Pro €99/month · Enterprise on quote · not in Free or Basic · downloads and polling do not use your request quota

format
Sigma · STIX 2.1
delivery
zip · TAXII 2.1 · sigma-rules
built
—
GET/rules/sigma/download

The rule counts could not be read just now.

—
Capabilities

Key features at a glance.

Provenance on every rule

Source, upstream path, commit or release, author, and the licence the rule or its repository declares.

Checked for pySigma

Each rule passes the attribute checks pySigma applies. Metadata that fails them is repaired and marked in the file; a rule whose detection would need guessing is left out.

One zip

One file per rule at its upstream path, with manifest.json, NOTICE.md and the licence texts. Its ETag changes with its content only: If-None-Match answers 304.

TAXII 2.1 collection

sigma-rules: one STIX 2.1 indicator per rule, pattern_type sigma, with its ATT&CK techniques, read incrementally with added_after.

Versions and withdrawals

A rule changed upstream keeps its STIX id and gets a new version; one removed upstream is revoked and leaves the next zip.

Converted on your side

Convert the rules to your SIEM's query language with sigma-cli or pySigma. No conversion is done on our servers.

Applications

Use cases to evaluate first.

  1. SIEM detections

    Convert a source's folder with sigma-cli to the backend of your SIEM.

  2. Detection engineering

    Compare your detections with each source's rules by ATT&CK technique, through the rules API (attack=) or the attack.* tags of each rule.

  3. OpenCTI

    Import the collection with the TAXII connector, with the decay exclusion described below.

  4. Your own pipeline

    Plain HTTPS and an API key: fetch the zip again when its ETag changes.

Specification

What you receive. Check it before you connect a tool.

Format
The zip: one YAML file per rule under sigma/, at its upstream path, plus manifest.json, NOTICE.md and the licence texts. Over TAXII: one STIX 2.1 indicator per rule, pattern_type sigma.
TAXII collection
sigma-rules, listed beside the IOC collections: a client that polls every collection imports the rules too.
Access
Pro and Enterprise, or a feed trial, with your API key. Downloads and polling do not use the monthly request quota.
Checks
Each rule passes the attribute checks pySigma applies. A repaired rule starts with a comment naming the checks; a Sigma id appears once in the zip.
Refresh
Every source is checked every 6 hours; a new zip is built only when a rule changes.
Versions
A changed rule keeps its STIX id; a withdrawn one comes back with revoked: true.

Before you use them

Licences, OpenCTI and MISP.

Licences

The rules are third-party works under the licences their authors declared, non-commercial and copyleft ones included. Each keeps its licence, and the zip carries NOTICE.md and the licence texts. isMalicious grants no rights beyond those licences.

OpenCTI decay

Add a decay exclusion rule on the label detection-rule, or OpenCTI's decay revokes the rules on its own schedule. A rule ends when its source withdraws it.

MISP

Convert the collection with misp-stix: an indicator with pattern_type sigma becomes a MISP sigma object.

Newest rules

The rules added most recently. Metadata only: the rules themselves are in the zip and the collection.

The latest rules could not be read just now.

FAQ

Frequently asked questions.

How many Sigma rules are there?

The count comes from the latest zip's manifest, which this page could not read just now.

Where do the rules come from?

From public repositories published by third parties. Every rule carries its source, its licence and, when one is named, its author, inside the zip and over TAXII. A rule found in several sources is served once, from the source ranked higher.

Can I use the rules in a commercial product?

It depends on each rule's licence. The rules are third-party works under the licences their authors declared, some of them non-commercial or copyleft. isMalicious grants no rights beyond those licences: check a rule's licence before you redistribute it or build it into a product.

How often are the rules updated?

Every source is checked every 6 hours. A new zip is built only when a rule is added, changed or withdrawn, so a download with If-None-Match answers 304 until then.

Do you convert the rules to my SIEM's language?

No. The rules are served as their authors wrote them, metadata repairs aside, and you convert them with sigma-cli or pySigma, which choose the backend and the pipeline for your SIEM.

Test it with your own indicators.

Start a 7-day trial from your workspace, no card: download the zip with your API key, or poll the rule collections over TAXII, where the trial reads up to 25,000 objects a day. For a larger evaluation, send us your tool and your decision date.

Pro €99/month · Enterprise on quote · not in Free or Basic · downloads and polling do not use your request quota