--- title: "VLAN/Q-in-Q based access control" slug: "vlan-q-in-q-based-access-control" tags: ["Reference", "NDRC 4.x", "Customer", "Network Security", "NDR 4.x"] updated: 2026-08-10T07:16:04Z published: 2026-09-09T18:07:57Z canonical: "docs.trellix.com/vlan-q-in-q-based-access-control" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # VLAN/Q-in-Q based access control You can define roles with specific access based on Active Directory groups or the inner and outer VLAN/Q-in-Q tags in PX metadata. VLAN/Q-in-Q based UI and API access control gives an NDR Console admin the ability to configure an analyst's access (search and visibility) to network metadata stored in Elasticsearch based on the origination of the traffic. This is determined based on the VLAN tags included in the network metadata provided by the PX appliance. The admin must have the ability to group the users and analysts into different organizational groups and should be able to assign groups to either a single VLAN, multiple VLANs, or a range of VLANs for RBAC purposes. Once an analyst is assigned to a group that is assigned to particular VLAN range, the analyst access must be restricted to traffic belonging to that VLAN. The following RBAC endpoints are available: - [Enable VBAC: Request](/network-and-platform/docs/enable-vbac-request) `PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/activation?status=<status>` - [VBAC state: Request](/network-and-platform/docs/vbac-state-request) `GET https://<IA_IP_address>:<port_number>/config/v1/rbac/activation` - [VLAN/Q-in-Q mappings: Request](/network-and-platform/docs/vlan-q-in-q-mappings-request) `GET https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings` - [Delete VLAN mappings: Request](/network-and-platform/docs/delete-vlan-mappings-request) `DELETE https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings` - [Bulk upsert VLAN/Q-in-Q mappings: Request](/network-and-platform/docs/bulk-upsert-vlan-q-in-q-mappings-request) `PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/_bulk` - [VLAN/Q-in-Q mapping for a group: Request](/network-and-platform/docs/vlan-q-in-q-mapping-for-a-group-request) `GET https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/<groupAlias>` - [Delete VLAN/Q-in-Q mapping for a group: Request](/network-and-platform/docs/delete-vlan-q-in-q-mapping-for-a-group-request) `DELETE https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/<groupAlias>` - [Create VLAN/Q-in-Q mapping for a group: Request](/network-and-platform/docs/create-vlan-q-in-q-mapping-for-a-group-request) `POST https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings` - [Update VLAN/Q-in-Q mapping for a group: Request](/network-and-platform/docs/update-vlan-q-in-q-mapping-for-a-group-request) `PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/<group_alias>`