PROTEUS audits asset classification data in navi.db — finding assets with missing, inconsistent, or contradictory type tags, OS lineage, and criticality scores. It surfaces the classification gaps that skew every downstream priority calculation.
Capabilities
- Queries navi.db for assets with missing or conflicting type and OS tags
- Identifies assets where ACR score doesn't match declared criticality
- Surfaces assets with no owner, no group, and no classification
- Proposes classification corrections — gated, previewed, written only on confirm
What PROTEUS Audits
PROTEUS reads the asset classification data already in navi.db — type tags, OS lineage, ACR scores, group membership — and finds the contradictions: the server tagged as a workstation, the critical asset with a default ACR of 1, the host with no classification at all.
Why It Matters
Every priority calculation downstream depends on accurate asset classification. PROTEUS ensures the foundation is sound — working entirely from navi.db, proposing corrections for your review before anything is written.
Gate Model
All proposed classification corrections are previewed before any write. PROTEUS requires explicit per-call confirmation. Works entirely from navi.db — no external feeds.