What are the best practices for user roles and permissions?
This article describes recommended role definitions and configuration tips for Role-Based Access Control (RBAC). RBAC defines what each user can see, configure, and act on. Correct RBAC setup prevents data from being shared between business units, supports accountability, and is often a compliance requirement.
Recommended role definitions
| Role: | Typical users: | Permissions: |
|---|---|---|
| Platform admin | Security lead, security engineer | Full access. Configures scans, manages users, and accesses all assets and reports. Keep this role to two or three people maximum. |
| Security analyst | SOC or vulnerability management team | Views all results, creates tickets, and runs ad-hoc scans. Cannot modify platform configuration or user accounts. |
| Business unit remediation owner | IT operations leads, team managers | Views results scoped to their own business unit tag only. Acknowledges findings and updates remediation status. Cannot see other business units' data. |
| Read only/auditor | Compliance, CISO | Views dashboards and reports for their scope. Cannot trigger scans or modify any records. |
RBAC configuration tips
- Tie every RBAC scope to a tag, not an IP range. Tags update automatically as assets are added, while hardcoded IP ranges can break silently.
- Create a shared "admin" group rather than granting admin rights to individual accounts. When staff leaves, you only need to update one group membership.
- Audit your user accounts regularly, for example every three months. Employees who have left or changed roles are the most common source of unnecessary access.
- Document your agreed RBAC model and get sign-off from your security lead before implementation.