Azure - Defender for Cloud

1. About this document

This document provides step-by-step instructions to configure "Azure - Defender for Cloud" (written as "Azure" in this document) in SAFE.

2. Introduction

This integration allows you to onboard assets from Azure and fetch recommendations (referred to as findings in SAFE). SAFE admins can configure this integration from the "Azure - Defender for Cloud" card available on the SAFE Hooks page. Once this integration is configured, SAFE fetches the security misconfiguration detected by Microsoft Defender for Cloud using the Azure Security Center Default policy assignment. This policy assignment depends on the Azure Security Benchmark and utilizes it to quantify cloud-related risks.

• After a successful configuration, SAFE will automatically onboard the Azure assets. You can view the Azure assets under the "Cloud-Azure" group.
• SAEF pulls in the MITRE ATT&CK Technique mapping for controls from Azure. 
• In addition to the auto-sync, SAFE admins can perform an on-demand sync with Azure to pull the assets and misconfigurations.
• SAFE uses REST APIs provided by Microsoft to consume recommendations data from Microsoft Defender for Cloud. These REST APIs are available at https://management.azure.com/* endpoints. 

3. Prerequisites

1. Microsoft Defender for Cloud is enabled for your Azure subscriptions.
2. All subscriptions have the Defender for Cloud default policy enabled. 
3. The following privileges are needed for a user in Azure to generate the connection details:
   1. For manually creating applications and assigning permissions:
      1. Sufficient privileges/permissions to create an application.
      2. Sufficient privileges/permissions to create a Service Principal account.
      3. Sufficient privileges/permissions to assign the Service Principal account a "Reader" role to the relevant subscriptions.
   2. [Optional] For generating credentials using a script:
      1. Access to the Cloud Shell of your Azure subscription to execute the PowerShell script provided by SAFE.
4. SAFE access with an admin role.

4. Generate connection details

You have two methods for generating the connection details (Tenant ID, Client ID, and Client Secret):

1. Manual method by registering an app
2. PowerShell script method

4.1. Manual method by registering an app

4.1.1. App Registration 

1. Log in to the Azure Portal. 
2. Navigate to Azure Active Directory.
   
3. Go to the App registrations and click the New Registration button.
   
4. On the app registration page, enter the Name for the application, select the Account Type, and Redirect URI. 
   1. Name: Enter a name of your choice. For example, SAFE-Azure App  
   2. AccountType: Select the option "Accounts in the organizational directory only (Default Directory only - Single Tenant)"
   3. Redirect URI: This can be left blank.
      
5. Click the Register button. The system registers the application.

4.1.2. Get the Client ID and Tenant ID

1. Go to the Application overview page you have created above.
2. You can find the Client ID and Tenant ID on the application's overview page.
   
3. Save the Client ID and Tenant ID on your system for later usage while configuring the Azure to SAFE.

4.1.3. Create the Client Secret

When we register a new application in Azure, it does not have any client secrets. To create a Client Secret:

1. Navigate to Certificates & Secrets from the left navigation.
2. Click the New Client Secret button.
3. Enter the Description and Expiry for the Client Secret.
   
4. Click the Add button.
5. The system adds the Client Secret and displays the details on the same page.
   
6. Save the Client Secret on your system for later usage while configuring the Azure in SAFE.

4.1.4. Assign reader role in the subscriptions to the created app

4.1.4.1 Get the Subscription

1. Go to the Azure Portal.
2. Search Subscriptions in the search bar and click it.
   
3. On the subscriptions page, the system displays all your Azure subscriptions. 
4. Search and click the subscription to which you want to assign the reader role for the app.
   

4.1.4.1 Assign Reader Role

You must assign a reader role to the subscriptions to sync Azure with SAFE. To assign the reader role:

1. Go to the Subscription Overview page on the Azure Portal.
2. Click the Access Control (IAM) button from the left navigation.
   
3. Click the Add button and then click the Add role assignment option.
4. On the Role tab of the Add role assignment page, select the Reader role and click Next.
   
5. On the Member tab Add role assignment page, click the + Select Member button and select the member of the application you created above.
   
   
6. Click Next and Save the settings to assign the reader role.
   To learn more, refer to Microsoft documentation here.

4.2 [Alternate Method] Generate connection details via PowerShell Script

You must run a Powershell script on your Azure portal to generate the connection details (Tenant ID, Client ID, and Client Secret). First, download the PowerShell script attached here.

