- 16 Mar 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Qualys Cloud Platform - Add Tags to Host Asset
- Updated on 16 Mar 2023
- 3 Minutes to read
-
Print
-
DarkLight
-
PDF
Qualys Cloud Platform - Add Tags to Host Asset adds a specified list of tags to each device entity retrieved from the saved query supplied as a trigger (or to devices selected in the asset table) that is a host asset in Qualys.
See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.
General Settings
- Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonious. You can change the name according to your needs.
- Add description (optional) - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
- Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
- A query only returns results for the asset type it was created for.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs and Adapter Fetch History Modules
- Action name - The name of the Main action. A default value is added by Axonious. You can change the name according to your needs.
- Configure Action Conditions - Toggle on to enter a condition statement. See Configuring Enforcement Action Conditions to learn more about condition statement syntax.
Connection Settings
- Use stored credentials from the Qualys Cloud Platform adapter (optional, default: empty) - Select this option to use the first connected Qualys Cloud Platform adapter credentials.
- Qualys Cloud Platform Domain (optional, default: empty) - The hostname of the Qualys API (for example, qualysapi.apps.qualys.com). For more details on how to determine your Qualys API URL, see Identify your Qualys platform.
- User name and Password (optional, default: empty) - The credentials for a user account that has the Required Permissions to add a specified list of tags to each host asset in Qualys.
- Verify SSL (required, default: False) - Verify the SSL certificate offered by the host supplied in Qualys Cloud Platform Domain. For more details, see SSL Trust & CA Settings.
- If enabled, the SSL certificate offered by the host will be verified against the CA database inside of Axonius. If it fails validation, the connection will fail with an error.
- If disabled, the SSL certificate offered by the host will not be verified against the CA database inside of Axonius.
- HTTPS proxy (optional, default: empty) - A proxy to use when connecting to Qualys Cloud Platform Domain.
- If supplied, Axonius will utilize the proxy when connecting to the host defined for this connection.
- If not supplied, Axonius will connect directly to the host defined for this connection.
Action Settings
-
Tags (required, default: empty) - Specify at least one new/existing tag in Qualys to be associated with each of the host assets in Qualys. Tag name is case sensitive.
NOTEIf Axonius will fail to create a tag or add tags to a host asset, Axonius will roll back the entire action and will fail it.
-
Parent tag name (optional, default: empty) - Associate a Qualys tag as a parent tag of all the specified tags. Tag name is case sensitive.
- If supplied, Axonius will add specified tag as a parent tag of all the specified tags.
- If not supplied, Axonius will not set any parent tag for the specified tags.
NOTEThe specified tag must exist in Qualys. If it does not exist in Qualys, Axonius will fail to run the action.
Required Permissions
The value supplied in User Name must be associated with one of the following user roles and with the following permissions:
- Managers with full scope
- Other roles with the following permissions:
- Desired host assets in scope.
- Access to the API.
- Tag permission: "Create User Tag", "Delete User Tag"
- Asset Management permission: "Read Asset", "Update Asset".
To enable user access to the API:
-
From Qualys, click the user button next to the Logout -> User Profile.
-
The Edit User screen opens. Click User Role -> select the API checkbox to enable API Access.
-
Save changes.
For more details about other Enforcement Actions available, see Action Library.