Control agent requirements - Idemeum Docs
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Operating system support
- Windows
- macOS
| Operating system | x64 | ARM | Products |
|---|---|---|---|
| Windows 10 | Yes | - | ALEPMMSP JIT |
| Windows 11 | Yes | Yes | ALEPMMSP JIT |
| IoT Enterprise | Yes | - | ALEPMMSP JIT |
| Server 2016 | Yes | - | MSP JIT |
| Server 2019 | Yes | - | MSP JIT |
| Server 2022 | Yes | - | MSP JIT |
| Server 2025 | Yes | - | MSP JIT |
| Operating system | Intel | Apple Silicon | Products |
|---|---|---|---|
| macOS 14 Sonoma | Yes | Yes | ALEPMMSP JIT |
| macOS 15 Sequoia | Yes | Yes | ALEPMMSP JIT |
| macOS 26 Tahoe | Yes | Yes | ALEPMMSP JIT |
Network requirements
The control agent does not listen on any port for traffic initiated external to the localhost, thus does not increase potential attack vectors. However, as outbound connections are made, any egress filtering performed by antivirus software, firewalls, routers, etc. would need to be opened. Idemeum control agent will leverage the following protocols and ports:
| Port | Transport protocol | Purpose |
|---|---|---|
| 443 | TCP | HTTPs |
| 5228 | TCP | Notifications |
The following URLs are used:
dvmi.idemeum.comasset.idemeum.com<tenant name>.idemeum.com(i.e.demo-nikpot.idemeum.com)mtalk.google.com(for incoming notifications from FireBase)
If your firewall or domain filtering solution supports wildcard you may want to allow *.idemeum.com
DLLs and executables
Idemeum control agent is installed in the following location on Windows - C:\Program Files\Idemeum Inc\Idemeum Desktop Client. There are a number of executables and DLLs that idemeum control agent is using. All DLLs and executables are signed with idemeum certificate (signer IDEMEUM INC). Also, some of the required DLLs are placed in the System32 folder. Those DLLs are also signed.