How Airgate compares
NAC products tend to come in two shapes. Appliance-based NACs give full control and on-prem integration, at the cost of hardware, clustering and specialist time. Cloud-only NACs are quick to start but often stop at the edge of the cloud. Airgate is built to be run as a service and still reach into your sites.
| Airgate | Appliance-based NAC e.g. Cisco ISE, HPE Aruba ClearPass, Forescout | Cloud-only NAC e.g. Portnox Cloud, Juniper Mist Access Assurance | |
|---|---|---|---|
| Where it runs | Airowire cloud with site connectors, or the same software on your VMware hosts | Physical or virtual appliances you size, cluster, patch and back up | The vendor’s cloud only |
| First working sign-in | Add a switch, a directory and a rule in the console | Hardware, HA design, certificates and services first | Usually quick |
| Branch sites | Site connector: RadSec to the cloud, CoA relayed through NAT, outbound only | RADIUS over the WAN or VPN to a central cluster, or appliances per region | RadSec from devices that support it; CoA through NAT varies |
| On-prem Active Directory with PEAP | Domain-joined appliance or AD relay through the site connector | Domain-joined appliances | Often cloud identity only, or an extra on-prem component |
| Device compliance | Intune, Jamf, SentinelOne and CrowdStrike built in, no agent on the device | Often an add-on, a posture agent or a separate integration product | Varies |
| Private Wi-Fi addresses | Matched by the Intune device ID in the certificate | MAC matching; randomised addresses need workarounds | Varies |
| Wi-Fi certificates | Built-in CA with SCEP validated by Intune, OCSP and CRL | A separate PKI or an onboarding add-on | Often included |
| Guests and BYOD | Included: portals, Teams sponsor delivery, QR passes, AirEnroll | Often separately licensed | Varies |
| Why a sign-in failed | Plain-language reason and fix, plus the full trace | Detailed logs written for RADIUS specialists | Varies |
| Many organisations | Isolated tenants on one platform | Usually one deployment per organisation | Usually supported |
| Internet link down at a site | Known MAB devices keep working from the connector’s cache; full local 802.1X is planned | Unaffected when appliances are on site | Depends on the vendor |
A comparison of approaches, not a feature-by-feature review of named products: what each product does depends on its edition and licence. Product names are trademarks of their owners.
Coming from ClearPass or ISE?
Services, enforcement policies and enforcement profiles will look familiar. Endpoint attributes from Intune and SentinelOne use the same names as the ClearPass extensions, so conditions written for ClearPass carry over.
