Microsoft Azure

Azure Security Center: Server Vulnerability Assessments Settings

API spec for Microsoft.Security (Azure Security Center) resource provider

Identity & security#openapi

Fork copies the collection into your workspace, without the publisher's secrets, so you can add your own key and send requests. Star saves it to your starred APIs (Account › Marketplace) and helps others find it.

Overview

API spec for Microsoft.Security (Azure Security Center) resource provider

Endpoints 4

ServerVulnerabilityAssessmentsSettings

  • GETServerVulnerabilityAssessmentsSettings_ListBySubscription/subscriptions/:subscriptionId/providers/Microsoft.Security/serverVulnerabilityAssessmentsSettingsGet a list of all the server vulnerability assessments settings over a subscription level scope
  • GETServerVulnerabilityAssessmentsSettings_Get/subscriptions/:subscriptionId/providers/Microsoft.Security/serverVulnerabilityAssessmentsSettings/:settingKindGet a server vulnerability assessments setting of the requested kind, that is set on the subscription
  • PUTServerVulnerabilityAssessmentsSettings_CreateOrUpdate/subscriptions/:subscriptionId/providers/Microsoft.Security/serverVulnerabilityAssessmentsSettings/:settingKindCreate or update a server vulnerability assessments setting of the requested kind on the subscription
  • DELETEServerVulnerabilityAssessmentsSettings_Delete/subscriptions/:subscriptionId/providers/Microsoft.Security/serverVulnerabilityAssessmentsSettings/:settingKindDelete the server vulnerability assessments setting of the requested kind from the subscription

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
4 operations on 2 pathsGET 2PUT 1DELETE 1
Main resources
ServerVulnerabilityAssessmentsSettings 4
Response formats
application/json
Description format
Swagger 2.0, API version 2023-05-01

How to test the Azure Security Center: Server Vulnerability Assessments Settings in Swastik Codes

  1. Open the APISelect “Fork & run in Swastik Codes” on this page. Sign in or create a free account if asked.
  2. Fork it into your workspaceChoose a workspace. You get your own copy of the Azure Security Center: Server Vulnerability Assessments Settings collection, without the publisher's secrets.
  3. Add your credentialsThis API uses OAuth 2.0 (implicit flow) with 1 scope. Add yours in the collection's variables or an environment; the requests already reference it.
  4. Send a requestPick an endpoint, for example “ServerVulnerabilityAssessmentsSettings_ListBySubscription” (GET /subscriptions/:subscriptionId/providers/Microsoft.Security/serverVulnerabilityAssessmentsSettings), and press Send. Check the response, add tests and run the whole collection with the runner.

Frequently asked questions

What is the Azure Security Center: Server Vulnerability Assessments Settings?

API spec for Microsoft.Security (Azure Security Center) resource provider It is listed under Identity & security and has 4 endpoints.

Who publishes the Azure Security Center: Server Vulnerability Assessments Settings?

It is listed from Microsoft Azure's public API description (an OpenAPI document), not published by Microsoft Azure on Swastik Codes. Anyone who controls azure.com can claim the profile by adding a DNS TXT record.

What is the base URL of the Azure Security Center: Server Vulnerability Assessments Settings?

Requests go to https://management.azure.com. Endpoint paths are added to this base URL.

How do I authenticate with the Azure Security Center: Server Vulnerability Assessments Settings?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure Security Center: Server Vulnerability Assessments Settings have?

4 operations on 2 paths (2 GET, 1 PUT, 1 DELETE). The largest groups are ServerVulnerabilityAssessmentsSettings.

Is forking the Azure Security Center: Server Vulnerability Assessments Settings free?

Yes. Forking copies the collection into your workspace for free. It has been starred 0 times and forked 0 times.

Suggest an API

Tell us which public API is missing. We check it, then add it here with its endpoints when it has an OpenAPI (Swagger) description.