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.

Analytics

9/20/2013
09:21 AM
Dark Reading
Dark Reading
Quick Hits
50%
50%

Choosing, Managing, And Evaluating A Penetration Testing Service

The right pen testing service can make your data more secure. The wrong one could introduce risk. Here's how to tell the difference

[The following is excerpted from "Choosing, Managing and Evaluating a Penetration Testing Service," a new report posted this week on Dark Reading's Vulnerability Management Tech Center.]

Hiring a security consulting company to perform penetration testing can make a company more secure by uncovering vulnerabilities in security products and practices -- before the bad guys do. It can also be an extremely confusing and frustrating experience if deliverables don't meet the needs or requirements of the business units. Understanding and properly managing relationships with outsourced security providers can be the difference between an expensive mistake and a well-executed exercise in security risk management.

To establish and maintain an effective relationship with a security consulting firm, one thing is needed above all: communication. Clear, concise and meaningful communication between your organization and your chosen vendor will absolutely affect the level of service and value on the deliverable side of the engagement.

And clear communication requires a firm understanding of the entire process of working with a consulting firm -- from contract to payment and everything in between. Knowing what goes into and influences each of these steps, and having a firm set of reasonable expectations, will go a long way toward ensuring that there are no surprises along the way.

Before any discussion about developing effective relationships with security consultants can take place, it's important to define what "penetration test" really means. You may think you know what a penetration test is, but the definition of the practice and its variables has changed in recent years.

A decade ago, a penetration test was generally a "black box" test that took place at the network level. Security researchers were given no details about the network they had been hired to attack, and, as the attack targeted the network level, the researchers usually attacked ports, services, operating systems and other components that comprise the lower layers of the OSI model. Indeed, the OSI model, antiquated as it may seem, offers a good way to define the scope of a penetration test.

There are several categories of penetration test, and each requires different levels of management and coordination.

1. Black-box testing
Black-box testing is performed by an attacker who has no knowledge of the victim's network technology. While pen testers can certainly still provide this type of testing, the model isn't used as often as it once was because attackers are now sophisticated enough that they will probably know a vast amount about your technology in advance of an attack.

2. White-box testing
White-box testing usually involves close communication and information sharing between your technology group and pen testers. Pen testers are typically supplied with legitimate user accounts, URLs, and even user guides and documentation. This type of penetration test will usually provide the most comprehensive results and is currently the most commonly requested.

3. Gray-box testing
As you might imagine from the name, gray-box testing is a mix of black-box and whitebox testing. With gray-box testing, pen test customers don't hand over the company jewels but do provide testers with some information. This might include credentials or access to a corporate intranet site.

Companies will have other things to consider when determining the scope of the pen test they will undergo. The first is whether to secure services that include social engineering assessment.

When you look at security, one of the biggest risks is people. Indeed, the end user is commonly considered the weakest link in computer security. Most security consultancies will be able to assess the ability of your users to, say, detect phishing schemes, but there are some legal and human resources issues that must be considered before including social engineering as part of your pen testing suite of services.

For detailed recommendations on how to select a pen testing service provider -- and for some advice on ways to evaluate the service you receive -- download the free report.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/3/2020
Pen Testers Who Got Arrested Doing Their Jobs Tell All
Kelly Jackson Higgins, Executive Editor at Dark Reading,  8/5/2020
Browsers to Enforce Shorter Certificate Life Spans: What Businesses Should Know
Kelly Sheridan, Staff Editor, Dark Reading,  7/30/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17366
PUBLISHED: 2020-08-05
An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. It allows remote attackers to bypass intended access restrictions or to cause a denial of service on dependent routing systems by strategically withholding RPKI Route Origin Authorisation ".roa" files or X509 Certificate...
CVE-2020-9036
PUBLISHED: 2020-08-05
Jeedom through 4.0.38 allows XSS.
CVE-2020-15127
PUBLISHED: 2020-08-05
In Contour ( Ingress controller for Kubernetes) before version 1.7.0, a bad actor can shut down all instances of Envoy, essentially killing the entire ingress data plane. GET requests to /shutdown on port 8090 of the Envoy pod initiate Envoy's shutdown procedure. The shutdown procedure includes flip...
CVE-2020-15132
PUBLISHED: 2020-08-05
In Sulu before versions 1.6.35, 2.0.10, and 2.1.1, when the "Forget password" feature on the login screen is used, Sulu asks the user for a username or email address. If the given string is not found, a response with a `400` error code is returned, along with a error message saying that th...
CVE-2020-7298
PUBLISHED: 2020-08-05
Unexpected behavior violation in McAfee Total Protection (MTP) prior to 16.0.R26 allows local users to turn off real time scanning via a specially crafted object making a specific function call.