--- sourceDocument: Brazil Security Management sourceDocumentLink: https://www.servicenow.com/docs/r/security-management Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Security Management ft:clusterId : - security bundleId : - security workflow : - Technology --- # Qualys # Qualys integration with Configuration Compliance {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Qualys integration with Configuration Compliance The Qualys Policy Compliance integration with ServiceNow Configuration Compliance enables automatic collection and analysis of configuration data. It integrates seamlessly with Qualys Integration for Security Operations to map configuration findings to Configuration Items (CIs) and business services, helping you determine the impact and priority of potential misconfigurations. Multiple Qualys Cloud Platform deployments are supported, consolidating assets and vulnerabilities into a single Vulnerability Response instance, even if scan processes overlap. Show full answer Show less ## Host Tags Host tags are imported through the Qualys Host List integration and are primarily used for filtering in Vulnerability Response Assignment and Remediation Task Rules. Tags are case-insensitive, with the first imported tag taking precedence. It is recommended to run the Host List integration before creating rules or importing vulnerable items to ensure tags are available. Host tags are controlled by the global system property **snvul.importhosttags**, which is enabled by default and affects all instances when toggled. These tags help organize and track assets and can be selected during scan launches. ## Associating Tests with Test Groups By enabling the **snvulc.addpolicyaskey** system property, the Test group field is added to the Test form, allowing clear association of tests to their test groups. This facilitates differentiation of Test records with the same ID but associated with different groups. Note that this property cannot be disabled once enabled, so review relevant documentation before activation. ## Integration Details and Configuration * **Ignore Passed Test Results:** Starting in Configuration Compliance version 15.2.5, the **ignorepassedresult** parameter can be set to true to exclude passed test results during import, helping focus on current issues. This setting does not affect the proper closure of test results that have transitioned from failed to passed. * **API Credentials:** If you already use the Qualys Vulnerability Integration but need different API credentials for Configuration Compliance, you can update them via the Setup Assistant in Vulnerability Response by editing the Qualys API Credentials under the Qualys REST Details tab. ## Key Benefits for ServiceNow Customers * Automated data collection and continuous analysis of configuration compliance from Qualys within ServiceNow. * Consolidated asset and vulnerability data from multiple Qualys deployments reconciled with your CMDB. * Enhanced filtering and organization of assets through host tags, improving remediation workflows. * Improved visibility into test groups for efficient compliance tracking. * Flexible import settings to tailor test result handling according to your compliance needs. * Simple management of API credentials within ServiceNow for integration consistency. The Qualys Policy Compliance collects the data and automatically sends it to the Qualys application, which continuously analyzes and correlates the information. It easily integrates as the Qualys Integration for Security Operations to map configuration findings to CIs and business services to determine the impact and priority of potential misconfigurations. If you have multiple deployments of the Qualys Cloud Platform application, you can add an integration for each deployment. Assets, identified by multiple third-party deployments and their vulnerabilities, are consolidated and reconciled with your CMDB. This consolidation happens even when scan processes overlap between the multiple deployments. Data sourced from each deployment is identified and available in a single instance of Vulnerability Response. Note: You cannot delete the original vulnerability integration, but you can disable it. Integrations created from inactive templates are disabled by default. ## Host tags {#Qualys-cc-Integration__id_atk_mpv_mxb} All host tags are imported as part of the Qualys Host List integration. Host tags are used primarily for filtering in Vulnerability Response Assignment and Remediation Task Rules. They are displayed in the Discovered Item form. Note: The Qualys Host List integration should be run prior to creating the Assignment or Remediation Task Rules in Vulnerability Response so that all tags can be present in the rules and before vulnerable items are imported and grouped. * Tag storage is not case-sensitive. If a San Diego tag is created, then a SAN DIEGO tag cannot be stored in the Host tag table. "San Diego" and "SAN DIEGO" are considered to be the same host tag. Whichever tag was imported first wins. * Using host tags as a Group Key in a Remediation Task Rule can have unexpected results. Host tags are intended for use only in the condition builder. * Host tags are controlled by the global system property sn_vul.import_host_tags. This property is set to true by default. Turning off tags turns them off across all instances. {#Qualys-cc-Integration__ul_xxt_hvj_cjb} Host tags (also called asset tags) are used for organizing and tracking the assets in your organization. You can assign tags to your host assets. Then, when launching scans, you can select tags associated with the hosts you want to scan. The Host Tags module enables you to download host tag data from Qualys to your instance on a scheduled basis. ## Associating a Test with its Test Group {#Qualys-cc-Integration__section_dbd_ghp_ddc} To populate the Test group field on a Test form, enable the sn_vulc.add_policy_as_key system property. For more information on how a test is associated to its test group, impact of enabling this system property and post-requisites, see [KB1644268](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644268) article. Warning: You cannot disable the sn_vulc.add_policy_as_key system property once it is enabled. So, review the Impact section in the [KB1644268](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1644268) article before you enable this system property. When you enable this system property, after the next ingestion, the Test group field is added on the Test table and it populates the test group to which a test belongs to. Therefore, you can easily: * identify the Test Group to which a Test Result belongs to by dot-walking from Test to Test Group. * differentiate Test records with same Test id that are associated with different Test Groups. {#Qualys-cc-Integration__ul_hgg_53p_ddc} ## Integrating Qualys with the ServiceNow® Configuration Compliance application {#Qualys-cc-Integration__section_bpb_k2h_cyb} Ignore passed test results Starting with v15.2.5 of Configuration Compliance, the ignore_passed_result integration instance parameter for the Qualys Integration for Security Operations has been added.This parameter is set to false by default so that passed test results imported by Qualys are not ignored. * Set the parameter to true to ignore passed test results on import. * If activated, this parameter does not impact the closure of the test results. For example, if you activate the parameter, and a failed test result from a previous import has since passed, it will be closed correctly. {#Qualys-cc-Integration__ul_sxp_3ch_nhc} API credentials If the Qualys Vulnerability Integration is already installed on your system, and your API credentials are different than the ones you want to use for Configuration Compliance, go into Setup Assistant (in Vulnerability Response) and assign them to each Qualys PC integration. Navigate to AllQualys Vulnerability IntegrationPrimary Integrations and edit the Qualys API Credentials field under the Qualys REST Details tab. *[\>]: and then