Our Azure integration supports external facing IPs and hostnames from DNS zones.
Azure app service endpoints (including web-apps) would need to be added manually (as would internal only VMs).
Create an application for Intruder
Login to the Azure management portal > search for
App registrationsusing the search functionality > clickApp registrations:
Click on the '
New registration' button:
Enter a name (we recommend 'Intruder' or something similar) then click
Register:
Retrieve the Application ID, Application secret key, Directory ID and Subscription ID from Azure
We require four access keys to connect your Azure account to Intruder:
'Application (client) ID' of the Azure application you just created
'Directory (tenant) ID' from Azure Active Directory (also shown on the App Overview page)
'Application secret key' of the Azure application you just created
'Subscription ID' of your Azure subscription.
You need to get them from various sections of the Azure portal, so it's probably best to open a text document that you can copy them into. It should all be straight-forward if you follow the steps below, so hang in there!
Application (client) ID
Click on the 'Intruder' application that we just created
Click 'Overview' and take a note of the
Application (client) ID.
(You'll need this for the 'Application ID' field in the Intruder portal.)
Directory (tenant) ID
You can also get the
Directory (tenant) IDfrom this screen so let's note that one down too.
(You'll need this for the 'Directory ID' field in the Intruder portal.)
Application secret key (in Azure you're looking for the secret 'VALUE')
Now scroll down and click on
Certificates & secretsin the left navigation panelClick on the
New client secretbutton:
Enter a description (e.g. 'Intruder')
Set an expiry date (i.e. how long you want the secret to be valid for).
(⚠️ Please note that Intruder will no longer be able to access your Azure account when the secret expires.)
Now click
Addand note down thesecretVALUE. (Not the Secret ID).
(You'll need this for the 'Application secret key' field in the Intruder portal.)
⚠️ Please note that you won't be able to see that 'Application secret key' again after you've left this screen, so make sure you copy and paste it now!
Subscription ID
Search for
Subscriptionsusing the search functionality and click to see the 'Subscriptions' menu.
Select your subscription from the list of Azure Subscriptions displayed. The following screenshots show the 'Intruder' subscription but yours will likely be specific to your organisation
Take note of your Azure
Subscription ID:
(You'll need this for the 'Subscription ID' field in the Intruder portal)
Create a role
Within your subscription detail page, select '
Access control (IAM)' from the left menuClick
AddThen click
Add role assignment.
A new window will appear.
Type
Readerinto the search boxClick on the
Readeritem in the dropdown. (We require read-only access in order to fetch your public IP addresses and DNS hostnames.)
Click '
Next'
Ensure the
Assign access toproperty is set toUser, group, or service principal:
Click '
Select members', and in the pop up window, search for the application we created earlier (e.g. 'Intruder', or whatever you chose to name it).Choose that application from the list, and click '
Select':
Enter the Application ID, Application secret key, Directory ID and Subscription ID into the Intruder portal
Log into the Intruder portal > Targets page >
Cloud accounts>Add account>Microsoft Azure:
Enter the Application ID, Directory ID, Application secret key and Subscription ID > click '
Add account':
The next thing you'll see is this modal 👇, for automated management of your cloud targets.
If that's not of interest and you'd like to manage them manually, skip the boxes and simply press Confirm setup.
Intruder scans comply with Microsoft's Penetration Testing Rules of Engagement.
Note: Azure integration is only available for customers on our Pro, Premium and Vanguard plans.