Device42
Device42 is a CMDB (configuration management database) connector. It brings in your device inventory as tracked in Device42, including devices that may have no security agent at all.
At a glance
| Data provided | Devices |
| Authentication | Username + password |
| Where to configure | Connectors → Add a Connector → Device42 |
Required permissions
| Credential | Required access |
|---|---|
| Username + Password | A Device42 account with read access to the Devices module. No write access is needed. |
Setup
- In Device42, create (or identify) a service account with read access to the Devices module.
- In Navigator, go to Connectors → Add a Connector → Device42.
- Enter the account’s Username, Password, and (if you’re not using the default public demo instance) your instance’s Base URL.
- Save. Navigator validates the credentials and enqueues a first sync immediately.
Vendor documentation
Device42’s own API reference: API Overview (Device42 Documentation). Device42’s docs don’t have a single dedicated page for basic-auth service account setup; the Devices module’s own admin/permissions settings are where read access is granted.
What data this connector provides
- Devices: Device42’s own device inventory, including hardware specs where Device42 tracks them.
Known limitations
- Because Device42 is a CMDB rather than a security tool, it has no concept of agent/EDR coverage. A device appearing only in Device42 should be read as “known to IT,” not as “has security tooling installed.”
- Device42’s hardware-spec fields (RAM, disk) are only mapped in Navigator once their unit of measurement has been confirmed against a real, live response. Some fields may not populate until that’s verified for your instance.