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.

Threat Intelligence

12:00 PM

Effective Pen Tests Follow These 7 Steps

Third-party pen tests are part of every comprehensive security plan. Here's how to get the most from this mandatory investment.
2 of 8

Decide What You Want

When an organization is getting ready to pay for an outside group to come in for a penetration test, executives might be tempted to answer the question, "What do we want them to test?" with a simple, "Everything, of course!" Giving in to that temptation, though, can be a grave mistake.

Penetration tests should be seen as targeted exercises. That target can, of course, be large: A pen test focusing on the network perimeter, for example, could cover a lot of cyber territory. But that territory wouldn't include the organization's application servers. In order to get the most from a third-party pen test, it's important to start with a clear idea of what you want the pen test to tell you.

Among the questions to ask yourself: Why are you performing the pen test? Is it to answer questions about your security? Is it to check a box for regulators, auditors, or insurance underwriters? Are you trying to find out what went wrong in the most recent breach of your security perimeter? Each of these will have its own set of parameters and processes. And each will return its own set of data and conclusions.

It's critical that you have a clear understanding of the pen test's purpose and that you express that purpose to the pen testers clearly. Make sure they understand what you've told them and that the scope of the test is agreed to by both sides. Once the understanding is reached, put it into writing.

(Image: stockpics VIA Adobe Stock)

2 of 8
Comment  | 
Print  | 
Newest First  |  Oldest First  |  Threaded View
User Rank: Apprentice
9/5/2019 | 3:07:57 PM
Kudos to the aythor (Curtis Franklin Jr.)
Very usefull article - thank you!
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.