Airgateby Airowire

Security

A NAC sits in the path of every connection to your network, so it has to be the most careful system on it. This is how Airgate is built; the hardening guide covers what you configure.

Encryption in transit

RadSec (RADIUS over TLS) from sites, TLS for the console, portals, SCEP and the API, and mutually authenticated connections for site connectors.

Blast-RADIUS hardening

Message-Authenticator is required on RADIUS requests, which closes the RADIUS/UDP forgery attack (CVE-2024-3596).

Secrets sealed at rest

Shared secrets, directory passwords, API tokens and private keys are encrypted in the database and are not shown again after they are saved.

Administrator access

Roles per tenant, console sign-in through your identity provider (with its MFA), and API keys with their own role.

Audit trail

Every administrative change is recorded with who made it, what changed, when and from where, and can be exported to a SIEM.

Outbound calls

Calls to directories, device-management services and webhook targets go through an egress policy that always refuses cloud metadata endpoints and, by default, loopback and link-local addresses.

Tenant isolation

Each organisation’s policy, identities, certificates and logs are separate; a network device belongs to exactly one tenant.

Certificate lifecycle

A certificate authority per tenant, OCSP and CRL, and immediate disconnection of a device whose certificate is revoked.