Audit Microsoft Azure in Tenable Vulnerability Management

Tenable offers the ability to audit the Microsoft Azure Cloud environment to detect misconfigurations in the cloud environment and account settings using Tenable Vulnerability Management. Complete the following steps to Audit Microsoft Azure in Tenable Vulnerability Management.

For more information on the Microsoft Azure audit, see the Microsoft Azure Audit Compliance Reference in the Compliance Checks Reference.

Before you begin:

• Configure Azure as described in Configure Azure for a Compliance Audit.

Note: No pre-authorization is needed from Microsoft to perform the audit, but a Microsoft Azure account is required.

To audit Microsoft Azure in Tenable Vulnerability Management:

1. Log in to Tenable Vulnerability Management.

2. In the upper-left corner, click the button.

   The left navigation plane appears.

3. In the left navigation plane, in the Vulnerability Management section, click Scans.

   The Scans page appears.

4. In the upper-right corner of the page, click Create a Scan.

   The Select a Scan Template page appears.

5. Select the Audit Cloud Infrastructure template.

   The Audit Cloud Infrastructure page appears.
   
   

6. In the Name box, type a descriptive name for the scan.
7. (Optional) In the Description box, enter information to describe your scan.

8. Click Compliance.

9. Click Microsoft Azure.

   Tenable offers pre-configured compliance checks and provides the ability to upload a custom Azure audit file.

   Note: For information on creating a custom audit, see the Microsoft Azure Audit Compliance Reference in the Nessus Compliance Checks Reference Guide.

10. Click each compliance check you want to add to the scan.

11. If you choose to add a custom audit file, click Add File and select the file to upload.

12. Click Credentials.

13. Click Microsoft Azure.

    Note: See the Required User Privileges section in the Nessus User Guide for the required Microsoft Azure privileges.
    
    

14. Click the Authentication Method drop-down menu to select your preferred authentication method: key, password, or certificate.

    Configure the credentials for your selected authentication method.

    To configure key authentication:

    Option	Description	Required
    Tenant ID	The Tenant ID or Directory ID for your Azure environment.	Yes
    Application ID	The application ID (also known as client ID) for your registered application.	Yes
    Client Secret	The secret key for your registered application.	Yes
    Subscription IDs	List of subscription IDs to scan, separated by a comma. If this field is blank, all subscriptions are audited.	No

    To configure password authentication:

    Option	Description	Required
    Username	The username required to log in to Microsoft Azure.	Yes
    Password	The password associated with the username.	Yes
    Client ID	The application ID (also known as client ID) for your registered application.	Yes
    Subscription IDs	List of subscription IDs to scan, separated by a comma. If this field is blank, all subscriptions are audited.	No

    To configure certificate authentication:

    Option	Description	Required
    Tenant ID	The Tenant ID or Directory ID for your Azure environment.	Yes
    Application ID	The application ID (also known as client ID) for your registered application.	Yes
    Private Key	A PEM formatted 2048-bit RSA private key and certificate.	Yes
    Config File	Additional configuration parameters. Currently only applicable for SCuBA scans.	No
    Subscription IDs	List of subscription IDs to scan, separated by a comma. If this field is blank, all subscriptions are audited.	No

15. Do one of the following:

    • Click Save.

    • Click the drop-down arrow next to Save and select Launch to initiate the scan.

Note: For additional information on configuring Tenable Vulnerability Management scans, refer to the Tenable Vulnerability Management User Guide.