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:
PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/activation?status=<status>GET https://<IA_IP_address>:<port_number>/config/v1/rbac/activationGET https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappingsDELETE https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappingsBulk upsert VLAN/Q-in-Q mappings: Request
PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/_bulkVLAN/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
DELETE https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/<groupAlias>Create VLAN/Q-in-Q mapping for a group: Request
POST https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappingsUpdate VLAN/Q-in-Q mapping for a group: Request
PUT https://<IA_IP_address>:<port_number>/config/v1/rbac/vlan/mappings/<group_alias>