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.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
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
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...