Planned integrations
Integrations on the Airgate roadmap, such as Microsoft Defender for Endpoint, more MDM compliance sources, Okta device context, ServiceNow CMDB import, SIEM apps and controller auto-configuration.
These integrations are on the Airgate roadmap. None of them is available yet, and none has a release date. Where a product can already be reached with an HTTP action, the current page is linked. For what works today, see the integrations overview.
Device and endpoint context
Section titled “Device and endpoint context”Microsoft Defender for Endpoint
Section titled “Microsoft Defender for Endpoint”Planned. Read devices from Microsoft Defender for Endpoint and write their onboarding state, risk level and exposure level to the matching device records, so access rules can admit only onboarded devices and quarantine high-risk ones, as SentinelOne and CrowdStrike do today.
Workspace ONE, Ivanti, MaaS360, Afaria and Kandji device compliance
Section titled “Workspace ONE, Ivanti, MaaS360, Afaria and Kandji device compliance”Planned. Poll VMware Workspace ONE UEM, Ivanti (MobileIron), IBM
MaaS360, SAP Afaria and Kandji for their devices and write the managed and compliance
state to the generic MDM attributes (MDM Enabled, MDM Compliant), so
the Managed by an MDM and MDM compliance conditions work for them
as they do for Intune and Jamf Pro. Today Workspace ONE, Ivanti, MaaS360 and
Afaria are HTTP action targets only: see
VMware Workspace ONE UEM,
Ivanti EPMM,
IBM MaaS360 and
SAP Afaria.
Jamf Pro page in the console
Section titled “Jamf Pro page in the console”Planned. A page under Integrations for Jamf Pro, like the Intune, SentinelOne and CrowdStrike pages, with connection, sync status and the list of synced devices. Jamf Pro sync works today through a context server on Settings › Webhooks: see Jamf Pro.
Google Endpoint Management
Section titled “Google Endpoint Management”Planned. Read devices managed by Google Endpoint Management (Google Workspace) and write their management and compliance state to the matching device records.
Okta device context
Section titled “Okta device context”Planned. Use Okta’s device information (registered and managed devices, device assurance results) as context in access rules, in addition to Okta users and groups, which work today: see Okta.
ServiceNow CMDB device import
Section titled “ServiceNow CMDB device import”Planned. Import devices from the ServiceNow CMDB (MAC address, owner, category, location) into Airgate’s device records, so access rules and device profiling can use the CMDB as a source of truth. Opening incidents works today: see ServiceNow.
Infoblox and Aruba IntroSpect context
Section titled “Infoblox and Aruba IntroSpect context”Planned. Import IP and host data from Infoblox, and risk scores or alerts from Aruba IntroSpect, into the device records. Today both are HTTP action targets: see Infoblox and Aruba IntroSpect.
Identity sharing with firewalls
Section titled “Identity sharing with firewalls”Session-based login and logout for Fortinet, Check Point and Juniper SRX
Section titled “Session-based login and logout for Fortinet, Check Point and Juniper SRX”Planned. Send login and logout to FortiAuthenticator, Check Point Identity Awareness and Juniper SRX on network session start and stop (RADIUS accounting), as Airgate does today for Palo Alto User-ID. Today these calls run as HTTP actions from access rules: see Fortinet, Check Point and Juniper SRX.
SIEM apps
Section titled “SIEM apps”Microsoft Sentinel and Splunk apps
Section titled “Microsoft Sentinel and Splunk apps”Planned. A Microsoft Sentinel solution and a Splunk app for Airgate data: parsers, workbooks or dashboards and analytics rules for sign-ins, sessions, guest activity and administrator changes. Event export to both works today: see SIEM and syslog and Splunk.
Network infrastructure
Section titled “Network infrastructure”Cisco and Aruba controller auto-configuration
Section titled “Cisco and Aruba controller auto-configuration”Planned. Configure Cisco and Aruba wireless controllers and switches for Airgate from the console: RADIUS servers, CoA, captive portal redirect and the needed ACLs, pushed through the device’s management API instead of entered by hand. Today these devices are configured manually: see Connect switches, APs and controllers.