Access policies
The Access policies page is where you decide who gets on the network and with which settings. You group rules into policies by who connects (employees, IoT devices, guests), and you write the TACACS+ rules that control logins to switches and routers.
What this page shows
Section titled “What this page shows”Access › Access policies has two tabs, each with a count:
- Network access: the RADIUS access policies, in the order Airgate checks them. The first policy that matches handles the sign-in.
- Switch and router logins: who may log in to switches, routers and firewalls over TACACS+, and with which privilege level.
Changes on both tabs are kept as a draft until you select Save changes. Nothing reaches live sign-ins before that.
Network access tab
Section titled “Network access tab”The table lists every policy, numbered from the top. Policies made on another page (for example guest Wi-Fi passes) or over the API are listed in their place but cannot be opened here; their Applies to cell reads Set up elsewhere (for example guest Wi-Fi passes). Turned-off policies show · off after the name.
The last row, Nothing matched, is fixed: when no policy above takes a sign-in, it is denied.
Select a policy name to open it. The policy view has four cards: Policy, Applies when, Sign-in and the rule list. Select All policies to return to the list.
Switch and router logins tab
Section titled “Switch and router logins tab”A banner reminds you to point your network devices at Airgate as their TACACS+ server. Below it are the login rules and the Accounts are checked in card, which lists Local users (always on) and a checkbox for each of your directories.
Fields and columns
Section titled “Fields and columns”Policy list columns
Section titled “Policy list columns”| Column | Meaning |
|---|---|
| Order | Position in the check order. Airgate tries policies from the top. |
| Policy | The policy name. Select it to open the policy. |
| Applies to | The connection type, the SSIDs (on Corp-WiFi), the device group (through Branch Switches) and the number of extra conditions (+1 more). |
| Sign-in | The allowed sign-in methods and the directories, in order. For MAC authentication policies: Any device or Known devices only. |
| Rules | Number of rules in the policy. |
Policy fields
Section titled “Policy fields”| Field | Meaning |
|---|---|
| Name | Required, for example Employees. Unique; cannot contain / or match the name of another policy-engine service. |
| Status | On or Off. A policy that is off is skipped. |
| Connection | 802.1X (laptops and phones signing in with a certificate or an account), MAC authentication (printers, cameras and other devices that cannot sign in) or Any sign-in (802.1X, PAP, CHAP, MS-CHAP and MAC authentication). |
| Wi-Fi networks (SSID) | The SSIDs this policy handles, separated by commas, for example Corp-WiFi. Leave empty for any network, wired included. |
| Switches and APs | Limits the policy to one device group. All switches and APs applies everywhere. |
| Also | Shown only when the policy carries extra match conditions created outside this page. They are kept but cannot be edited here. |
| Which devices | MAC authentication only. Any device: the rules decide, also for devices not known yet. Known devices only: devices not in Devices are refused. |
| Allowed methods | 802.1X and Any sign-in only. Methods that are not ticked are refused. 802.1X offers EAP-TLS (certificate), PEAP and EAP-TTLS (username and password). Any sign-in adds PAP, CHAP and MS-CHAP. |
| Check accounts in | 802.1X and Any sign-in only. The account stores, checked in the order shown: Local users, Guest accounts and the directories from Directories. At least one is required. Directories also answer group lookups for EAP-TLS sign-ins. |
Rule list columns
Section titled “Rule list columns”| Column | Meaning |
|---|---|
| Order | Position in the rule list. The first rule that matches wins. |
| Rule | The rule name. Select it to edit the rule. |
| When | The conditions in words, joined with and. A rule without conditions reads anyone this policy handles. |
| Then | Deny, Allow, or the settings the rule sends (VLAN 110, Role employee, SGT 10, ACL EMPLOYEE-ACL, re-check 28800s), or the name of the enforcement profile it sends. On the logins tab: the privilege level. |
| Default | Fixed last row. What happens when no rule matches: Deny or Allow (on the logins tab, Deny or Allow read-only). |
Rule editor
Section titled “Rule editor”| Field | Meaning |
|---|---|
| Rule name | Required, for example Staff laptops. Unique in the list; cannot contain /. Not shown when the rule sends an enforcement profile: the rule then takes the profile’s name. |
| When | The conditions. All must be true. See Rule conditions. |
| Access (network) / Login (logins tab) | Allow or Deny. |
| Send | Network rules that allow only. These settings shows the fields below; An enforcement profile shows the Enforcement profile picker. |
| Enforcement profile | A RADIUS accept profile from Enforcement profiles. Built-in profiles are marked (built-in). The profile’s attributes are listed under the picker. |
| VLAN | A VLAN number or name, for example 110. Sent as Tunnel-Type = VLAN (13), Tunnel-Medium-Type = IEEE-802 (6) and Tunnel-Private-Group-Id. Leave empty to keep the port’s VLAN. |
| Role | Aruba user role, sent as Aruba-User-Role, for example employee. |
| Security group tag | Cisco TrustSec SGT, a number from 1 to 65519. Sent as Cisco-AVPair = cts:security-group-tag=<hex>-00. |
| ACL or firewall policy | Sent as Filter-Id, for example EMPLOYEE-ACL. |
| Re-check after (seconds) | Sent as Session-Timeout, for example 28800. |
| Privilege level | Logins tab only. Read-only (level 1), Operator (level 7) or Full admin (level 15). Sent as the TACACS+ priv-lvl and, for Aruba devices, as Aruba-Admin-Role (read-only, network-operations or root). |
Rule conditions
Section titled “Rule conditions”Each condition is one line in the When section. On the Switch and router logins tab only User is in group and Network device group is are offered.
| Condition | Values | Matches |
|---|---|---|
| User is in group | A directory and a group name, for example Staff |
Authorization:<directory>:Groups equals the group. |
| Wi-Fi network (SSID) is | An SSID, for example Corp-WiFi |
Connection:SSID. |
| Device is in MAC list | A list from MAC lists | The client MAC belongs to the list. |
| Device type is | A category, for example Printer |
Endpoint:Category, ignoring case. |
| Device is | Known (added to Devices) or Not known yet | Endpoint:Status. |
| Intune managed | Yes (managed by Intune) or No | Endpoint:Intune Managed. |
| Intune compliance | Compliant, Not compliant or In grace period | Endpoint:Intune Compliance State. |
| SentinelOne agent | Installed (found in SentinelOne) or Not found | Endpoint:SentinelOne System Found. |
| SentinelOne threats | None (clean) or Infected | Endpoint:SentinelOne Infected. |
| CrowdStrike sensor | Installed (found in CrowdStrike) or Not found | Endpoint:CrowdStrike System Found. |
| CrowdStrike containment | Not contained (normal) or Network contained | Endpoint:CrowdStrike Status. |
| Managed by an MDM | Yes (Intune or Jamf) or No | Endpoint:MDM Enabled, written by the Intune and Jamf Pro syncs. |
| MDM compliance | Compliant or Not compliant | Endpoint:MDM Compliant. |
| BYOD device | Yes (onboarded via BYOD) or No | Endpoint:BYOD. |
| Guest portal login | Still valid or None or expired | Whether Endpoint:Access_Valid_Till is still in the future. |
| Network device group is | A device group | Device:Device-Group. |
| Signed in with | PEAP (username and password), EAP-TLS (certificate), TTLS, Password (PAP), MS-CHAP or MAC address | Authentication:OuterMethod. |
Conditions created outside this page (over the API, for example) are shown as read-only chips that you can only remove.
Actions
Section titled “Actions”| Action | What it does |
|---|---|
| Add a policy | Opens a template picker. Employees: 802.1X with EAP-TLS and your first enabled directory, one rule Staff. IoT and printers: MAC authentication for any device, one rule Known devices matching Device is Known. Guests: Any sign-in on the SSID Guest WiFi with PEAP and PAP against Guest accounts, one rule Guests. Blank: nothing filled in. Every template denies by default. A new policy is placed after the SSID-specific policies and before the catch-all ones. |
| Move up / Move down | Changes the check order of a policy, a directory in Check accounts in, or a rule. |
| Delete (trash icon) | Removes a policy or a rule from the draft. Policies set up elsewhere cannot be deleted here. |
| Add a directory… | Adds an account store to Check accounts in. Remove (x) takes one out. |
| Add a rule | Opens the rule editor. Done puts the rule in the draft; Cancel discards it. |
| Add condition | Adds a condition line in the rule editor. Remove condition (x) deletes one. |
| Default | Switches the fallback of a rule list between Deny and Allow (or Allow read-only). |
| Accounts are checked in | On the logins tab, ticks the directories that TACACS+ logins are checked against, after Local users. |
| Save changes | Checks every policy for errors, then writes the policies, their rules and the check order. New sign-ins use them right away. If a policy has an error, Airgate opens it and shows what to fix. |
| Discard changes | Shown when there are unsaved changes. Reloads the saved policies. |
Permissions
Section titled “Permissions”- View:
policy:read: Tenant Administrator, Network Administrator, Help Desk, Read-only Administrator and Platform Administrator. - Change:
policy:write: Tenant Administrator, Network Administrator and Platform Administrator. Without it the page is read-only and rules cannot be opened.