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

5/14/2019
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  | 
Comments
Newest First  |  Oldest First  |  Threaded View
theartof
50%
50%
theartof,
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 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
The Yellow Brick Road to Risk Management
Andrew Lowe, Senior Information Security Consultant, TalaTek,  11/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: He hits the gong anytime he sees someone click on an email link.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-29128
PUBLISHED: 2020-11-26
petl before 1.68, in some configurations, allows resolution of entities in an XML document.
CVE-2020-27251
PUBLISHED: 2020-11-26
A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior. This vulnerability could allow a remote, unauthenticated attacker to send malicious port ranges, which could result in remote code execution.
CVE-2020-27253
PUBLISHED: 2020-11-26
A flaw exists in the Ingress/Egress checks routine of FactoryTalk Linx Version 6.11 and prior. This vulnerability could allow a remote, unauthenticated attacker to specifically craft a malicious packet resulting in a denial-of-service condition on the device.
CVE-2020-27255
PUBLISHED: 2020-11-26
A heap overflow vulnerability exists within FactoryTalk Linx Version 6.11 and prior. This vulnerability could allow a remote, unauthenticated attacker to send malicious set attribute requests, which could result in the leaking of sensitive information. This information disclosure could lead to the b...
CVE-2020-25651
PUBLISHED: 2020-11-26
A flaw was found in the SPICE file transfer protocol. File data from the host system can end up in full or in parts in the client connection of an illegitimate local user in the VM system. Active file transfers from other users could also be interrupted, resulting in a denial of service. The highest...