# General Structure ## Rule Collection {% hint style="info" %} We recommend providing descriptive names for your rules, as this will allow them to be clearly identifiable in the Insight [Log](https://docs.radiusaas.com/admin-portal/insights/log)s. {% endhint %} Every Rule can have a **Name, Description** and is specified for a specific authentication type.\ Currently you can define a rule for **Wi-Fi**, **LAN** and **VPN**. Furthermore, you can **Enable** or **Disable** each rule.

## SSID, Access Point (AP) and Switch MAC Groups {% hint style="info" %} For **Wi-Fi** and **Wired/LAN** networks only! {% endhint %} To restrict access to specific networking infrastructure elements, such as APs, SSIDs or network switches, you have two options: 1. Add the respective **MAC** **address(es)** or **SSID(s)** directly in the Rule collection. 2. Create **Groups** that allow you to add multiple targets and manage them more efficiently. This way, items can be added or removed without the need to touch the Rule itself, as the Rule will only reference the Group. {% hint style="info" %} Should you have a large number of MAC addresses that you wish to add, you can import them from the following file types: .xlsx, .xls or .csv file. The maximum number of MAC addresses that can be imported depends on a number of factors, including the number of rules you have configured. {% endhint %}

## Trusted NAS Identifiers and IP Addresses {% hint style="info" %} For **VPN** networks only! {% endhint %} When using RADIUSaaS for authenticating a VPN, the authentication requests can be limited to certain Network Access Servers (NAS) by allow-listing their identifier or IP address. 1. Add the respective **NAS Identifier(s)** or **NAS IP Address(es)** directly in the Rule collection 2. Create Groups that allow you to add multiple targets and manage them more efficiently. This way, items can be added or removed without the need to touch the Rule itself, as the Rule will only reference the Group.

## Custom Certificate Extensions If you have your own PKI and want to assign VLAN IDs based on the value of a custom certificate extension (OID), you can make that mapping information available to RADIUSaaS under **Custom Certificate Extensions.** Once you have specified such a custom extension, you can reference it in any rule and assign VLANs based on the raw or filtered extension value. {% hint style="info" %} Currently it is not supported to add custom certificate extensions to SCEP profiles in many MDM systems, including Microsoft Intune and Jamf Pro. We therefore recommend using the Certificate Subject Name instead to [dynamically assign VLANs](https://docs.radiusaas.com/admin-portal/settings/rules/..#vlan-assignment). {% endhint %} ![Showing VLAN assignment by Certificate Extension](https://1222554226-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSWU1DQ4UGkqER7uGNUOm%2Fuploads%2FHxA3CIyrKTc2lerDxjtG%2F2024-05-28_10h41_47.png?alt=media\&token=031d2b4e-d891-4d4c-a2ea-3de3f3852792)

## VLAN Attributes This section allows the configuration of vendor-specific VLAN attributes that RADIUSaaS will return if a relevant rule (static or dynamic VLAN tagging enabled) is matched. In case the pre-configured values lead to issues with your networking equipment, they can be removed from here, too.

## RADIUS Attributes In this section, vendor-specific attributes (VSAs) can be managed. The attributes configured here can then be used in your rules under [**Additional RADIUS Return Attributes**](https://docs.radiusaas.com/admin-portal/settings/rules/..#additional-radius-return-attributes).