You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/security-center/partner-vulnerability-assessment.md
+52-3Lines changed: 52 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,9 +19,9 @@ ms.author: memildin
19
19
20
20
If you're on the standard tier, you're able to use Azure Security Center's built-in vulnerability assessment tool as described in [Integrated vulnerability scanner for virtual machines](built-in-vulnerability-assessment.md). This tool doesn't require a Qualys license or even a Qualys account - everything's handled seamlessly inside Security Center.
21
21
22
-
Alternatively, you might want to deploy your own privately-licensed vulnerability assessment solution from [Qualys](https://www.qualys.com/lp/azure) or [Rapid7](https://www.rapid7.com/products/insightvm/). You can install one of these partner solutions on multiple VMs that belong to the same subscription.
22
+
Alternatively, you might want to deploy your own privatelylicensed vulnerability assessment solution from [Qualys](https://www.qualys.com/lp/azure) or [Rapid7](https://www.rapid7.com/products/insightvm/). You can install one of these partner solutions on multiple VMs that belong to the same subscription.
23
23
24
-
## Configuring a partner solution
24
+
## Configuring a partner solution (in the Azure portal)
25
25
26
26
1. On the **Security Center** dashboard, in the **Overview** section, click **Recommendations**.
27
27
@@ -60,8 +60,57 @@ Alternatively, you might want to deploy your own privately-licensed vulnerabilit
60
60
61
61
1. Click **OK**.
62
62
63
+
64
+
## Configuring a partner solution (using PowerShell and the REST API)
65
+
66
+
To programatically deploy your own privately licensed vulnerability assessment solution from [Qualys](https://www.qualys.com/lp/azure) or [Rapid7](https://www.rapid7.com/products/insightvm/), use the supplied script [PowerShell > Vulnerability Solution](https://github.com/Azure/Azure-Security-Center/tree/master/Powershell%20scripts/Vulnerability%20Solution).
67
+
68
+
This script uses the REST API to create a new Security Solution in ASC. The solution requires a license and a key provided by the service provider: Qualys or Rapid7.
69
+
70
+
> [!IMPORTANT]
71
+
> Only one solution can be created per license. Attempting to create another solution using the same name/license/key will fail.
72
+
73
+
### Prerequisites
74
+
75
+
Required PowerShell modules:
76
+
77
+
- Install-module Az
78
+
- Install-module Az.security
79
+
80
+
### Running the script
81
+
82
+
To run the script, you'll need the relevant information for the parameters below.
83
+
84
+
|**Parameter**|**Required**|**Notes**|
85
+
|----|:----:|----|
86
+
|**SubscriptionId**|✔|The subscriptionID of the Azure Subscription that contains the resources you want to analyze.|
87
+
|**ResourceGroupName**|✔|Name of the resource group. Use any existing resource group including the default ("DefaultResourceGroup-xxx"). Since the solution isn't an Azure resource, it won't be listed under the resource group, but still it is attached to it.|
88
+
|**vaSolutionName**|✔|The name of the new solution.|
|**autoUpdate**|-|Enable (true) or disable (false) auto deploy for this VA solution. When enabled, every new VM on the subscription will automatically attempt to link to the solution.<br/>(Default: False)|
After the vulnerability assessment solution is installed on the target VM, Security Center scans the VM to detect and identify system and application vulnerabilities.
113
+
After the vulnerability assessment solution is installed on the target VM, Security Center scans the VM to detect and identify vulnerabilities in the system and application.
65
114
66
115
> [!NOTE]
67
116
> It might take a couple of hours for the first scan to complete. After that, it is an hourly process.
0 commit comments