Appearance
Overview
The imper.ai collector script runs on your managed Mac and Windows devices, collects device signals, and sends them to imper.ai for analysis. Each run is a snapshot of the device at that moment, so the script runs again on a schedule to keep monitoring the device after hire.
The collector script:
- Reads device, software, network and security information. Every read is read-only.
- Sends the result to imper.ai in a single HTTPS request.
- Does not install software, create services or scheduled tasks, or change system settings.
What the collector collects
- Configurations: system, software and security settings, such as the operating system version, installed apps and what starts automatically.
- Files: specific files that can indicate risk, such as file transfer tool settings and upload logs.
- Network layout: the network the device is on, such as its gateway details.
- Usage: how the device is used and accessed, such as running programs, remote sessions and attached devices.
What the collector doesn't collect
- Passwords and other credentials. Passwords, keys and tokens are masked on the device before anything is sent, and imper.ai filters again when the result arrives, before it is stored.
- Personal data. The collector only reads data that is needed for detection of malicious or fraudulent use.
How the script reaches your devices
| MDM | Who deploys the script | Setup |
|---|---|---|
| Iru (Mac) | imper.ai, through the Iru integration | Integrating Iru with imper.ai |
| Microsoft Intune (Windows) | You, from the Intune admin center | Integrating Microsoft Intune with imper.ai |
Choose how often it runs
Run the script on a recurring schedule so new risks are detected after the device is first checked. See Running the Collector from Your MDM for how to set the schedule in Iru and Microsoft Intune.
Related articles
Need help or have a question? support@imper.ai