Role-based access control (RBAC) for Application Security

Admin Access Required

Managing which users can access what data is one element of a strong security program. Administrators often need to separate apps between teams so that users from a team can access apps approved for their team only. To enforce this type of application isolation, you can configure individual and user group access at the feature and app levels. By using groups and roles, you can scale your application security program without manually assigning individual users to individual apps, or giving too much access to too many users.

Application Security and Platform admins can customize and manage user roles and access at the feature-level with Role-based access control (RBAC) in the Command Platform . To get started with RBAC for Application Security , we offer managed user roles so that you can assign feature-level to your users and user groups.

Access levels

Users have diverse needs for the data and functionality of features. Though many users may need access to a feature, they may only need to view data or add comments. To help you refine user roles, each feature has at least one of the following access levels:

  • Administer. Full access to the feature, including add, edit, delete, and other privileges.
  • View and Change. Access to view and make changes (add, edit, delete) to the data for that feature.
  • View. Access to view, but not edit, data.

Application Security user roles

To better protect your data, create multiple user roles with specific permissions based on the different tasks users perform in their roles. We provide the following user roles that you can copy or update to fit your needs:

  • App Owner. Set up apps and configure settings within the app, but has lesser privileges to scan configurations and vulnerabilities.
  • Scan Manager. Create scan configs and run scans, but not view and change apps or vulnerabilities.
  • Remediator. Fix, manage, and replay attacks on vulnerabilities within apps they can access, but not manage apps or scans.

Feature-level access details

You can customize roles by setting additional permissions at the feature level for apps, scans, vulnerabilities, and administrative tasks. Expand each high-level feature to view specific features and their descriptions.

App-level access

Network administrators often need to segregate apps between teams so that users from a team can access apps approved for their team only. To enforce this type of application isolation, you can configure user access at the app level. Administrators can manage user access for all apps.

User group-level access

You can grant or restrict user groups access to individual or all apps. If you restrict access to an app group, every app current or future apps created within the group is automatically restricted. Users are only given access to the apps you select within an app group. When you select some and not all of the apps within a group, users will not have access to any additional apps added to the group in the future.

Manage role conflicts

RBAC functionality makes user management more flexible, but the freedom to assign multiple roles to users and leverage user groups may result in permissions conflicts. Platform Admins can resolve permission conflicts by reviewing the cause of the conflict and adjusting permissions as needed by editing the individual user’s permissions, a user role, or the groups a user is assigned to. For more information, view Resolve Permission Conflicts in the Command Platform documentation.

Do you have questions?

Check out our FAQ for Application Security RBAC.