Follow the below step-by-step procedure to generate the connection details:

1. Login to your Azure portal.
2. Click the Cloud Shell terminal icon located at the top right corner (refer to the screenshot below).
   
3. In the PowerShell terminal, execute the "Connect-AzureAD" command to enable the usage of Active Directory cmdlet requests.
   
4. Upload the PowerShell script (azureSafeOnboardingScript.ps1) attached above.
   
5. Execute the PowerShell script to create a Service Principal account and assign "Reader" access to subscriptions using one of the following approaches:
   ApproachA: If you want to provide "Reader" access to selected subscriptions for which your current user has privileged access, run the script with the following command-line argument:
   PS /home/user1> ./azureSafeOnboardingScript.ps1 "MySubscription1" "MySubscription2"
   ApproachB: If you want to provide "Reader" access to all subscriptions for which your current user has privileged access, run the script:
   PS /home/user1> ./azureSafeOnboardingScript.ps1
6. Once the PowerShell script execution is complete, the system creates a Service Principal account named "SAFE-Azure-App" with "Reader" access to all subscriptions.
7. The system will display the TenantID, ClientID, and ClientSecret. Make sure to copy and save these values for use while configuring Azure in SAFE in the next section.

5. Configure Azure in SAFE

Follow the below steps to configure Azure in SAFE.

1. Go to the SAFE Hooks and click the "Azure - Defender for Cloud" card.
2. Enter the TenantID, ClientID, and ClientSecret generated above.
3. Enter a value for the Auto-SyncFrequency. This controls how often SAFE will synchronize with Azure for the most recent data.
4. Click the Test Connection button.
5. Once the connection is validated, click the Save button.
6. Once the configuration is saved, click the SyncNow button to trigger the on-demand sync outside the scheduled auto sync.
   

6. View Result

To view the assets:

1. On the Azure configuration page, click the See Updated Assets option available at the top-right of the History table.
   
2. The system redirects you to a filtered assets list of Azure assets. 
3. Alternatively, you can navigate to Technology > Assets and filter the asset list for signal source equals security.safe.azure.
   

To view the findings:

1. Navigate to the Risk Scenario created for the AWS assets.
2. Scroll down to the Findings section. Here you can see the finding details of the Azure assets.

7. Integration History

SAFE displays the Integration Sync History table on each integration's configuration page, providing a comprehensive overview of sync history, including action, start time, started by, and sync status.

Refer to Integration History for more details.

8. SAFE's Outgoing IP Addresses

Click here to find the outgoing IP addresses of SAFE. All traffic to any integrations in SAFE will see one IP address as the source IP of the incoming connection.

9. Add additional Azure accounts in SAFE

9.1. Configure

You can add additional Azure accounts in SAFE only via SAFE REST APIs. To add an additional Azure account, follow the below step-by-step instructions:

1. Generate the connection details by following the steps discussed above in step 4.
2. Prepare a JSON file with the necessary configuration details (Clicent ID, Tenant ID, Client Secret, and Auto-sync frequency).
   Here is an example JSON:
   {
   "type":"cloud",
   "subtype":"azure",
   "config":{
   "autoSync":1,
   "clientId":"<insert ID here>",
   "tenantId":"<insert ID here>",
   "clientSecret":"<insert secret here>",
   "sensitiveFields":[
   "clientSecret"
   ]
   }
   }
3. Log in to SAFE as an admin and navigate to SAFE REST APIs by clicking the help icon at the top right corner.
4. Scroll down to the Integrations section, and expand POST /api/v3/integrations.
   
5. Click the Try it out button. 
6. In the request body, replace the example JSON with the one you prepared with connection details.
7. Click the Execute button. The system adds the integration to SAFE.
   
8. Scroll down and check the response body and record the Integration ID.
9. Now scroll down a little further and expand POST /api/v3/integrations/{id}?action={action}.
10. Click the Try it out button.
11. Insert the Integration ID you recorded and type "test" as the action.
12. Click the Execute button.
13. If the test is successful, repeat the same step using "sync" as the action
14. Click the Execute button. SAFE will now start pulling in the data from Azure.

9.2. Check status

1. On the SAFE REST API documentation, navigate to the integrations.
2.  Expand GET /api/v3/integrations/{id}.
3. Click the Try it out button.
4. Enter the Integration ID used when setting up the integration.
5. Enter Execute. The system displays the configuration and its current status.