MORPHEUS reads software inventory and finding data from navi.db to build a risk-weighted software leaderboard — ranking packages by the number of assets affected, the severity of associated findings, and the presence of KEV or exploit-available flags.
Capabilities
- Queries navi.db software inventory and correlates with finding severity
- Ranks packages by asset spread, critical finding count, and KEV presence
- Identifies end-of-life software with active findings
- Gated leaderboard report — proposed, previewed, sent only on confirm
What MORPHEUS Ranks
MORPHEUS reads the software inventory MIMIR catalogued and cross-references it with finding data — building the leaderboard that answers "which package, if patched today, would close the most critical findings across the most assets?" The answer comes from navi.db, not a guess.
Why It Matters
Patch prioritisation by CVSS alone misses the blast radius. MORPHEUS ranks by real impact — how many assets, how many critical findings, how many KEV entries — so your patching queue reflects actual exposure, not theoretical severity.
Gate Model
Every leaderboard report is proposed and previewed before delivery. MORPHEUS requires explicit per-call confirmation. Works entirely from navi.db — no external feeds.