Connect to your Azure Security Centre app for OAuth.
To setup your Azure Security Centre in Cobalt for OAuth, you will need the following credentials from your Microsoft Azure account:
To create a Azure Security Centre app and acquire the above mentioned credentials, please follow the steps mentioned below:
Overview
in the side menu > Click on +Add
> Select App Registration
.Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)
under Supported Account Types.Apps catalog
in Cobalt > Search for Azure Security Centre
> Settings
> Use your credentials
> Callback Url
> Copy it.Web
, paste the Callback Url as the URL and click Register
.If you already have an app created, then follows these steps to add Redirect URL:
Select your Application > Select Authentication in side menu > Under Platform configurations, press the Add a platform button > Select Web > Paste the Callback Url > Click on Configure > Click Save button at the bottom.
Manage
> API permissions
in the side menu > Click on + Add a permission
.Microsoft Graph
card under Microsoft APIs > Choose Application permissions
> Select the mandatory scopes > click on the Add Permissions
button.
Certificates and Secrets
in the side menu and under Client Secrets tab, press the + New client secret
button. Give a Description, select the best expiry for your application and click Add
to create your credentials.Value
column.Overview
in the side menu > Essentials
tab > Copy the Client ID under Application (client) ID
and Tenant ID under Directory (tenant) ID
.App settings page lets you configure the authentication settings for an OAuth2
based application. For your customers to provide you authorization to access their data,
they would first need to install your application. This page lets you set up your application credentials.
Provide the acquired Client ID and Client Secret under Settings of the app and save it.
Cobalt lets you configure what permissions to ask from your users while they install your application. The scopes can be added or removed from the App settings page, under Permissions & Scopes
section.
For some applications Cobalt sets mandatory scopes which cannot be removed. Additional scopes can be selected from the drop down. Cobalt also has the provision to add any custom scopes supported by the respective platform.
Once the scopes has been added to the application in Cobalt, go to your Microsoft Azure account and update the scopes as added on Cobalt.
Select the OAuth App created for Cobalt and follow Step 7 and 8 above.
If you are facing scopes missing or invalid scope error. Make sure you are not passing any custom scope not supported by the platform. And, the scopes selected here are identical to the ones selected in the platform.
Once the above setup is completed, you can create orchestrations of your use-cases using Azure Security Center actions and triggers. Following are the set of Azure Security Center actions and triggers supported by Cobalt.
Location
Task
Others
Location
Task
Others
There are no triggers in this application.
Connect to your Azure Security Centre app for OAuth.
To setup your Azure Security Centre in Cobalt for OAuth, you will need the following credentials from your Microsoft Azure account:
To create a Azure Security Centre app and acquire the above mentioned credentials, please follow the steps mentioned below:
Overview
in the side menu > Click on +Add
> Select App Registration
.Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant)
under Supported Account Types.Apps catalog
in Cobalt > Search for Azure Security Centre
> Settings
> Use your credentials
> Callback Url
> Copy it.Web
, paste the Callback Url as the URL and click Register
.If you already have an app created, then follows these steps to add Redirect URL:
Select your Application > Select Authentication in side menu > Under Platform configurations, press the Add a platform button > Select Web > Paste the Callback Url > Click on Configure > Click Save button at the bottom.
Manage
> API permissions
in the side menu > Click on + Add a permission
.Microsoft Graph
card under Microsoft APIs > Choose Application permissions
> Select the mandatory scopes > click on the Add Permissions
button.
Certificates and Secrets
in the side menu and under Client Secrets tab, press the + New client secret
button. Give a Description, select the best expiry for your application and click Add
to create your credentials.Value
column.Overview
in the side menu > Essentials
tab > Copy the Client ID under Application (client) ID
and Tenant ID under Directory (tenant) ID
.App settings page lets you configure the authentication settings for an OAuth2
based application. For your customers to provide you authorization to access their data,
they would first need to install your application. This page lets you set up your application credentials.
Provide the acquired Client ID and Client Secret under Settings of the app and save it.
Cobalt lets you configure what permissions to ask from your users while they install your application. The scopes can be added or removed from the App settings page, under Permissions & Scopes
section.
For some applications Cobalt sets mandatory scopes which cannot be removed. Additional scopes can be selected from the drop down. Cobalt also has the provision to add any custom scopes supported by the respective platform.
Once the scopes has been added to the application in Cobalt, go to your Microsoft Azure account and update the scopes as added on Cobalt.
Select the OAuth App created for Cobalt and follow Step 7 and 8 above.
If you are facing scopes missing or invalid scope error. Make sure you are not passing any custom scope not supported by the platform. And, the scopes selected here are identical to the ones selected in the platform.
Once the above setup is completed, you can create orchestrations of your use-cases using Azure Security Center actions and triggers. Following are the set of Azure Security Center actions and triggers supported by Cobalt.
Location
Task
Others
Location
Task
Others
There are no triggers in this application.