We know that keeping the targets you want to monitor for security weaknesses up to date can be a bit of a pain...
New instances are constantly being spun up in Microsoft Azure, others are being closed down, keeping track of it all can easily become a full time job!
That's why we've created an Azure integration - add your public IP addresses and hostnames from DNS zones as Intruder targets directly from our portal! 🎉
How to connect Azure to your Intruder account
1. Create an application for Intruder in Azure
Login to the Azure management portal
Search for 'App registrations' using the search functionality and click to get to the 'App registrations' menu.
Click on the 'New registration' button.
Enter a name (we recommend 'Intruder' or something similar) then click 'Register'.
2. Get 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
'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) ID' from 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 & secrets' in the left navigation panel
Click on 'New client secret':
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 'Add' and note down the secret 'VALUE'. (Not the Secret ID).
(You'll need this for the 'Application secret key' field in the Intruder portal.)
Important: 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!
Almost there... 😅
Search for 'Subscriptions' using the search functionality and click to see the 'Subscriptions' menu.
Take note of your Azure 'Subscription ID':
(You'll need this for the 'Subscription ID' field in the Intruder portal)
3. Create a role
Select 'Access control (IAM)' from the left menu inside the subscription detail page
Then click 'Add role assignment'.
A new menu will appear on the right of the screen.
Type 'Reader' into the search box
Click on the 'Reader' item in the dropdown. (We require read-only access in order to fetch your public IP addresses and DNS hostnames.)
'Assign access to': Ensure 'Azure AD user, group, or application' is selected
'Select': search for the application we created earlier (e.g. 'Intruder' or whatever you chose to name it). Select that application, and click 'Save'.
4. Enter the Application ID, Application secret key, Directory ID and Subscription ID into the Intruder portal
Log into the Intruder portal
Head to the Targets page
Click 'Add Target'
Select 'Cloud Target sync'.
Enter the Application ID, Application secret key, Directory ID and Subscription ID and click the button to add your Azure account.
Now give yourself a pat on the back because you're done! 💪
Renaming your cloud ID
Just head to your Targets page, hit Settings and then click 'Edit'.
Intruder scans comply with Microsoft's Penetration Testing Rules of Engagement.
Note: Azure integration is only available for customers on our Pro and Vanguard plans.