Penetration Testing Tutorial PDF
Penetration Testing Tutorial PDF
Audience
This tutorial has been prepared for beginners to help them understand the basics of
Penetration Testing and how to use it in practice.
Prerequisites
Before proceeding with this tutorial, you should have a basic understanding of software
testing and its related concepts.
All the content and graphics published in this e-book are the property of Tutorials Point (I)
Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish
any contents or a part of contents of this e-book in any manner without written consent
of the publisher.
We strive to update the contents of our website and tutorials as timely and as precisely as
possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt.
Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our
website or its contents including this tutorial. If you discover any errors on our website or
in this tutorial, please notify us at contact@tutorialspoint.com
i
Penetration Testing
Table of Contents
About the Tutorial .................................................................................................................................... i
Audience .................................................................................................................................................. i
Prerequisites ............................................................................................................................................ i
Reconnaissance ....................................................................................................................................... 4
Discovery ................................................................................................................................................ 4
ii
Penetration Testing
iii
Penetration Testing
iv
Penetration Testing
1. Penetration Testing Introduction
If a system is not secured, then any attacker can disrupt or take authorized access to that
system. Security risk is normally an accidental error that occurs while developing and
implementing the software. For example, configuration errors, design errors, and software
bugs, etc.
It identifies a simulation environment i.e., how an intruder may attack the system
through white hat attack.
It helps to find weak areas where an intruder can attack to gain access to the
computers features and data.
It supports to avoid black hat attack and protects the original data.
1
Penetration Testing
Customer Protection: Breach of even a single customers data may cause big
financial damage as well as reputation damage. It protects the organizations who
deal with the customers and keep their data intact.
2
Penetration Testing
2. Penetration Testing Method
Reconnaissance
Discovery
Final analysis
Report Preparation
3
Penetration Testing
The client and the tester jointly define the goals so that both the parties have the same
objectives and understanding. The common objectives of penetration testing are:
To identify the vulnerability and improve the security of the technical systems.
Have IT security confirmed by an external third party.
Increase the security of the organizational/personnel infrastructure.
Reconnaissance
Reconnaissance includes an analysis of the preliminary information. Many times, a tester
doesnt have much information other than the preliminary information, i.e., an IP address
or IP address block. The tester starts by analyzing the available information and, if
required, requests for more information such as system descriptions, network plans, etc.
from the client. This step is the passive penetration test, a sort of. The sole objective is to
obtain a complete and detailed information of the systems.
Discovery
In this step, a penetration tester will most likely use the automated tools to scan target
assets for discovering vulnerabilities. These tools normally have their own databases giving
the details of the latest vulnerabilities. However, tester discovers:
The estimated time required for evaluating potential security flaws for the
subsequent active penetration testing.
However, from the list of identified systems, the tester may choose to test only those
which contain potential vulnerabilities.
4
Penetration Testing
Final Analysis
This step primarily considers all the steps conducted (discussed above) till that time and
an evaluation of the vulnerabilities present in the form of potential risks. Further, the tester
recommends to eliminate the vulnerabilities and risks. Above all, the tester must assure
the transparency of the tests and the vulnerabilities that it disclosed.
Report Preparation
Report preparation must start with overall testing procedures, followed by an analysis of
vulnerabilities and risks. The high risks and critical vulnerabilities must have priorities and
then followed by the lower order.
However, while documenting the final report, the following points needs to be considered:
5
Penetration Testing
3. Penetration Testing Vs. Vulnerability Assessment
Generally, these two terms, i.e., Penetration Testing and Vulnerability assessment are
used interchangeably by many people, either because of misunderstanding or marketing
hype. But, both the terms are different from each other in terms of their objectives and
other means. However, before describing the differences, let us first understand both the
terms one-by one.
Penetration Testing
Penetration testing replicates the actions of an external or/and internal cyber attacker/s
that is intended to break the information security and hack the valuable data or disrupt
the normal functioning of the organization. So, with the help of advanced tools and
techniques, a penetration tester (also known as ethical hacker) makes an effort to control
critical systems and acquire access to sensitive data.
Vulnerability Assessment
On the other hand, a vulnerability assessment is the technique of identifying (discovery)
and measuring security vulnerabilities (scanning) in a given environment. It is a
comprehensive assessment of the information security position (result analysis). Further,
it identifies the potential weaknesses and provides the proper mitigation measures
(remediation) to either remove those weaknesses or reduce below the risk level.
Network
Discovery
Remediation
Vulnerability Vulnerability
Assessment Scanning
Result
Analysis
6
Penetration Testing
The following table illustrates the fundamental differences between penetration testing
and vulnerability assessments:
Vulnerability assessment identifies the weaknesses and gives solution to fix them. On the
other hand, penetration testing only answers the question that can anyone break-in the
system security and if so, then what harm he can do?
As we have seen here, the vulnerability assessment is more beneficial and gives better
result in comparison to penetration testing. But, experts suggest that, as a part of security
management system, both techniques should be performed routinely to ensure a perfect
secured environment.
7
Penetration Testing
4. Types of Penetration Testing
The type of penetration testing normally depends on the scope and the organizational
wants and requirements. This chapter discusses about different types of Penetration
testing. It is also known as Pen Testing.
Black Box
Penetration
Testing
Penetration
Testing
8
Penetration Testing
Tester need not necessarily be an expert, as it does not demand specific language
knowledge.
Test is generally conducted with the perspective of a user, not the designer.
Possibly, it is not worth, incase designer has already conducted a test case.
White box penetration testing examines the code coverage and does data flow testing,
path testing, loop testing, etc.
It ensures that all logical decisions have been verified along with their true and
false value.
It finds the design errors that may have occurred because of the difference between
logical flow of the program and the actual execution.
9
Penetration Testing
As the tester does not require the access of source code, it is non-intrusive and
unbiased.
As there is clear difference between a developer and a tester, so there is least risk
of personal conflict.
You dont need to provide the internal information about the program functions and
other operations.
The response or workflow of the system: This is the third area that needs to
be tested. Social engineering gathers information on human interaction to obtain
information about an organization and its computers. It is beneficial to test the
ability of the respective organization to prevent unauthorized access to its
information systems. Likewise, this test is exclusively designed for the workflow of
the organization/company.
10
Penetration Testing
5. Penetration Testing Manual and Automated
Both manual penetration testing and automated penetration testing are conducted for the
same purpose. The only difference between them is the way they are conducted. As the
name suggests, manual penetration testing is done by human beings (experts of this field)
and automated penetration testing is done by machine itself.
This chapter will help you learn the concept, differences, and applicability of both the
terms.
Data Collection: Data collection plays a key role for testing. One can either collect
data manually or can use tool services (such as webpage source code analysis
technique, etc.) freely available online. These tools help to collect information like
table names, DB versions, database, software, hardware, or even about different
third party plugins, etc.
Actual Exploit: This is a typical method that an expert tester uses to launch an
attack on a target system and likewise, reduces the risk of attack.
Report Preparation: Once the penetration is done, the tester prepares a final
report that describes everything about the system. Finally the report is analyzed to
take corrective steps to protect the target system.
11
Penetration Testing
Vulnerability
Actual Exploit
Assessment
Report
Data Collection
Methods of Preparation
Manual
Penetration
Testing
Tools for automated penetration testing are Nessus, Metasploit, OpenVAs, backtract
(series 5), etc. These are very efficient tools that changed the efficiency and meaning of
penetration testing.
However, the following table illustrates the fundamental difference between the manual
and automated penetration testing:
It requires expert engineer to perform the It is automated so even a learner can run
test. the test.
12
Penetration Testing
13
Penetration Testing
6. Penetration Testing Tools
It is also essential to learn the features of various of tools which are available with
penetration testing. This chapter provides information and insights about these features.
Linux, Windows,
Network Scanning
FreeBSD, OS X, HP-
Nmap Port Scanning UX, NetBSD, Sun, Free
OpenBSD, Solaris,
OS Detection
IRIX, Mac, etc.
Linux, FreeBSD,
Os fingerprinting NetBSD, OpenBSD,
p0f Free
Firewall detection Mac OS X, Solaris,
Windows, and AIX
Remote active OS
fingerprinting
Xprobe Linux Free
Port Scanning
TCP fingerprinting
14
Penetration Testing
Windows Server
2003/2008, Windows 7
Ultimate/ Vista,
GFI Detect network Only Trial
Windows 2000
LANguard vulnerabilities Version Free
Professional,
Business/XP, Sever
2000/2003/2008
Windows 2000
Professional with SP4,
Detect network Windows Server 2003 Only Trial
Iss Scanner
vulnerabilities Standard with SO1, Version Free
Windows XP
Professional with SP1a
15
Penetration Testing
7. Infrastructure Penetration Testing
Computer systems and associated networks normally consist of a large number of devices
and most of them play a major role in conducting total works and businesses of the
respective system. A minor flaw at any point of time, and at any part of these devices may
cause great damage to your business. Therefore, all of them are vulnerable to risk and
need to be secured properly.
Whether hidden on your internal enterprise network or from public view, there is always
a possibility that an attacker can leverage which can harm your infrastructure. So, it is
better to be safe in advance rather than regret later.
External
Wireless Security
Infrastructure
Penetration
Penetration
Types of Testing
Testing
Infrastructure
Penetration
Testing
16
Penetration Testing
In this testing, a tester normally replicates the same kind of attacks that the hackers can
use by finding and mapping the security flaws in your external infrastructure.
There are various benefits of leveraging external infrastructure penetration testing, as it:
Identifies the flaws within the firewall configuration that could be misused
Finds out how information can be leaked out from your system by an attacker
Identifies how an internal attacker could take advantage of even a minor security
flaw.
Identifies the potential business risk and damage that an internal attacker can
inflict.
17
Penetration Testing
Discovers the real risks within the virtual environment and suggests the methods
and costs to fix the threats and flaws.
To provide guidelines and an action plan on how to protect from the external
threats.
18
Penetration Testing
8. Penetration Testers
There is the issue of protecting the most critical data of the organization; therefore, the
role of a penetration tester is much critical, a minor error can put both the parties (tester
and his client) on risk.
Therefore, this chapter discusses various aspects of a penetration tester including his
qualification, experience, and responsibilities.
Either qualified internal expert or a qualified external expert may perform the penetration
test until they are organizationally independent. It means that the penetration tester must
be organizationally independent from the management of the target systems. For
example, if a third-party company is involved in the installation, maintenance, or support
of target systems, then that party cannot perform penetration testing.
Here are some guidelines that will help you while calling a penetration tester.
Certification
A certified person can perform penetration testing. Certification held by the tester is the
indication of his skill sets and competence of capable penetration tester.
Past Experience
The following questions will help you to hire an effective penetration tester:
19
Penetration Testing
What type of experience does the penetration tester has? For example, conducting
network-layer penetration testing etc.
You may also ask for the reference from other customers for whom he worked.
When hiring a penetration tester, it is important to evaluate the past year testing
experience of the organization for which he (tester) has worked as it is related to the
technologies specifically deployed by him within the target environment.
In addition to the above, for complex situations and typical client requirements, it is
recommended to evaluate a testers capability to handle similar environment in his/her
earlier project.
20
Penetration Testing
9. Report Writing
It is not necessary that an experienced penetration tester can write a good report, as
writing report of penetration testing is an art that needs to be learnt separately.
Report Planning
Information Collection
Writing the First Draft
Review and Finalization
Report Planning
Report planning starts with the objectives, which help readers to understand the main
points of the penetration testing. This part describes why the testing is conducted, what
are the benefits of pen testing, etc. Secondly, report planning also includes the time taken
for the testing.
21
Penetration Testing
Time: Inclusion of time is very important, as it gives the accurate status of the
system. Suppose, if anything wrong happens later, this report will save the tester,
as the report will illustrate the risks and vulnerabilities in the penetration testing
scope during the specific period of time.
Target Audience: Pen testing report also needs to include target audience, such
as information security manager, information technology manager, chief
information security officer, and technical team.
Information Collection
Because of the complicated and lengthy processes, pen tester is required to mention every
step to make sure that he collected all the information in all the stages of testing. Along
with the methods, he also needs to mention about the systems and tools, scanning results,
vulnerability assessments, details of his findings, etc.
22
Penetration Testing
Executive Summary
Scope of work
Project objectives
Assumption
Timeline
Summary of findings
Summary of recommendation
Methodology
Planning
Exploitation
Reporting
Detail Findings
Detailed systems information
Windows server information
References
Appendix
23
Penetration Testing
10. Ethical Hacking
The fast growth of the internet has changed the way of life for everyone. These days, most
of the private and public works are internet dependent. Governments all secret working
plans, and operations are internet based. All these things made the life very simple and
easily accessible.
But with the good news, there is also a dark face of this development i.e., the criminal
hacker. There is no geopolitical limitation of these criminal hackers, they can hack any
system from any part of the world. They can damage confidential data and credit history
very badly.
Therefore, to protect from the criminal hackers, the concept of the ethical hacker evolved.
This chapter discusses the concept and the role of an ethical hacker.
24
Penetration Testing
And, here is the screenshot of the same webpage after it was hacked:
25
Penetration Testing
Whatever the risks and vulnerabilities, they discover while testing the system, they
have to keep them confidential.
They should have good analytical skills to analyze the situation and speculate the
risk in advance.
They should have the management skill along with patience, as pen testing can
take one day, one week, or even more.
What are the weak points that a criminal hacker can hit?
Moreover, an ethical hacker is required to address adequately the vulnerabilities and risks,
which he found to exist in the target system(s). He needs to explain and suggest the
avoidance procedures. Finally, prepare a final report of his all ethical activities that he did
and observed while performing penetration testing.
Types of Hackers
Hackers are normally divided into three categories.
26
Penetration Testing
27
Penetration Testing
11. Penetration Testing Vs. Ethical Hacking
Penetration testing is very closely related to ethical hacking, so these two terms are often
used interchangeably. However there is a thin line of difference between these two terms.
This chapter provides insights into some basic concepts and fundamental differences
between penetration testing and ethical hacking.
Penetration Testing
Penetration testing is a specific term and focuses only on discovering the vulnerabilities,
risks, and target environment with the purpose of securing and taking control of the
system. Or in other words, penetration testing targets respective organizations defense
systems consisting of all computer systems and its infrastructure.
Ethical Hacking
On the other hand, ethical hacking is an extensive term that covers all hacking techniques,
and other associated computer attack techniques. So, along with discovering the security
flaws and vulnerabilities, and ensuring the security of the target system, it is beyond
hacking the system but with a permission in order to safeguard the security for future
purpose. Hence, we can that, it is an umbrella term and penetration testing is one of the
features of ethical hacking.
The following are the major differences between Penetration testing and Ethical hacking
which is listed in the following table:
Paper work in less compared to Ethical A detailed paper works are required,
hacking. including legal agreement etc.
To perform this type of testing, less time Ethical hacking involves lot of time and
required. effort compared to Penetration testing.
28
Penetration Testing
Since penetration techniques are used to protect from threats, the potential attackers are
also swiftly becoming more and more sophisticated and inventing new weak points in the
current applications. Hence, a particular sort of single penetration testing is not sufficient
to protect your security of the tested systems.
As per the report, in some cases, a new security loophole is discovered and successful
attack took place immediately after the penetration testing. However, it does not mean
that the penetration testing is useless. It only means that, this is true that with thorough
penetration testing, there is no guarantee that a successful attack will not take place, but
definitely, the test will substantially reduce the possibility of a successful attack.
29
Penetration Testing
12. Penetration Testing Limitations
Because of the swift pace of developments in the field of information and technology, the
success story of penetration testing is comparatively short-lived. As more protection to
the systems is required, more often than you need to perform penetration testing in order
to diminish the possibility of a successful attack to the level that is appreciated by the
company.
Limitation of Time: As all of us know, penetration testing is not at all time bound
exercise; nevertheless, experts of penetration testing have allotted a fixed amount
of time for each test. On the other hand, attackers have no time constrains, they
plan it in a week, month, or even years.
Limitation on Access: More often testers have restricted access to the target
environment. For example, if a company has carried out the penetration test
against its DMZ systems from all across its internet networks, but what if the
attackers attack through the normal internet gateway.
Limitation of Methods: There are chances that the target system can crash
during a penetration test, so some of the particular attack methods would likely be
turned off the table for a professional penetration tester. For example, producing a
denial of service flood to divert a system or network administrator from another
attack method, usually an ideal tactic for a really bad guy, but it is likely to fall
outside of the rules of engagement for most of the professional penetration testers.
Limitation of Known Exploits: Many of the testers are aware with only those
exploits, which are public. In fact, their imaginative power is not as developed as
attackers. Attackers normally think much beyond a testers thinking and discover
the flaw to attack.
Limitation to Experiment: Most of the testers are time bound and follow the
instructions already given to them by their organization or seniors. They do not try
something new. They do not think beyond the given instructions. On the other
hand, attackers are free to think, to experiment, and to create some new path to
attack.
30
Penetration Testing
Moreover, penetration testing can neither replace the routine IT security tests, nor it can
substitute a general security policy, but rather, penetration testing supplements the
established review procedures and discovers new threats.
31
Penetration Testing
13. Penetration Testing Remediation
Penetration testing efforts however thorough they may be cannot always ensure an
exhaustive discovery of every instance where a security controls effectiveness is
insufficient. Identifying a cross-site scripting vulnerability or risk in one area of an
application may not definitely expose all instances of this vulnerability present in the
application. This chapter illustrates the concept and utility of remediation.
What is Remediation?
Remediation is an act of offering an improvement to replace a mistake and set it right.
Often the presence of vulnerability in one area may indicate weakness in process or
development practices that could have replicated or enabled similar vulnerability in other
locations. Therefore, while remediating, it is important for the tester to carefully
investigate the tested entity or applications with ineffective security controls in mind.
Because of these reasons, the respective company should take steps to remediate any
exploitable vulnerability within a reasonable period of time after the original penetration
test. In fact, as soon as the company has completed these steps, the pen tester should
perform a retest to validate the newly implemented controls which are capable to mitigate
the original risk.
The remediation efforts extending for a longer period after the initial pen test possibly
require performing a new testing engagement to ensure accurate results of the most
current environment. This determination should be made after a risk analysis of how much
change has occurred since the original testing was completed.
Moreover, in specific conditions, the flagged security problem may illustrate a basic flaw
in respective environment or application. Therefore, the scope of a retest should consider
whether any changes caused by remediation identified from the test are classified as
significant. All changes should be retested; however, whether an entire system retest is
necessary or not will be determined by the risk assessment of the changes.
32
Penetration Testing
14. Penetration Testing Legal Issues
Before allowing someone to test sensitive data, companies normally take measures
regarding the availability, confidentiality, and integrity of data. For this agreement to be
in place, legal compliance is a necessary activity for an organization.
The most important legal regulations which have to be observed when establishing and
maintaining security and authorization systems are presented below in context for using
in implementing penetration tests.
The tester is unknown to his client so, on what ground, he should be given access
of sensitive data.
The client may blame for the loss of data or confidentiality to tester
Penetration testing may affect system performance, and can raise confidentiality and
integrity issues; therefore, this is very important, even in an internal penetration testing,
which is performed by an internal staff to get permission in writing. There should be a
written agreement between a tester and the company/organization/individual to clarify all
the points regarding the data security, disclosure, etc. before commencing testing.
A statement of intent should be drawn up and duly signed by both the parties prior to
any testing work. It should be clearly outlined that the scope of the job and that, you may
and may not be doing while performing vulnerability tests.
For the tester, it is important to know who owns the business or systems which are being
requested to work on, and the infrastructure between testing systems and their targets
that may be potentially affected by pen testing. The idea is to make sure;
the tester has the permission in writing, with clearly defined parameters.
the company has the details of its pen tester and an assurance that he would not
leak any confidential data.
A legal agreement is beneficial for both the parties. Remember, regulations change from
country to country, so keep yourself abreast with the laws of your respective country. Sign
an agreement only after considering the respective laws.
33