HERMES reads asset ownership data from navi.db and routes approved findings to the correct owner — building the remediation assignment that turns a prioritised finding list into an actionable work queue, without leaving anything unowned.
Capabilities
- Reads owner tags and asset group data from navi.db
- Matches findings to owners by asset, group, and tag hierarchy
- Surfaces unowned findings — assets with no owner tag assigned
- Gated routing report — proposed, previewed, sent only on confirm
What HERMES Routes
HERMES takes the pack's approved findings and maps each one to its owner — reading the tag and group data already in navi.db. It surfaces the gaps too: findings on assets with no owner tag, and assets that belong to a group with no assigned contact.
Why It Matters
A finding without an owner is a finding that doesn't get fixed. HERMES ensures every approved exposure has a named accountable party — working from the ownership data you've already built into your Tenable estate.
Gate Model
Every routing report is proposed and previewed before delivery. HERMES requires explicit per-call confirmation. Works entirely from navi.db — no external feeds.