Frequently Asked Questions
We have compiled a list of a few questions that you may have for Administration application.
Enhanced Role-Based Access Control (RBAC)
The enhanced Role-Based Access Control (RBAC) feature centralizes user and role management in the Administration application. It gives you more granular control over roles and permissions, so you can assign access based on user responsibilities and reduce unnecessary administrative privileges.
No. Existing users retain access to their assigned applications and assets based on their existing roles. This helps minimize disruption during the transition.
Existing roles and permissions are transitioned based on the defined migration behavior. For details on how each existing role is handled, see the role and permission comparison.
Yes. Granular permissions let you delegate specific tasks, such as activating or deactivating users, without granting broader administrative privileges.
Can I have multiple roles?Can I have multiple roles?
Yes. You can have one primary role and one or more additional roles. This lets you configure access based on the your business and functional responsibilities.
No. You cannot modify the roles assigned to your account or change the associated permissions to increase your privileges.
Can the predefined Administrator role be modified?Can the predefined Administrator role be modified?
No. The Administrator role is read-only. This prevents unintended changes to the role and its permissions.
How are UI access and API access controlled?How are UI access and API access controlled?
Global UI Access and API Access settings determine how you can access Qualys. Product-specific permissions separately determine what you can do within each application.
No. API Access only allows you to access Qualys through APIs. Your product permissions continue to determine which API operations you can perform.
Administrators receive real-time email notifications for important account activities, such as email address changes, privilege escalation, and account deactivation, reactivation, and deletion.
Note: Email notifications for critical account changes are currently available in beta.
User Groups and IdP Sync
What happens when a User Group is deleted? What happens when a User Group is deleted?
When deleting a User Group, you can choose to detach all users, deactivate all users, or delete all users along with the group. Each option provides flexibility of how users are retained or removed from the platform.
What are the steps to configure an IdP connector? What are the steps to configure an IdP connector?
On the Connector application, create a connector by entering authentication details such as tenant ID, secret ID, and client secret. After authentication, Azure AD groups are mapped to Qualys User Groups, enabling automatic user synchronization and management.
Administrators can view users and their assigned roles under the User Listing page.
Once users are provisioned through an AD-synced User Group, their roles are assigned based on the group configuration defined in the IdP (Azure AD). In the current implementation, role transitions outside of the defined mapping such as moving from a 'Manager role to Remediation' or 'POC' are not a part of the supported transition matrix.
Are all the user roles supported by User Groups? Are all the user roles supported by User Groups?
Except for the Super Users, all user roles are supported through User Groups.
How are the changes to the user access handled? How are the changes to the user access handled?
Access changes can be managed centrally by updating the User Group configuration. All the users associated with that group automatically inherit the updated access settings.
One Azure AD group can be mapped to only one Qualys group, and one user can only be a part of only one Azure AD group.