Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

6/5/2013
11:27 PM
Vincent Liu
Vincent Liu
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

What To Ask Your Penetration Tester

The importance of manual pen testing

Third installment in a series on spotting a novice pen tester

Reviewing the results of a penetration test and discussing methodology is another way to assess the skill level of your pen tester (and the overall quality of the penetration test). What this means is that by asking a few simple questions and evaluating the quality of his or her responses, you can get a good read of his or her abilities. It doesn't mean that if a pen tester fails to break into your system that he or she is a novice. Even the best testers run into targets that are secure.

So start by asking about methodology. What did they do during the penetration test? Zero in on manual testing and how they approached that type of testing. Ask specific questions about what they did for certain exposed services and vulnerability classes. A novice tester is usually highly reliant on the tool for findings, so their answers will usually circle back to the tool. As a general rule, automated tools should make up at most 20 percent (and, in extreme cases, 25 percent) of the time spent during a penetration test. Ask about how a tool was used, but focus more on how they followed-up with manual testing.

When quizzing your pen tester, be sure to differentiate between the act of validating tool results and manual penetration testing. The two are commonly (and mistakenly) used interchangeably.

What you want to know is what types of manual testing were performed beyond eliminating false positives from the report. You really want to know if they attempted to exploit any of the identified issues, which would indicate that they know more than just validation. Conversely, if you find that your reports contain several false positives, there's a good chance that your pen tester doesn't even have the ability to perform the most basic manual validation, so it's very unlikely that he or she was able to perform any manual pen testing.

Don't Fear The Questions
In the population of penetration testers, there exists very skilled and talented assessors, but there also exists an ever greater number of simple tool jockeys who have applied the name of "pen tester" to themselves despite lacking the skill. Then, as the number of unqualified "pen testers" continues to multiply, it becomes all the more important to understand the different levels of pen testers and how to identify them.

Until then, don't be shy about questioning your testers about their results and methodology. They should be clear and open about what they did; if they aren't, then I would recommend reconsidering your choice of assessor.

A hallmark of a better pen tester is the ability to locate and then exploit any identified vulnerabilities. In order to properly and successfully exploit issues, a tester must have a strong understanding of how the vulnerability is manifested, how the environment affects that instance, and how to adapt an attack to properly take advantage of the weakness. The ability to exploit and adapt to each environment is a characteristic of an advanced penetration tester, whose qualities we'll explore in our next installment.

Vincent Liu (CISSP) is a Partner at Bishop Fox, a cyber security consulting firm providing services to the Fortune 500, global financial institutions, and high-tech startups. In this role, he oversees firm management, client matters, and strategy consulting. Vincent is a ... View Full Bio

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 7/6/2020
Ripple20 Threatens Increasingly Connected Medical Devices
Kelly Sheridan, Staff Editor, Dark Reading,  6/30/2020
DDoS Attacks Jump 542% from Q4 2019 to Q1 2020
Dark Reading Staff 6/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15037
PUBLISHED: 2020-07-07
NeDi 1.9C is vulnerable to cross-site scripting (XSS) attack. The application allows an attacker to execute arbitrary JavaScript code via the Reports-Devices.php page st[] parameter.
CVE-2019-4323
PUBLISHED: 2020-07-07
"HCL AppScan Enterprise advisory API documentation is susceptible to clickjacking, which could allow an attacker to embed the contents of untrusted web pages in a frame."
CVE-2019-4324
PUBLISHED: 2020-07-07
"HCL AppScan Enterprise is susceptible to Cross-Site Scripting while importing a specially crafted test policy."
CVE-2020-15036
PUBLISHED: 2020-07-07
NeDi 1.9C is vulnerable to cross-site scripting (XSS) attack. The application allows an attacker to execute arbitrary JavaScript code via the Topology-Linked.php dv parameter.
CVE-2020-15577
PUBLISHED: 2020-07-07
An issue was discovered on Samsung mobile devices with P(9.0) and Q(10.0) software. Cameralyzer allows attackers to write files to the SD card. The Samsung ID is SVE-2020-16830 (July 2020).