Role Based Access Control Policy

Using the Role Based Access Control Policy (RBAC) feature, organizations can deploy a single SSID for multiple roles, and provide different access privileges based on the user's role in the organization.

For example, a school could create a single secure WLAN for both students and staff members. Then, when either type of user connects to the network, they will be granted the proper access privileges based on their role at the school.

Users created on an AAA server can be mapped to roles on ZoneDirector using group attributes. When a client completes authentication successfully, ZoneDirector gets the group attributes assigned to this user from the AAA server and uses the group attributes to determine the user's role, and applies the access control restrictions defined in that role to the client's access privileges.

Note: When RBAC is enabled on a WLAN, Client Fingerprinting must be enabled, and Dynamic VLAN should also be enabled if VLANs will be assigned based on user roles.

RBAC Policy Options

The following control policies can be applied to a role:

  • Device type: Limit access based on operating system/device type.
  • VLAN: Assign a VLAN ID to this role.
  • Rate Limiting: Limit per-station uplink and downlink speeds.
  • L3/L4/IP address ACL: Apply a Layer 3/Layer 4/IP address ACL to this role.
  • Application Recognition & Control: Apply an application policy to this role.
  • Time Range: Limit the time range during which this role will be allowed to access the WLAN.

Once you have created access control policies for your user roles, you will need to apply them to any WLANs for which you want to enforce these policies. To do this, edit the WLAN, expand the Advanced Options, and enable the check box next to Enable Role Based Access Control Policy in the Access Control section.

Note: When role-based application recognition and control (ARC) policies and WLAN-based ARC policies both exist, role-based ARC takes priority. If an application policy is available based on RADIUS attributes, then RADIUS group attributes take priority. In other words, the priority is: RADIUS attribute > Role > WLAN.