Overview
Vanta integrates with Iru (formerly Kandji) to sync device inventory and compliance data, supporting automated device trust monitoring. By pulling device posture and enrollment information, Vanta helps ensure that only compliant devices retain access to company systems, simplifying device access reviews and compliance evidence collection.
How it works
Iru is a Mobile Device Management (MDM) platform that manages device enrollment, configuration, and security posture across your organization. Vanta’s Access integration connects to Iru and syncs device inventory, enrollment status, and device posture information on a recurring schedule. Vanta performs an initial import upon connection and continues syncing data on an hourly basis. This data enables Vanta to evaluate device security controls and generate evidence for device-related compliance checks.
Use cases
Connecting Iru enables Vanta to:
Maintain accurate visibility into device enrollment and compliance status
Enforce device trust by ensuring only compliant, managed devices retain access
Continuously monitor device posture and security policy adherence
Support audit readiness with authoritative device and user data
Requirements
To connect the Iru integration, you must have:
An Administrator account in your Iru admin dashboard
A Vanta account with permission to add or manage integrations
An Iru API token with read-only access to device and user data
Connect the integration
Step 1: Create an API token in Iru
Sign in to your Iru admin dashboard.
Navigate to Account → Access → API Tokens (menu names may vary depending on your UI version).
Click Add Token (or similar).
Assign the token a descriptive name, for example: Vanta Integration — <date>.
Save the token and securely copy the token value. You will paste this into Vanta.
Configure token permission
Click Configure Permissions.
Grant read-only permissions (GET endpoints) that allow access to:
Devices (device inventory)
Users (device owner / assigned user)
Library (if you want application metadata to appear in Vanta)
Note: If Iru lists named API scopes, pick the minimal read-only scopes that cover Devices, Users, and Library. There is no need to grant write permissions for this integration.
Step 2: Add Iru In Vanta
In your Vanta dashboard, go to Settings → Integrations.
Locate Iru and click View details.
Click Connect to open the credentials modal.
Paste the API token generated in Iru into the API Token field.
Enter your Iru API url (example): https://subdomain.api.kandji.io
Tip: Use the exact API URL displayed in the Access section of your Iru Admin dashboard.Click Save (or Connect) to submit your Iru credentials to Vanta.
Step 3: Verify the connection
After connecting, Vanta will perform an initial sync.
To confirm the integration is working:
Verify that device inventory and attributes appear in Vanta’s device list.
Confirm that device counts and key details (owner, OS, last check-in, serial number) match the Iru admin console.
If fewer devices appear in Vanta:
Verify the API token’s scopes.
Confirm that the token’s account has visibility into all devices.
Sync behavior & token rotation
Sync Frequency
Vanta performs an initial import upon connection and continues syncing on an hourly schedule. You can trigger a manual resync from Vanta’s integration page if you need changes reflected immediately.
Rotating API Tokens
To rotate your API token:
Generate a new read-only taken in Iru.
Update the token value in Vanta’ Iru integration settings.
Save and confirm a successful sync.
Revoke the old token only after verifying the new token is functioning properly.
Permissions
Vanta accesses the following data from Iru:
Read Access
Vant can access:
Device inventory and metadata (OS, serial number, model, last check-in, tags, etc.)
Device enrollment and management status
Device posture / compliance details reported by Iru
Associated device user/owner information
Write Access
Vanta does not write to Iru. The integration uses read-only access and does not modify any data in your Iru environment.
Troubleshooting
Invalid API token
If you receive an invalid token error:
Ensure the token was copied correctly.
Confirm that the token has not expired or been revoked.
Verify that the token includes the required read-only scopes.
If needed, generate a new token in Iru and reconnect the integration.
Fewer devices in Vanta than Iru
If fewer devices appear in Vanta than in Iru:
Confirm that the token’s associated account has visibility into all devices.
Verify that there are no Iru filters limiting device visibility.
Ensure the token’s scopes include access to Devices and Users.
If issues persist, contact Vanta Support and include:
A screenshot of the error
The Iru admin URL entered in Vanta
Confirmation of the token’s assigned permissions
Frequently Asked Questions
Do I need to change anything because Kandji rebranded to Iru?
No. Kandji’s rebrand to Iru does not require any changes to your integration. The Kandji admin dashboard and panel URLs continue to use kandji.io.
You may optionally update internal references to display “Iru (formerly Kandji)” for clarity.
What scopes or permissions does the API token need?
The API token must allow read-only access to Devices and Users. If you want Vanta to ingest Library metadata, include read access for Library as well. Select the minimal read-only scopes exposed by Iru that cover these resources.
Will Vanta ever write to Iru?
No. Vanta uses read-only API access and does not modify any data in your Iru environment.