Getting to a Unified View.
Using the platform’s extensible framework, customers are able to use adapters to connect to their existing systems via APIs. This creates an abstraction layer to devices and provides a unified point of view for visibility and control.
Featured Example: Active Directory Adapter
Different properties of each device are present in different silos within the organization. What do we need to see the device for what it is? What information would we need to determine whether a device needs updating?
Firstly, in order to understand its network positioning (Is it in production or the corporate net? Is it internet facing or not?) we would go to the solutions that look at the device from a network perspective: the firewall, the vulnerability assessment tool, and/or the NAC.
Next, in order to get a precise and accurate reading of the OS version, we would need to use an asset management system, such as SCCM/Active Directory. This will enable us to also understand the software installed on the device and the respective version and requirements for updating.
But what happens if that device doesn't have an agent and we're required to get the data only from Active Directory? Should we access each one through RPC/WMI just to get a reading of the software version? All of these different siloed properties would be able to be gathered and used through Axonius adapters.
AD is just a single example of an adapter. Many other adapters are available to integrate with tools like firewalls, endpoint protection solutions, asset management systems, and more.