What you are evaluating
The product is an aggregation and ownership plane, not a replacement scanner. Adapter quality for the local stack, configuration-database reconciliation, write-back safety, and the separate Exposures product are the evaluation surface.
A useful evaluation context
A plausible evaluation context is an organization with several inventories that need one asset model and coverage-gap view before arguing about scanner scores.
Documented capabilities
The vendor describes these capabilities in the linked sources. Availability depends on the product edition and supported environment.
- Normalizes and deduplicates asset records from a large adapter catalog spanning endpoint, cloud, identity, and related sources.
- Flags coverage gaps such as assets missing a recent scan, endpoint detection, or single sign-on.
- Exposures unifies vulnerabilities, misconfigurations, identity findings, coverage gaps, and owners on top of that asset model.
Where it fits in the work
- Connect adapters only for systems you own and map each source to an owner before enabling any write-back.
- Reconcile Axonius assets against the configuration-management database and investigate duplicates, ghosts, and uncovered records.
- Use Exposures to route unified findings to owners, then confirm that tickets and exceptions still match the source scanners after deduplication.
APPLY THE IDEA / ILLUSTRATIVE EXERCISE
Make the outcome observable.
In a lab you own, feed Axonius from an endpoint source, an identity source, and a scanner source. Plant one host that exists in DHCP or cloud inventory but lacks endpoint detection and a recent authenticated scan.
Evidence to look for
The planted host appears as a coverage gap with an owner, unified findings do not duplicate it into conflicting tickets, and no write-back occurs unless an operator explicitly approves a lab-safe action.
Use synthetic data and an authorized test environment. Agree the scope and recovery steps before enabling enforcement.
Questions for your evaluation
- Which adapters for the actual stack produce complete, timely records, and which silently drift?
- How are conflicts with the configuration-management database resolved, and who is authoritative?
- What write-back actions are possible, and what approval stops an unsafe change?
Names you may encounter: Axonius Cyber Assets · Axonius Exposures. Historical names do not establish current availability or feature equivalence.