Microsoft Azure

Azure Security Center: Secure Score

API spec for Microsoft.Security (Microsoft Defender for Cloud) 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 (Microsoft Defender for Cloud) resource provider

Endpoints 6

Secure Score

  • GETSecureScores_List/subscriptions/:subscriptionId/providers/Microsoft.Security/secureScoresList secure scores for all your Microsoft Defender for Cloud initiatives within your current scope.
  • GETSecureScores_Get/subscriptions/:subscriptionId/providers/Microsoft.Security/secureScores/:secureScoreNameGet secure score for a specific Microsoft Defender for Cloud initiative within your current scope. For the ASC Default initiative, use 'ascScore'.
  • GETSecureScoreControls_ListBySecureScore/subscriptions/:subscriptionId/providers/Microsoft.Security/secureScores/:secureScoreName/secureScoreControls?$expand=definitionGet all security controls for a specific initiative within a scope

Secure Score Controls

  • GETSecureScoreControls_List/subscriptions/:subscriptionId/providers/Microsoft.Security/secureScoreControls?$expand=definitionGet all security controls within a scope

Secure Score Control Definitions

  • GETSecureScoreControlDefinitions_List/providers/Microsoft.Security/secureScoreControlDefinitionsList the available security controls, their assessments, and the max score
  • GETSecureScoreControlDefinitions_ListBySubscription/subscriptions/:subscriptionId/providers/Microsoft.Security/secureScoreControlDefinitionsFor a specified subscription, list the available security controls, their assessments, and the max score

API details

Base URL
https://management.azure.com
Authentication
OAuth 2.0 (implicit flow) with 1 scope
Operations
6 operations on 6 pathsGET 6
Main resources
Secure Score 3Secure Score Control Definitions 2Secure Score Controls 1
Response formats
application/json
Description format
Swagger 2.0, API version 2020-01-01

How to test the Azure Security Center: Secure Score 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: Secure Score 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 “SecureScores_List” (GET /subscriptions/:subscriptionId/providers/Microsoft.Security/secureScores), 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: Secure Score?

API spec for Microsoft.Security (Microsoft Defender for Cloud) resource provider It is listed under Identity & security and has 6 endpoints.

Who publishes the Azure Security Center: Secure Score?

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: Secure Score?

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

How do I authenticate with the Azure Security Center: Secure Score?

With OAuth 2.0 (implicit flow) with 1 scope.

How many endpoints does the Azure Security Center: Secure Score have?

6 operations on 6 paths (6 GET). The largest groups are Secure Score, Secure Score Control Definitions, Secure Score Controls.

Is forking the Azure Security Center: Secure Score 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.