Roles and permissions for BMC Helix Portal
Consult the following table to understand the available access permissions for different functions and roles, and the capabilities assigned to each role.
User flows | Minimum permissions required | Allowed actions |
---|---|---|
To integrate with BMC Helix Intelligent Automation for vulnerability remediation Non-admin users need the specified minimum permissions to create and execute vulnerability remediation operations. | Automation Console
|
|
Core
| The user can perform all actions on credentials | |
Intelligent Automation
|
| |
Identity Management Service
|
| |
Vulnerability Manager These permissions are granted to the Vulnerability Manager, an out-of-the-box role. | Automation Console
| The Vulnerability Manager can perform all actions on vulnerabilities. |
aiops
| ||
To perform import operation of scan files If a user wants to import a scan file, then this role will require the minimum permissions as specified. |
|
|
Non-admin vulnerability view only A non-admin user role who can only view vulnerabilities will require the minimum permissions as specified. |
|
|
To close vulnerabilities If a user wants a role that can only close vulnerabilities will require the minimum permissions as specified. |
|
|
To manage exceptions If a user wants a role to manage vulnerability exceptions will require the minimum permissions as specified. |
|
|
Non-admin exception view only A non-admin user who can only view vulnerability exceptions will require the minimum permissions as specified. |
|
|
To manage asset and vulnerability tags If a user wants a role to manage assets and tags will require the minimum permissions as specified. |
|
|
To manage patch policies If a user wants a role to manage patches will require the minimum permissions as specified. |
|
|
To view catalogs A non-admin user who can only view catalogs will require the minimum permissions as specified. |
|
|
To manage compliance operations If a user wants a role to manage compliance will require the minimum permissions as specified. |
|
|
To add connectors If a user wants a role to add and manage connectors will require the minimum permissions as specified. |
|
|
To view connectors If a user wants a role to only view connectors will require the minimum permissions as specified. |
|
Important: This user role can be combined with other user roles. |
To perform remediation operations If a user wants a role to perform the following actions will require the minimum permissions as specified:
|
|
|
|
| |
|
| |
To remediate vulnerabilities If a user wants a role to perform remediation and vulnerability operations will require the minimum permissions as specified. |
|
|
Default permissions assigned for TrueSight Server Automation roles in BMC Helix Portal
A role is created in BMC Helix Portal, with the same name as provided in the Server Automation Role Name field while configuring the TrueSight Server Automation connector. This role has the default permissions, as shown in the table below:
Role | Permissions |
---|---|
Connector |
|
Vulnerability |
|
Patch policy | Manage |
Security group |
|
SLA |
|
Catalog |
|
Compliance | Manage |
Tag | Manage |
Operation |
|
Operation template |
|
When you import a security group into TrueSight Server Automation endpoint, a role with the same name is created in the BMC Helix Portal, with the following default permissions, as shown in the table below:
Role | Permissions |
---|---|
Connector | View |
Vulnerability |
|
Patch policy | Manage |
Security group | View |
SLA | View |
Catalog | View |
Compliance | Manage |
Tag | Manage |
Operation |
|
Operation template |
|