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)

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!
Sodinokibi Ransomware: Where Attackers' Money Goes
Kelly Sheridan, Staff Editor, Dark Reading,  10/15/2019
Data Privacy Protections for the Most Vulnerable -- Children
Dimitri Sirota, Founder & CEO of BigID,  10/17/2019
State of SMB Insecurity by the Numbers
Ericka Chickowski, Contributing Writer,  10/17/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-11674
PUBLISHED: 2019-10-22
Man-in-the-middle vulnerability in Micro Focus Self Service Password Reset, affecting all versions prior to 4.4.0.4. The vulnerability could exploit invalid certificate validation and may result in a man-in-the-middle attack.
CVE-2019-12967
PUBLISHED: 2019-10-22
Stephan Mooltipass Moolticute through 0.42.1 (and possibly earlier versions) has Incorrect Access Control.
CVE-2019-17189
PUBLISHED: 2019-10-22
totemodata 3.0.0_b936 has XSS via a folder name.
CVE-2019-4523
PUBLISHED: 2019-10-22
IBM DB2 High Performance Unload load for LUW 6.1 and 6.5 is vulnerable to a buffer overflow, caused by improper bounds checking which could allow a local attacker to execute arbitrary code on the system with root privileges. IBM X-Force ID: 165481.
CVE-2019-17424
PUBLISHED: 2019-10-22
A stack-based buffer overflow in the processPrivilage() function in IOS/process-general.c in nipper-ng 0.11.10 allows remote attackers (serving firewall configuration files) to achieve Remote Code Execution or Denial Of Service via a crafted file.