Restrict Access to a Scan Role Using RBAC
📖 If you’re new to Probe Roles, start with Create a Scan Role.
You can now restrict access to probe roles based on user roles (RBAC). This gives you fine-grained control over who can view or use a particular probe role.
This is especially useful in collaborative environments where different teams (e.g., Security, QA, DevOps) need access to different sets of probes.
📘 Prerequisite
Make sure you’ve already created Custom Roles for your team members.
✅ Steps to Restrict Probe Role Access by User Role
Go to Scan Roles
Navigate to AI Red Teaming → Scan Roles.
Create or Edit a Scan Role
You can either create a new Probe Role or edit an existing one.
Set Scope Role
In the Probe Role configuration form, locate the dropdown labeled ”Scope Role”.
Select one or more user roles from the list.
Only users with the selected roles will be able to view or apply this Probe Role during probing.
Save
Click Save to update the Probe Role with the new RBAC restrictions.
🔒 What Happens After Setting a Scope Role?
Users without the selected roles will not see the Probe Role in their list.
They also won’t be able to select the Probe Role when triggering a probe.
Admins and Super Admins retain visibility over all Probe Roles by default.
🧪 Example Use Case
QA Team: Create a probe role named “Regression Suite” and assign it a scope role of QA.
Security Team: Set up a probe role named “Critical Security Checks” and assign it to the Security scope role.
📎 Related Documentation
Last updated