What's new? Product updates from Intruder April 2024
Author
Andy Hornegold
•
VP of Product
Updated
May 1, 2024
|
Published
May 1, 2024
|
min read
Key Points
Check out what's new at Intruder in Q2 2024 including scanning single page apps (SPAs), improved cloud connections, and more! Watch our video for the latest updates from VP of Product, Andy Hornegold.
We improved our existing AWS integration, giving you the ability to add AWS accounts at the organization level, rather than having to do it individually. It makes things easier, saves you time, and increases your cloud coverage. You won't have to worry about any missing targets in your attack surface, as cloud assets in AWS are synced and added as targets in Intruder automatically.
This update applies to customers on our premium plan. Curious about premium? Speak to the team and get a trial of premium today.
In addition to our work on our AWS integration, we now automatically identify AWS targets that need an API schema. Whenever you add a target from AWS (or when we pull one in automatically), we’ll analyze it to see if an API is present. If it is, we'll prompt you to add a schema to your target, meaning you get better coverage and find more issues.
Automatically Discover Login Pages
We now scan your targets for the presence of a login page. If we find one, we prompt you to add an authentication to that target. Adding authentications to targets with login pages allows us to run additional checks, find more issues, and ensure your web apps are more secure. Want to learn more? Read all about the update here.
What's next on the roadmap?
In Q2, we will be focusing heavily on Attack Surface Management. Before we dive into what features we're going to build, lets talk about what Attack Surface Management means to us.
What do we mean by Attack Surface Management?
Discovering your assets and services
Understanding what you own and what's exposed
Minimizing exposure by patching current vulnerabilities and fixing misconfigurations & exposed services.
Want to learn the difference between Vulnerability Management and Attack Surface Management? Read our blog where we explain it in detail.
Expanding Attack Surface Management in Q2
Here is what we are building to help you protect your attack surface:
Attack surface discovery: Find all your subdomains exposed to the internet with subdomain enumeration.
Attack surface visibility: Get a complete picture of your attack surface in one, searchable place.
Attack surface issue detection: Discover more vulnerabilities, with 1000+ additional checks.
Cloud integration prompt: Automatically find new assets in your cloud environment on an ongoing basis.
More features!
We're not just working on our attack surface management offering this quarter. We're also adding to our overall feature set:
Automatically detect when a target is being blocked by a web application firewall (WAF) so you can ensure your targets are being fully scanned
Empower your team with the ability to manage their own scans
Make sure you don't miss out on any of these features by registering for our next addition of Office House with Intruder
Got some ideas?
Are you an existing customer or on a trial with us and have something you want us to add to the roadmap? Submit a feature request here.
Andy has a long career in cyber security including a decade in threat simulation and consulting. Career highlights include being the Assurance Regional Lead at one of the UK's leading cyber security consultancies and helping critical national infrastructure providers stay secure. Most recently, Andy was the EU Red Team Operations Lead at Mandiant, building out and leading the security team to deliver high quality intelligence-led threat simulations.
Get a Free PDF Guide to Vulnerability Scanning: Learn How to Start with Vulnerability Scanning, Different Types of Scanners Available, and Vulnerability Scanning Best Practices
Oops! Something went wrong while submitting the form.
We're committed to your privacy. Intruder may contact you in the future about our relevant products or services. By submitting your details, you agree to our Privacy Policy.
What's new? Product updates from Intruder April 2024
Andy Hornegold
May 1, 2024
Check out what's new at Intruder in Q2 2024 including scanning single page apps (SPAs), improved cloud connections, and more! Watch our video for the latest updates from VP of Product, Andy Hornegold.
We improved our existing AWS integration, giving you the ability to add AWS accounts at the organization level, rather than having to do it individually. It makes things easier, saves you time, and increases your cloud coverage. You won't have to worry about any missing targets in your attack surface, as cloud assets in AWS are synced and added as targets in Intruder automatically.
This update applies to customers on our premium plan. Curious about premium? Speak to the team and get a trial of premium today.
In addition to our work on our AWS integration, we now automatically identify AWS targets that need an API schema. Whenever you add a target from AWS (or when we pull one in automatically), we’ll analyze it to see if an API is present. If it is, we'll prompt you to add a schema to your target, meaning you get better coverage and find more issues.
Automatically Discover Login Pages
We now scan your targets for the presence of a login page. If we find one, we prompt you to add an authentication to that target. Adding authentications to targets with login pages allows us to run additional checks, find more issues, and ensure your web apps are more secure. Want to learn more? Read all about the update here.
What's next on the roadmap?
In Q2, we will be focusing heavily on Attack Surface Management. Before we dive into what features we're going to build, lets talk about what Attack Surface Management means to us.
What do we mean by Attack Surface Management?
Discovering your assets and services
Understanding what you own and what's exposed
Minimizing exposure by patching current vulnerabilities and fixing misconfigurations & exposed services.
Want to learn the difference between Vulnerability Management and Attack Surface Management? Read our blog where we explain it in detail.
Expanding Attack Surface Management in Q2
Here is what we are building to help you protect your attack surface:
Attack surface discovery: Find all your subdomains exposed to the internet with subdomain enumeration.
Attack surface visibility: Get a complete picture of your attack surface in one, searchable place.
Attack surface issue detection: Discover more vulnerabilities, with 1000+ additional checks.
Cloud integration prompt: Automatically find new assets in your cloud environment on an ongoing basis.
More features!
We're not just working on our attack surface management offering this quarter. We're also adding to our overall feature set:
Automatically detect when a target is being blocked by a web application firewall (WAF) so you can ensure your targets are being fully scanned
Empower your team with the ability to manage their own scans
Make sure you don't miss out on any of these features by registering for our next addition of Office House with Intruder
Got some ideas?
Are you an existing customer or on a trial with us and have something you want us to add to the roadmap? Submit a feature request here.
Limited public information is available about the vulnerability.
Red teamers, security researchers, detection engineers, threat actors have to actively research type of vulnerability, location in vulnerable software and build an associated exploit.
Tenable release checks for 47.43% of the CVEs they cover in this window, and Greenbone release 32.96%.
Day of CVE publish
😊
Vulnerability information is publicly accessible.
Red teamers, security researchers, detection engineers and threat actors now have access to some of the information they were previously having to hunt themselves, speeding up potential exploit creation.
Tenable release checks for 17.12% of the CVEs they cover in this window, and Greenbone release 17.69%.
First week since CVE publish
😐
Vulnerability information has been publicly available for up to 1 week.
The likelihood that exploitation in the wild is going to be happening is steadily increasing.
Tenable release checks for 10.9% of the CVEs they cover in this window, and Greenbone release 20.69%.
Between 1 week and 1 month since CVE publish
🥺
Vulnerability information has been publicly available for up to 1 month, and some very clever people have had time to craft an exploit.
We’re starting to lose some of the benefit of rapid, automated vulnerability detection.
Tenable release checks for 9.58% of the CVEs they cover in this window, and Greenbone release 12.43%.
After 1 month since CVE publish
😨
Information has been publicly available for more than 31 days.
Any detection released a month after the details are publicly available is decreasing in value for me.
Tenable release checks for 14.97% of the CVEs they cover over a month after the CVE details have been published, and Greenbone release 16.23%.
With this information in mind, I wanted to check what is the delay for both Tenable and Greenbone to release a detection for their scanners. The following section will focus on vulnerabilities which:
Have CVSSv2 rating of 10
Are exploitable over the network
Require no user interaction
These are the ones where an attacker can point their exploit code at your vulnerable system and gain unauthorised access.
We’ve seen previously that Tenable have remote checks for 643 critical vulnerabilities, and OpenVAS have remote checks for 450 critical vulnerabilities. Tenable release remote checks for critical vulnerabilities within 1 month of the details being made public 58.4% of the time, but Greenbone release their checks within 1 month 76.8% of the time. So, even though OpenVAS has fewer checks for those critical vulnerabilities, you are more likely to get them within 1 month of the details being made public. Let’s break that down further.
In Figure 10 we can see the absolute number of remote checks released on a given day after a CVE for a critical vulnerability has been published. What you can immediately see is that both Tenable and OpenVAS release the majority of their checks on or before the CVE details are made public; Tenable have released checks for 247 CVEs, and OpenVAS have released checks for 144 CVEs. Then since 2010 Tenable have remote released checks for 147 critical CVEs and OpenVAS 79 critical CVEs on the same day as the vulnerability details were published. The number of vulnerabilities then drops off across the first week and drops further after 1 week, as we would hope for in an efficient time-to-release scenario.
Figure 10: Absolute numbers of critical CVEs with a remote check release date from the date a CVE is published
While raw numbers are good, Tenable have a larger number of checks available so it could be unfair to go on raw numbers alone. It’s potentially more important to understand the likelihood that OpenVAS or Tenable will release a check of a vulnerability on any given day after a CVE for a critical vulnerability is released. In Figure 11 we can see that Tenable release 61% their checks on or before the date that a CVE is published, and OpenVAS release a shade under 50% of their checks on or before the day that a CVE is published.
Figure 11: Percentage chance of delay for critical vulnerabilities
So, since 2010 Tenable has more frequently released their checks before or on the same day as the CVE details have been published for critical vulnerabilities. While Tenable is leading at this point, Greenbone’s community feed still gets a considerable percentage of their checks out on or before day 0.
I thought I’d go another step further and try and see if I could identify any trend in each organisations release delay, are they getting better year-on-year or are their releases getting later? In Figure 12 I’ve taken the mean delay for critical vulnerabilities per year and plotted them. The mean as a metric is particularly influenced by outliers in a data set, so I expected some wackiness and limited the mean to only checks released 180 days prior to a CVE being published and 31 days after a CVE being published. These seem to me like reasonable limits, as anything greater than 6 months prior to CVE details being released is potentially a quirk of the check details and anything after a 1-month delay is less important for us.
What can we take away from Figure 12?
We can see that between 2011 and 2014 Greenbone’s release delay was better than that of Tenable, by between 5 and 10 days.
In 2015 things reverse and for 3 years Tenable is considerably ahead of Greenbone by a matter of weeks.
But, then in 2019 things get much closer and Greenbone seem to be releasing on average about a day earlier than Tenable.
For both the trendline over an 11-year period is very close, with Tenable marginally beating Greenbone.
We have yet to have any data for 2021 for OpenVAS checks for critical show-stopper CVEs.
Figure 12: Release delay year-on-year (lower is better)
With the larger number of checks, and still being able to release a greater percentage of their remote checks for critical vulnerabilities Tenable could win this category. However, the delay time from 2019 and 2020 going to OpenVAS, and the trend lines being so close, I am going to declare this one a tie. It’s a tie.
The takeaway from this is that both vendors are getting their checks out the majority of the time either before the CVE details are published or on the day the details are published. This is overwhelmingly positive for both scanning solutions. Over time both also appear to be releasing remote checks for critical vulnerabilities more quickly.
Get Our Free "Ultimate Guide to Vulnerability Scanning"
Learn everything you need to get started with vulnerability scanning and how to get the most out of your chosen product with our free PDF guide.
.jpg)
