Rule taxonomy / Open the evidence atlas
Every rule.
Its own line of inquiry.
184 detection rules across 17 threat categories and 73 sub-categories. Explore what each rule inspects, its evidence requirements, and its security context.
The catalogue describes available checks. A server report records which checks actually ran, and which inputs or observations remain unresolved.
Security Category Deep Dive
Select a category to explore sub-categories, findings, and compliance coverage.
02
A rule opens a question.
Its evidence answers it.
Follow a category into its rules, inspection methods and required inputs. Framework mappings provide context for the finding; a server assessment records whether the rule had the evidence it needed to run.
The catalogue excludes retired checks from its available-rule totals. Historical findings can still name a retired rule without claiming that the current engine executes it.
A catalogue entry describes an available check, not a successful execution against every server.
Explore framework mappingsFrom a rule to a record
Availability is the beginning. Evidence is the answer.
Follow a finding into the registry to inspect its evidence, assessment method, and coverage. An available rule is not a promise that every assessment could execute it.