Skip to content

Rule Categories

A TrustSight rule makes one kind of claim. That claim is its category (the RuleCategory value, sometimes called its subject). There is exactly one category per rule, the set is closed, and each category owns exactly one documentation page.

A category page does two jobs at once, because a reader needs both:

  • it explains where the idea comes from and what a finding means (the threat context and interpretation); and
  • it carries the definition of every rule in the category, with severity, target, scope and limitations.

Those halves used to live on separate System and Nature pages. They are now one canonical page per category, so there is no parallel navigation to keep in step. The taxonomy itself is still defined in src/trustsight/categories.py; tests/test_docs.py fails if a rule is documented on a page its category does not own.

Category is not capability, and not series

Three labels are easy to confuse:

  • Category answers what kind of claim does this rule make? It decides which page owns the rule.
  • Capability is the per-rule category field in rules.toml (network_execution, installer, obfuscation). It names what a match touched and is used by H027 to count capability density.
  • Series answers how does the rule detect? It is the leading letter of the rule ID. See Rule Series.

A rule can carry category = "meta" as its capability and belong to the Composition subject. The full side-by-side comparison is in Rule Labels Explained.

The categories

The generated table in Rules Overview is the canonical index. The pages themselves are:

Code reaches the machine and runs

Trust, identity and history

Composition and cross-package signals

Evidence outside the static diff

  • Artifact: what actually lands in the built package.
  • Indicators: concrete observables from signed data.
  • Unverifiable: claims TrustSight cannot check.

How to use a category page

Each page follows the same order: an overview, the threat context, the detection mechanisms, the individual rule definitions, the interpretation, and related documentation. If you are triaging a finding, read the interpretation section before the definition; the definition explains what matched, while the interpretation explains what that match does and does not establish.