0% found this document useful (0 votes)
28 views2 pages

Pen Testing Methods and Reporting Guide

This document provides a summary of different types of penetration testing methods, including black box testing with limited information provided, white box testing where testers are given detailed information, and grey box testing with some initial information. It also discusses preparation, scope definition, testing methodology, and reporting, with the report typically including an executive summary, introduction, methodology, findings, and conclusions sections. Automated testing uses tools to scan for vulnerabilities while manual testing relies on a tester's skills. A hybrid approach combines both.

Uploaded by

lbb1987
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views2 pages

Pen Testing Methods and Reporting Guide

This document provides a summary of different types of penetration testing methods, including black box testing with limited information provided, white box testing where testers are given detailed information, and grey box testing with some initial information. It also discusses preparation, scope definition, testing methodology, and reporting, with the report typically including an executive summary, introduction, methodology, findings, and conclusions sections. Automated testing uses tools to scan for vulnerabilities while manual testing relies on a tester's skills. A hybrid approach combines both.

Uploaded by

lbb1987
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Pen Testing Methods, Prep and Reporting Cheat Sheet

by binca via [Link]/44948/cs/13446/

Black Box Automated Testing

Little or no inform​ation provided to tester other than the name of the Automated tools are used to scan a target for vulner​abi​lities.
target, an IP range or applicable URLs. Many automated scanners are available including HP WebIns​pect,
The target is a "​black box". Trustwave App Scanner, IBM AppScan, ZAP, Burp Suite.

This type of testing requires close coordi​nation between testers and Rapidly scans site but can still take a long time.
target system personnel to ensure that the testing stays within scope. Tester has less control and it is more prone to false positives.
This type of testing is not typically done in web applic​ation testing. Lacks the ability to provide business implic​ations to discovered flaws.

White Box Penetr​ation Testing Hybrid Web App Penetr​ation Testing


Testers are provided with inform​ation in advance including target Combines manual and automated techni​ques.
URLs, applic​ation functi​onality summary, applic​ation map and test
Scanner provide a starting point with manual verifi​cation and exploi​‐
accounts.
tation as follow-up.
Target system personnel are available to answer questions.
As new components of an applic​ation are discovered the process
This type of testing is an integral part of the develo​pment process returns to automated scanning, repeating the cycle.
and as a result it is often performed by an internal team.
Scripting is done as needed.
This is the most frequently used technique for testing.
Grey Box Testing

Testers are provided with some inform​ation at the beginning of


Prepar​ation
testing including URLs and user accounts.
It is the first step, and is contin​uous.
Inform​ation gathering is a critical part of this type of testing.
Practicing and developing skills is paramount.
Commun​ication between the tester and target system personnel is
critical.
Managing a Web App Pen Test
This is the most common type of testing performed today.
Begins BEFORE the hands-on testing, involves the testing team and
the target system personnel.
Manual Testing
Developers can be brought in to help improve security awareness.
Manual testing using scripts and tools
Any vendors or infras​tru​cture providers should be included.
The tester processes each page of the target applic​ation using tools
and script to help manipulate and formulate requests as well as
Establ​ishing the Test Scope
gather and analyze data.
The scope is defined by the purpose of the test. What are the
It is time consuming but allows for the discovery of logic and
concerns associated witht he target applic​ation.
business flaws that tools cannot find.
The type of of test should be agreed upon black, crystal or grey box
Thorou​ghness is dependent on the tester's time, attention and skill
testing.
set.
The scope of the test will define which applic​ations and/or servers
are involved and which should be avoided.

By binca Not published yet. Sponsored by [Link]


[Link]/binca/ Last updated 9th November, 2017. Everyone has a novel in them. Finish
Page 1 of 2. Yours!
[Link]
Pen Testing Methods, Prep and Reporting Cheat Sheet
by binca via [Link]/44948/cs/13446/

Inform​ation Required for Testing Introd​uction

Applic​ations included in the scope Outlines the parts of the test including the scope, objective and the
Multiple user IDs and passwords, each pair having different access. team.

Technology restri​ctions such as client types, ports and servers to This section should be 1-2 pages in length.
avoid
Method​ology
Emergency contact inform​ation.
A step-b​y-step explan​ation of testing including tools used.
Rules of Engagement It should be clear enough that a competent tester could reproduce
Iden​tifying tester traffic and data and verify the test.
Target system personnel should be know source identi​fiers such as This section is often 3-10 pages in length.
IP addresses, email addresses, and other identi​fiers.

Agreeing upon a testing time frame Findings

This includes testing windows and time for analysis, reporting and This is the meat of the report including each finding catego​rized by
follow-up. The delive​rables should be scheduled prior to testing. risk as pertaining to the applic​ation.
Esta​bli​shing commun​ica​tions plans In some cases findings will be divided by applic​ation.
There should be various contacts both technical and manage​ment,
Recomm​end​ations are part of the findings. If there are multiple, each
as well as methods including email, phone, and possibly IM.
should be provided with an explan​ation of the most benefi​cial.
Sensitive inform​ation regarding vulner​abi​lities should be discussed
over secured channels with PGP/GnuPG for email or OTR/en​crypted
Conclu​sions
IM.
This is the final part of the report and is similar to the executive
summary.
Reporting
The audience is the techni​cians, unlike the executive summary which
Probably the most important part of the penetr​ation test, since it is
is geared to higher​-level.
the most lasting portion.
Any appendices are added after the conclusion including
Format:
permission memos
1. Executive Summary
lists of users harvested
2. Introduction
records retrieved from the database
3. Methodology
detailed tool output
4. Findings
5. Conclu​sions
Presen​tation
All inform​ation gathered during testing becomes part of reporting,
An optional part of penetr​ation tests but an excellent way to work
important notes, permis​sions, memos and other items may be
with develo​pers.
included in the append​ices.
Audience should be chosen by target personnel, possibly hold
Executive Summary multiple sessions to focus the presen​tation on different kinds of staff
such as develo​pers, admini​str​ators, management and testing staff.
Contains a high-level overview of our test and findings
The audience is higher​-level personnel.
Maximum 1.5 pages, best kept to a single page.
Contains the findings, including the root cause, and recomm​end​‐
ations, which should be reasonable and accomp​lis​hable. Including
recomm​ended time frames including short-term versus long-term
changes.

By binca Not published yet. Sponsored by [Link]


[Link]/binca/ Last updated 9th November, 2017. Everyone has a novel in them. Finish
Page 2 of 2. Yours!
[Link]

You might also like