Access policies
An access policy decides what happens to a sign-in: which methods are allowed, where accounts are checked, and what access the user or device gets. This page explains the parts of a policy, the order in which Airgate evaluates them, and the policy engine underneath the Access › Access policies page.
The building blocks
Section titled “The building blocks”| Term | What it is |
|---|---|
| Access policy (engine name: service) | Handles one kind of sign-in, for example employees on Corp-WiFi or IoT devices by MAC address. It has match conditions (Applies when), allowed authentication methods, the directories to check, and a rule list. |
| Rule | One line of the rule list: conditions (When) and an action (Then). |
| Condition | A test on one attribute, such as Connection:SSID EQUALS Corp-WiFi or Authorization:Contoso AD:Groups EQUALS Staff. |
| Enforcement profile | What the network device is told when a rule matches: accept, reject or drop, plus RADIUS attributes (VLAN, role, ACL, vendor attributes). |
| Enforcement policy | The engine object that holds a rule list, its evaluation algorithm and its default profile. The Access policies page creates one per access policy. |
Tags (engine name: roles, Tips:Role) |
Labels attached to a sign-in before the rules run, such as [User Authenticated]. Shown as Tags in the Sign-in log and in Test access. |
Order of evaluation
Section titled “Order of evaluation” Access-Request │ ├─ 1. Policy selection policies in order; the first enabled one whose │ conditions all match handles the request │ none → reject "No service matched" ├─ 2. Method check outer (and inner) method must be allowed │ otherwise → reject "Authentication method not allowed" ├─ 3. Authentication account / certificate / MAC verified ├─ 4. Context directory groups and attributes, endpoint, device │ compliance, guest account, certificate, NAD, time ├─ 5. Tags identity roles + role mapping → Tips:Role ├─ 6. Rules first matching rule wins → its profiles │ no match → the default profile └─ 7. Merge and reply profiles merged into one Access-Accept, Access-Reject, or no answer (drop)1. Policy selection
Section titled “1. Policy selection”Airgate checks the tenant’s policies for the request’s protocol (RADIUS, TACACS+ or application logins such as the guest operator login) in order, from the top. The first enabled policy whose conditions all match handles the request. Later policies are never looked at. If no policy matches, the request is rejected with error code 9001 (No service matched).
On Access › Access policies, the match conditions come from Applies when:
| Setting | Condition written |
|---|---|
| Every policy | Radius:IETF:User-Name EXISTS |
| Connection: 802.1X | Connection:Request-Type EQUALS 802.1X |
| Connection: MAC authentication | Connection:Request-Type EQUALS MAC-AUTH |
| Wi-Fi networks (SSID): one name | Connection:SSID EQUALS <name> |
| Wi-Fi networks (SSID): several names | Connection:SSID BELONGS_TO <name>, <name> |
| Switches and APs: a device group | Device:Device-Group EQUALS <group> |
A new policy is inserted after the enabled policies that are limited to an SSID, and ahead of catch-all policies. Use Move up and Move down to change the order, then Save changes.
2. Method check
Section titled “2. Method check”The policy lists the authentication methods it accepts. A sign-in with any other method, or with an inner method the outer method does not allow, is rejected with error code 9002 (Authentication method not allowed). See Authentication methods.
For MAC authentication, Which devices picks the method:
| Option | Engine method | Behaviour |
|---|---|---|
| Any device | [Allow All MAC AUTH] |
Every MAC address is accepted into the rules, known or not. The rules decide. |
| Known devices only | [MAC AUTH] |
The MAC address must be under Devices. Unknown devices are rejected as User not found before the rules run. |
3 and 4. Authentication and context
Section titled “3 and 4. Authentication and context”Airgate verifies the credential (see Authentication methods) against the directories under Check accounts in, in order. It then collects everything the rules may test and stores it as attributes in namespaces, for example the user’s groups from each directory, the endpoint’s status and compliance facts, the client certificate’s fields and the NAD’s device groups. The Computed attributes tab of a Sign-in log record shows exactly what was collected for that request.
5. Tags
Section titled “5. Tags”Before the rules run, Airgate attaches tags (Tips:Role) to the sign-in:
[User Authenticated]for a successful user authentication,[Machine Authenticated]for a machine authentication (see machine authentication);- the role of a local user or guest account, and
Authorization:<directory>:Role_Name; - values of directory attributes marked Enable as role on the directory;
- for MAC authentication against Devices, the device status (
Known,UnknownorDisabled); - roles from role mapping policies, which you can configure through the API.
Rules can test tags with the Tips:Role attribute.
6. Rules
Section titled “6. Rules”The rule list is evaluated with one of two algorithms. Policies made on the Access policies page always use first-applicable.
| Algorithm | Result |
|---|---|
| First-applicable | The first rule whose conditions match wins; its profiles are applied. |
| Evaluate-all (API) | Every matching rule contributes its profiles, in rule order. |
Within a rule, conditions are combined with AND (all must be true; the Access policies page always uses AND) or OR (any may be true). If no rule matches, the policy’s default profile applies. On the Access policies page that is the Default row: Deny ([Deny Access Profile]) or Allow ([Allow Access Profile]). If a policy has no default and no rule matches, the request is rejected.
7. Merge and reply
Section titled “7. Merge and reply”The profiles of the decision are merged into one answer:
- Drop beats reject beats accept. If any profile’s action is Drop, Airgate sends no answer at all. Otherwise, if any profile’s action is Reject, Airgate sends an Access-Reject.
- An Access-Reject carries only
Reply-Message; all other attributes are removed. - Single-valued attributes: first wins. If two profiles set the same single-valued attribute (such as
Tunnel-Private-Group-Id), the first profile’s value is sent and the later one is ignored (the trace says so). - Multi-valued attributes accumulate, for example
Cisco-AVPair. - A profile limited to Device groups applies only when the request’s NAD is in one of those groups. If none of the decision’s profiles applies, the default profile is used.
- Attribute values may contain references such as
%{Authentication:Username}. Airgate expands them from the request’s attributes. A value whose reference cannot be resolved is left out.
A rejected decision is recorded with error code 206 (Access denied by policy).
Conditions
Section titled “Conditions”A condition is Namespace:Attribute OPERATOR value. The value may be a literal or a %{Namespace:Attribute} reference to another attribute of the same request.
Namespaces
Section titled “Namespaces”| Namespace | What it holds |
|---|---|
Radius:IETF, Radius:<Vendor> |
Attributes of the RADIUS request, for example Radius:IETF:NAS-Port-Type or Radius:Aruba:Aruba-Essid-Name. |
Connection |
Facts about the connection: SSID, Request-Type, Protocol, Client-Mac-Address (in several formats), Client-Mac-Randomized, NAD-IP-Address, Client-IP-Address. |
Authentication |
The sign-in: Username, Full-Username, OuterMethod, InnerMethod, Source, Status, MacAuth, Machine. |
Authorization:<directory> |
Groups and attributes a directory returned, for example Authorization:Contoso AD:Groups. Authorization:Sources lists the directories that answered. |
Endpoint |
The device record under Devices, including the facts synced from Intune, CrowdStrike, SentinelOne and Jamf, and the BYOD markers. |
Device |
The network device: Device-Name, Device-Type, Device-Vendor, Device-IP-Address, Device-Group, Location, OS-Version, plus custom attributes. |
Certificate |
The EAP-TLS client certificate: subject and issuer fields, SANs, validity and Intune-Device-Id. |
Onboard |
For certificates issued by the tenant CA: Owner and MAC Address. |
GuestUser |
The guest account: visitor name, sponsor, status, start and expiry time. |
LocalUser |
The local user: name, e-mail, role, enabled, expiry. |
Date |
Day-of-Week, Time-of-Day, Date-of-Year, Day-of-Month, Month, Year, Date-Time, in the tenant time zone. |
Tips |
Role (the tags) and Posture. |
TACACS |
TACACS+ requests: Service, Privilege-Level, Command, Command-Args and others. |
Host, Application |
Portal and web-login requests. |
The complete list with types is in the policy attributes reference.
Operators
Section titled “Operators”| Operator | True when |
|---|---|
EQUALS / NOT_EQUALS |
A value equals the configured value (typed: enumerations by name or number, MAC and IP addresses, numbers and times by value). |
EQUALS_IGNORE_CASE / NOT_EQUALS_IGNORE_CASE |
The same, ignoring case. |
CONTAINS, BEGINS_WITH, ENDS_WITH and their NOT_ forms |
A value contains, starts or ends with the configured text. |
EXISTS / NOT_EXISTS |
The attribute is present and not empty / absent or empty. |
BELONGS_TO / NOT_BELONGS_TO |
A value is one of a list (comma-separated). |
MATCHES_ANY, MATCHES_ALL, MATCHES_EXACT and their NOT_ forms |
Set comparisons between the attribute’s values and a list. |
BELONGS_TO_GROUP / NOT_BELONGS_TO_GROUP |
The NAD is in a device group, or the client MAC or IP address is in a MAC list (static host list). |
MATCHES_REGEX / NOT_MATCHES_REGEX |
A value matches a regular expression (RE2, not anchored). |
LESS_THAN, LESS_THAN_OR_EQUALS, GREATER_THAN, GREATER_THAN_OR_EQUALS |
Typed comparison of numbers, times, IP addresses or versions. |
IN_RANGE / NOT_IN_RANGE |
The value lies between low,high (times of day may wrap midnight). |
IN_SUBNET / NOT_IN_SUBNET |
An IP address lies in one of the listed prefixes. |
Enforcement profiles
Section titled “Enforcement profiles”Profiles are listed on Access › Enforcement profiles: Built-in, Custom and From access rules (the profiles the Access policies page creates for each rule, named Rule: <policy> / <rule>).
| Profile type | Effect |
|---|---|
RADIUS |
Accept, Reject or Drop, plus RADIUS reply attributes. |
RADIUS_COA |
A CoA or Disconnect sent after the reply. See Change of Authorization. |
POST_AUTH |
Updates after the decision, for example set the endpoint status ([Update Endpoint Known]). |
TACACS |
Privilege level, services and command authorization for switch and router logins. |
SESSION |
Session restrictions: concurrent sessions, time, data or expiry limits. |
HTTP |
An outbound HTTP action, run asynchronously. |
APPLICATION |
Accept or deny for portal and application logins. |
ARUBA_DUR |
An Aruba downloadable user role. |
Built-in RADIUS profiles include [Allow Access Profile], [Deny Access Profile] and [Drop Access Profile], examples such as Employee VLAN, Guest VLAN, Quarantine VLAN and Registration VLAN, and captive-portal redirects ([Aruba Captive Portal Redirect], [Cisco CWA Redirect], [Meraki Splash]). Built-in profiles cannot be changed. See RADIUS attributes for the attributes you can send.
Monitor mode
Section titled “Monitor mode”A policy can run in monitor mode (set through the API). Airgate then computes and logs the full decision, but always answers with a plain Access-Accept and runs none of its side effects. The trace shows the result that would have applied. Use it to try a policy on live traffic before enforcing it.
Switch and router logins
Section titled “Switch and router logins”The Switch and router logins tab of Access › Access policies holds one TACACS+ rule list for administrator logins on network devices. Each rule allows a Privilege level (Read-only (level 1), Operator (level 7) or Full admin (level 15)) or denies. Accounts are checked in Local users and the directories you tick. The default is Deny or Allow read-only.