deviceTRUST 23.1.410
This service pack adds detection for Microsoft Intune and introduces the detection of proxies using IP2Location Web Services or MaxMind GeoIP2 Insights Web Service providers. Please refer to Compatibility for changes that may impact users upgrading from previous releases.
The deviceTRUST 23.1.410 patch includes bugfixes to the deviceTRUST Agent and Console. This release includes no changes to the deviceTRUST Client Extension and therefore has not been released on https://devicetrust.com/download.
- Microsoft Intune Detection
- WHOIS Proxy Detection
- Minor enhancements to 23.1.400
- Bug fixes in 23.1.400
- Bug fixes in 23.1.410
- Compatibility
Microsoft Intune Detection
Microsoft Intune can now be detected using our new MDM properties. Microsoft Intune detection is supported on Microsoft Windows and Apple macOS devices.
WHOIS Proxy Detection
The WHOIS properties have been extended with support for proxy, proxy type and usage properties. These properties are taken from the response fields of the IP2Location or MaxMind provider when an appropriate plan is selected.
As part of this change, we’ve renamed LOCAL_WHOIS_VPN and REMOTE_WHOIS_VPN to LOCAL_WHOIS_ADAPTER_VPN and REMOTE_WHOIS_ADAPTER_VPN respectively to ensure clarity with the new proxy properties.
Proxy Detection with IP2Location Web Services
IP2Location Web Services provides proxy detection from the following IP2Location response fields and is available with the following plans:
| Property | Response Field | Free Plan | Starter Plan | Plus Plan | Security Plan |
|---|---|---|---|---|---|
| Proxy |
is_proxy1
|
✓ | ✓ | ✓ | ✓ |
| Proxy Type | proxy.proxy_type |
✓ | |||
| Usage | usage_type |
✓ | ✓ | ✓ |
- 1The accuracy of the `is_proxy` field is dependent upon the selected plan.
Proxy Detection with MaxMind GeoIP2 Insights Web Service
MaxMind GeoIP and GeoLite Web Services provides proxy detection from the following MaxMind response fields and is available with the following plans:
| Property | Response Field | GeoIP2 Country | GeoIP2 City Plus | GeoIP2 Insights | GeoLite Country | Geolite City |
|---|---|---|---|---|---|---|
| Proxy | is_anonymous |
✓ | ||||
| Proxy Type |
is_hosting_provider, is_anonymous_vpn, is_public_proxy, is_residential_proxy, is_tor_exit_node
|
✓ | ||||
| Usage | user_type |
✓ |
Minor enhancements to 23.1.400
- Renamed Microsoft Azure AD to Microsoft Entra ID throughout the console.
- Added a
Use remote client names to connect to iOS devicesadvanced setting, which forces the deviceTRUST Agent to connect to iOS devices by matching the remote client names with those registered within the iOS Portal.
Bug fixes in 23.1.400
- Fixed an issue where a virtual session could be logged off during a live reconnect to a session that had never shown the desktop to the user.
- Fixed an issue with the Logical Disk Identity operator where the None Of operator was shown as Not Equals.
Bug fixes in 23.1.410
- Fixed an issue on Citrix virtual sessions when running a client OS, where the logoff process could get stuck and require a restart of the deviceTRUST Agent before allowing additional logons.
- Fixed an issue within the deviceTRUST Console where a context custom condition would fail to load when the custom condition targeted data types of IP or Position.
Compatibility
This compatibility section builds on our general approach to compatibility which can be found on the compatibility page.
We’ve renamed LOCAL_WHOIS_VPN and REMOTE_WHOIS_VPN to LOCAL_WHOIS_ADAPTER_VPN and REMOTE_WHOIS_ADAPTER_VPN respectively to ensure clarity with the new proxy properties. deviceTRUST Policies will upgrade automatically, but if these properties are referenced within scripts, or Web Request tasks, they may need to be manually updated.
If upgrading from a release prior to 23.1.400, be sure to check out the deviceTRUST 23.1.300 compatibility notes.
The deviceTRUST Agents can read policies created by previous releases of the deviceTRUST Console. However, they cannot read policies created by a newer console. Therefore, you must ensure that the deviceTRUST Agent 23.1.400 is deployed before applying policy that has been written by the deviceTRUST Console 23.1.400 or later.