What is an Internal Pen Test?
This time in our series on the different types of penetration test, we’re covering internal pen tests, otherwise known as 'internal infrastructure' or 'internal network' penetration tests. Hopefully, from our post on external penetration testing you should now have some idea about penetration testing both in general and on the outside of your business, and this post will explain why you might want to take a look on the inside.
What is an internal network penetration test?
Commonly referred to as an 'internal pen test', the internal infrastructure penetration test focuses on testing attacks which could be carried out by an adversary who has already gained a foothold within your network and is looking to 'elevate' themselves to gain further control and cause more damage. It also deals with security holes that could be taken advantage of by a malicious insider — perhaps a disgruntled employee that wishes to cause damage to areas of the business outside of their usual access level.
This type of pen test typically involves tapping into your network on site, so the tester(s) will need to be given access to your office similar to that of an employee. Alternatively, they could start in your cloud infrastructure, depending on the scope of testing and the scenario to be explored. Testers will then attempt to gain access to sensitive information sources or privileged user accounts which should be off-limits to them, finding ways to subvert any access controls you may have in place.
How is internal pen testing carried out?
The process normally starts with a 'discovery phase' where the tester uses network mapping tools to discover the inner workings and layout of your network. Testers will effectively build up a map of your internal network, and the computers and services available on it, and will use this map to guide their efforts to find holes in your security, and to breach areas they shouldn’t be able to access.
After the discovery phase comes the 'identification phase'. Some examples of the sorts of activity that can take place in this phase are as follows:
- Brute forcing of user accounts to attempt to gain unauthorized access to machines on the network
- Subversion of network routers and switches to control and monitor traffic, inject weaknesses or take control of endpoints by exploiting protocols. For example, the Web-Proxy Auto-Discovery protocol, that normally helps computers communicate with the internet can be abused by local attackers to sniff your web traffic
- Exploiting known vulnerabilities in software running locally to break into servers, elevate existing access, or prove attackers could run malicious code
The aim of these types of tests is really to find all possible weaknesses in the shortest space of time. An ordinary infrastructure pen test is therefore usually carried out as an audit-style approach, in collaboration with the security team, and can often be very noisy (in terms of security alerts from any monitoring systems you might have). Although this is a good way to discover the majority of the weaknesses you might have, the downside of this approach is that it may not give you the best understanding of how you might fare when targeted by a real attacker.
You can also learn more about how penetration tests are scoped and quoted.
Penetration testing vs red teaming
For larger and more security-mature businesses, it’s possible to go one step further and conduct what’s called a 'red team' exercise. Tests conducted by a red team aim to mirror techniques a real attacker would use as accurately as possible, including trying to avoid detection. As such, a red team is more of a test of your operational defences, and is often carried out without the knowledge of staff members, including those working in security teams. Red teaming will usually involve other types of attack such as phishing, and can offer a more comprehensive, realistic (and expensive!) coverage.
Standard internal pen tests typically take anything from a few days to a couple of weeks, whereas a full red team engagement would likely take longer, running for over a month or even two for larger firms. Pricing varies hugely based on the scale of the job and the experience of the professionals carrying out the tests.
Automated internal penetration tests
Manual penetration testing can be costly, infrequent, and only give you point-in-time insight into your security posture. It’s also impossible for pen testers to manually check for every vulnerability that exists, as there are simply too many.
Although it’s not possible to fully automate an internal pen test, a tool like Intruder provides continuous vulnerability scanning, as well as proactive Emerging Threat Scans, which is like having an automated penetration tester watching over your systems! Learn more about automated penetration testing and penetration testing tools.
Hopefully this has cleared up some of the questions you may have had regarding internal pen tests. At Intruder, we offer a combination of penetration testing and continuous vulnerability scanning with our automated penetration testing tool. Start your 14 day free trial today.
- Raw CVE Coverage
- Risk Rating Coverage
- Remote Check Types
- Check Publication Lead Time
- Local/Authenticated vs Remote Check Prioritisation
- Software Vendor & Package Coverage
- Headline Vulnerabilities of 2021 Coverage
- Analysis Decisions
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%.
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%.
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%.
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%.
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.
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.
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.
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.