ServerVulnerabilityAssessment Class
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
A server vulnerability assessment.
[Microsoft.Rest.Serialization.JsonTransformation]
public class ServerVulnerabilityAssessment : Microsoft.Azure.Management.Sql.Models.ProxyResource
[<Microsoft.Rest.Serialization.JsonTransformation>]
type ServerVulnerabilityAssessment = class
inherit ProxyResource
Public Class ServerVulnerabilityAssessment
Inherits ProxyResource
- Inheritance
- Attributes
Constructors
ServerVulnerabilityAssessment() |
Initializes a new instance of the ServerVulnerabilityAssessment class. |
ServerVulnerabilityAssessment(String, String, String, String, String, String, VulnerabilityAssessmentRecurringScansProperties) |
Initializes a new instance of the ServerVulnerabilityAssessment class. |
Properties
Id |
Gets resource ID. (Inherited from Resource) |
Name |
Gets resource name. (Inherited from Resource) |
RecurringScans |
Gets or sets the recurring scans settings |
StorageAccountAccessKey |
Gets or sets specifies the identifier key of the storage account for vulnerability assessment scan results. If 'StorageContainerSasKey' isn't specified, storageAccountAccessKey is required. Applies only if the storage account is not behind a Vnet or a firewall |
StorageContainerPath |
Gets or sets a blob storage container path to hold the scan results (e.g. https://myStorage.blob.core.windows.net/VaScans/). |
StorageContainerSasKey |
Gets or sets a shared access signature (SAS Key) that has write access to the blob container specified in 'storageContainerPath' parameter. If 'storageAccountAccessKey' isn't specified, StorageContainerSasKey is required. Applies only if the storage account is not behind a Vnet or a firewall |
Type |
Gets resource type. (Inherited from Resource) |
Methods
Validate() |
Validate the object. |
Applies to
意見反應
https://aka.ms/ContentUserFeedback。
即將登場:在 2024 年,我們將逐步淘汰 GitHub 問題作為內容的意見反應機制,並將它取代為新的意見反應系統。 如需詳細資訊,請參閱:提交並檢視相關的意見反應