Your Tenable agent groups already describe how the estate is organized โ but that structure is invisible everywhere tags are consumed. Scans, reports, automation, and every downstream hound work from tags, and when tags drift out of sync with deployment reality, segmentation quietly stops meaning anything.
Sirius tags assets by their Tenable agent group, turning deployment structure into clean, queryable tag segmentation. Group membership becomes usable structure everywhere tags are consumed โ one mapping, consistently applied, kept current.
Sirius reads agent-group membership from your Tenable data in the local navi.db and proposes matching tags. All writes are proposed, human-approved, and logged.
Security operations teams who own the tag estate, and anyone who wants scans and reports scoped by how the deployment is actually organized.
In a reference environment of 268 assets, Sirius's group tags are the segmentation backbone the pack's producers and the Contract build on โ structure laid down once, consumed everywhere. Tags propagate to the Tenable UI/API on Tenable's schedule.
Sirius pairs with Garmr โ structure laid down, clutter swept out โ and feeds Covenant, which keeps group tagging current on the Contract's schedule.