This document describes how to install Qualys Cloud Agents (Windows and Linux) for Azure instances from the Azure Security Center console and view vulnerability assessment findings within Azure Security Center and your Qualys subscription.
Azure Security Center provides a unified security management and monitoring console for Azure infrastructure. Qualys is integrated into the Azure security center's partner solutions for Vulnerability assessment. The security center detects the virtual machines without the solution and automates the deployment of the lightweight Qualys cloud agents on them. The agents gather vulnerability data and send it to the Qualys Cloud Platform, which in turn, provides vulnerability and health monitoring data back to Azure Security Center.
Introduction Overview Video - Qualys Azure Integration
Info from Microsoft - Vulnerability assessment in Azure Security Center | Microsoft Docs
This document describes briefly how to deploy the Qualys Cloud Agents from Azure Security Center.
Want to learn more about Microsoft Azure? Check out the Azure Support page.
We'll help you with these steps:
Login into the Microsoft Azure portal and navigate to "Security Center".
Deploying Qualys Cloud Agents
Qualys agents are integrated into the Recommendations for the vulnerability assessment solution within the security center. Security center automatically detects the virtual machines and with this integration, users can directly deploy the Qualys Cloud Agent.
Click on "Recommendations", then click "Install a vulnerability assessment solution on your virtual machines".
From the list of recommendations select one or many* virtual machines where you want to deploy the Cloud Agents.
Select to 'Create New'. If you have already gone through the flow once, the Qualys solution will be available in the 'Use existing solution" list under this option.
Select Qualys solution from the list.
Specify the inputs for the deployment. Select a Name for the solution and fill out rest of the inputs.
You need to have a subscription with Qualys to get the license code and public key needed for the deploying the agent.
When generating the Agent key toggle the "Deploying in Azure Cloud" selector. See further detailed instructions in the "Retrieve License code and key from Qualys" section of this document.
Follow the section inline, to retrieve the License code and Public Key.
If you are NEW to Qualys, you can review the Qualys solution and sign up for a free trial from 'Sign up for the solution' link.
If you wish for this VM solution to be deployed to any VM found without a VM solution, within the selected resource group, enable "Auto deploy".
Note: For subsequent deployments, choose the solution you just created from the 'Existing Solution' list. The inputs are saved, so you don't need to retrieve the code and key from your Qualys subscription again.
Upon deploying the agents, vulnerability assessment from Qualys will show up for the virtual machines where the solution is deployed.
From Security Center - Navigate to "Security solutions" then select the VM solution by clicking "VIEW".
Here you can view the health status of all associated resources to this VM solution.
Click on a VM to get more details.
Click "View findings" to review the Qualys findings.
To learn more about the vulnerability, click the vulnerability in ASCC.
Alternatively you can click the link 'Solution Console' back on the VM solution blade. This method provides the QID information for the specific vulnerability.
Follow the remediation instructions to resolve the vulnerability.
You can also login into Qualys and review the vulnerability information for the virtual machines in Azure.
Use the tags to generate a report to view all the vulnerabilities for assets in Azure.
Login into your Qualys subscription. Navigate to the "Cloud Agent" application from the menu, then select "Activation Keys".
Click on "New Key" and generate a new activation key. We recommend you handle the Azure cloud deployments via a separate Activation Key. Additionally, manage your departments with separate activation keys.
Specify a name to identify it uniquely (example:Azure Security Center Key) and select Vulnerability Management and/or Policy compliance modules depending on your licenses.
We encourage you to have both the solutions to secure your assets in Azure completely.
As a best practice, we recommend you to create a Tag for Azure and use that tag to be dynamically associated with the assets identified via the key. Refer to the section 'Creating a Tag' for Azure to create a new tag.
Currently, as a part of this integrated deployment is only available for Windows and Linux agents. (Linux agent support is newly added).
Click 'Install Instructions' under Windows or Linux. Choose 'Deploying on Azure' and retrieve the keys from the page
Copy the License Code and Public Key and use it in during Deploying the agent.
Tags provide you with an ability to uniquely list out the assets. For this exercise, we will create a new tag 'Azure' and use that to identify the assets in the Azure cloud from the rest. Create additional tags as it applies to your organization, in a similar way.
Navigate to the Asset View and create a new Tag from the 'Tag' page.
The tag created shows up in the list of Tags. Associate the tag during key generation.
- Users can create Power shell methodology against the Azure Security Center APIs to automate the process.
- If you are looking to leverage the virtual appliance scanner in Azure, follow the document 'Scanning in Microsoft Azure' to deploy the virtual scanners from the Azure Marketplace.
Qualys Cloud Agent Linux is pre-authorized to install into Marketplace Images running supported operating systems. (See the Cloud Agent Linux Installation Guide for list of supported operating systems.)
For custom operating system images, each image needs to have the two pre-requisites before the Cloud Agent Linux can be deployed.
1. The Microsoft Azure agent needs to be provisioned and working in the image.
a. The Azure agent is the method to deploy/provision the Qualys Cloud Agent into the image.
2. The image's VHD custom properties need to be modified to add in an identifiable operating system information.
Example for custom images based on Red Hat 7.5:
More information on configuring Azure property files available here: Update-AzureRmImage (AzureRM.Compute) | Microsoft Docs
Looking for more help?
Check out our Help Center.