on Jan 21, 2019If you are like me and have experienced where Tag's get out of sync and are manually selecting them for re-evaluation through the UI. Then you know this can take a bit a bit of time to get them in sync. Re-Evaluation of your TAG's through the API will enable you to be more pro-active in your asset tagging and management of Qualys data. This will also help keep data in sync for your dashboards and widgets which leverage tags.
Why re-evaluation of your tags is important?
TAG's at times can get out of sync. The same key advantages of tags can also be their downfall. TAGs are considered a maturity level use case for asset management, which helps with organization and identification of assets. Tags can help you build a more robust Reporting, Scanning, Threat Remediation, Continuous Monitoring, Cloud Agent deployment and asset classification within your organizations Qualys life cycle. TAGs work based on the TAG engine rule defined. This means that assets get assigned tags if and when a condition is met, as defined in the tag condition engine. This same benefit means that if an asset is not scanned, it could result in the tag getting out of sync with old data. This is why we recommend the purging of old data.
Demonstration: New
API Guide - Evaluate Tag:
Asset Mgmt and Tagging v2 APISee Page: 31
* * * Re-Evaluate the Tags as needed * * *
| Evaluate all tags that have Groovy Script tag rules. |
|---|
API Request: **Note the POD API url & the file.xml needs to be created** |
POD 1: curl -u "USERNAME:PASSWORD" -H "content-type: text/xml" -X "POST" --data-binary @- "https://qualysapi.qualys.com/qps/rest/2.0/evaluate/am/tag" < file.xml |
POD 2: curl -u "USERNAME:PASSWORD" -H "content-type: text/xml" -X "POST" --data-binary @- "https://qualysapi.qg2.apps.qualys.com/qps/rest/2.0/evaluate/am/tag" < file.xml |
POD 3: curl -u "USERNAME:PASSWORD" -H "content-type: text/xml" -X "POST" --data-binary @- "https://qualysapi.qg3.apps.qualys.com/qps/rest/2.0/evaluate/am/tag" < file.xml |
| Request POST data: file.xml | TAG Rule Types: |
|---|---|
| <?xml version="1.0" encoding="UTF-8" ?> <ServiceRequest> <filters> <Criteria field="ruleType" operator="EQUALS"> INSERT RULE TYPE HERE </Criteria> </filters> </ServiceRequest> | GROOVY |
Help Link:
POD - 1 - Apply Tags to Organize Your Assets
POD - 2 - Apply Tags to Organize Your Assets
POD - 3 - Apply Tags to Organize Your Assets
References:
Related community Posts:
Additional Dashboards: performance_mgmt
Dashboard Toolbox - Asset View: How To - Importing Dashboard json
- - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - -
Dashboard Toolbox - AssetView: Performance Management (v1.0)
Dashboard Toolbox - AssetView: Host Scan Time Management (v1.0)
Dashboard Toolbox - AssetView: Scanning Activity Management (v1.0)
Dashboard Toolbox - AssetView: Open Ports Management & RTI (v1.0)
Dashboard Toolbox - AssetView: EOL/Obsolete Software & RTI MGMT (v1.0)
Dashboard Toolbox - AssetView: Windows Authentication Management (v1.0)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - - - - - - - - - - - - -
Dashboard Toolbox - VM DASHBOARD BETA: Windows Authentication Management (v1.4)
Credits
fjimenez This page contains information to create a Scorecard dashboard leveraging data in your Qualys Vulnerability Management subscription. This dashboard is part of AssetView Dashboard Program. If you have any questions regarding the content, please comment below or Contact Support - Technical Assistance Inquiry Form | Qualys, Inc.
Back to Dashboarding and Reporting
don't forget to check for success as I got failures. Be sure your using TLS 1.2 or TLS 1.1 as a minimum.
You may also need the --insecure flag on the CURL command.