CloudBot keeps a constant watch over your cloud accounts and automatically adds any new external IP addresses or hostnames as Intruder targets.
Why do I need CloudBot?
It's easy to spin up new VMs and containers in AWS, GCP and Azure, but keeping on top of them and ensuring that they're being monitored for weaknesses isn't exactly a walk in the park.
It's for that reason that we built CloudBot; a neat feature that periodically checks your connected cloud accounts for unseen IP addresses or hostnames. When CloudBot spots something new, it automatically adds the system to your targets list – so you don't have to.
Whenever CloudBot adds new targets to your account, we'll send you a Slack and email notification telling you which targets were added.
How do I activate CloudBot?
CloudBot can be individually activated for each cloud account you connect to Intruder (enabling/disabling it for one, will not influence another):
You can activate it when you add the cloud account:
Or at a later date, by heading to the Targets page and following the steps below:
How do I exclude cloud targets?
If there are certain targets in your account that you'd like to exclude from scans, just check the box to the left of the target and hit 'Exclude'.
How do I disable CloudBot?
Head to the Targets page, hit the setting button and toggle to off.
If you disable CloudBot, you can still manually add targets from your cloud accounts via the "Add from Cloud" popup on the targets page.
What if I exceed the licenses in my account?
CloudBot will automatically add new targets until you've reached your license limit. We'll notify you of any targets that CloudBot could not add due to a license deficit. See our licensing help page for more information on how our licensing works.
Note: CloudBot is only available for customers on our Pro and Verified plans.