Talon ForgeTalon Studio v1.0.2-beta
Standards
Enforce consistent detections across every engineer in the workspace — a conformance spec every change request is graded against.
Detection standards
At Talon Forge → Standards (/forge/standards), click New standard to build one from a detection or from scratch, or use Save as standard on a detection's page. A standard is a conformance spec: the fields a detection must fill in, a few numeric minimums, and a naming pattern.
The spec can require any of a fixed list of 16 fields: description, severity, detection type, MITRE technique, data sources, references, tests, false positives, RBA, risk score, query, analytic story, NIST CSF, data model, asset type and confidence.
Numeric thresholds are configurable too — minimum description length, minimum tests, minimum data sources, minimum references — plus a naming-pattern regex the detection name must match.
One standard is active per workspace: Set as workspace standard, or Set as organisation standard for a default that applies wherever a workspace hasn't set its own.
The active standard is checked at the change-request gate for every detection the change touches. With Warn only (the default) violations show as warnings; with Block deploy on violation they stop the change request from merging, and with it the deploy.
A detection's page grades it against the active standard as you author, and the Adopt browser shows a per-rule conformance-gap count against it.
Tip
Set your standard before bulk-importing from the library — each saved detection's page then shows its gaps against it straight away, and every change request that touches one is graded, so imported rules are flagged on the first pass instead of after they're already spread across the workspace.