User Roles and Permissions
The access to the Qualys Core and Qualys Policy Compliance/Policy Audit applications is restricted based on the user roles.
Permissions Required for Qualys Core Application
The following table presents the user groups and associated roles and permissions for the Qualys Core application:
Role |
Permissions |
---|---|
x_qual5_core.admin |
An administrative user of the application. Create, Write, Read, and Delete access to all aspects of the application. |
x_qual5_core.create
|
Can see the Create CI UI action from host records. |
x_qual5_core.
|
Grants access to any Data Receiver API Endpoints available globally across the Qualys for ServiceNow app and add-ins. These endpoints are used to push data from Qualys into ServiceNow. You should give this role to the ServiceNow Service Account, which Qualys uses for API Authentication. # API Endpoints /api/x_qual5_core/v1/data_receiver/
|
x_qual5_core.connector_user |
This role allows the user to create, modify, and delete Connector Records. |
x_qual5_core.
|
This role allows the user to read/write the General Settings values of the application. |
x_qual5_core.import_user |
This role allows the user to import_set tables for debugging and API Calls. |
x_qual5_core.host_user |
This role allows the user to Host Asset Records and related information, such as Asset Tags and Asset Groups |
x_qual5_core.user |
This role grants basic access to the Data Tables within Qualys Core and the basic information found in those tables. Generally, this role is not assigned directly to users; instead, it is automatically granted based on the add-on application roles associated with applications like Qualys VMDR. # Access to read the following
|
Permissions Required for Qualys Policy Compliance/Policy Audit
The following table presents the user groups and associated roles and permissions for Qualys Policy Compliance/Policy Audit application:
Roles |
Permissions |
---|---|
itil | This role is required to access the ServiceNow incident table. |
x_qual5_pc_user | |
x_qual5_pc.admin | |
glide.http.outbound.max_timeout.enabled | |
glide.rest_outbound.ecc_response.timeout |