Penetration Testing

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

10 hours 37 minutes
Video Transcription
Hey, guys, Welcome to another episode of the S S C P Exam prep. I'm your host, Peter Civility.
This is the fifth lesson in the third do mean
so far in the third domain, we've taken a look at the risk management process. How to determine the rest, Get no organization faces. We've looked at four ways of handling risk properly. We've looked in mourning, but just simply an evaluation off the framework of a security organization.
And we've looked at vulnerability, scanning in analysis,
which is identifying weaknesses that may lie within a system.
Now finally, in today's lesson, we're gonna look at penetration testing.
Penetration. Testing is simply an extension of vulnerability scanning, so it's similar to vulnerability scanning in the sense that we look for weaknesses in the system. But penetration testing goes one step further. We actively exploit these weaknesses, trying to expose other weaknesses.
Let's get started
penetration. Testing simply takes the vulnerability assessment one step for
So in the last lesson, we looked at all of those vulnerabilities and found a whole bunch. From now, we're gonna take that one step further. We're gonna try to actively exploit these vulnerabilities through penetration testing penetration. Testing is good because when you exploit certain vulnerabilities, this can lead to
new vulnerabilities.
Countries. You testing consists of five general phases preparation, information, gathering,
information, evaluation at risk analysis,
active penetration and analysis and reporting.
We'll be looking all these in the coming lesson.
Penetration Testing also has
three different moods. It has the white box moon,
the grey box and the black box
book box testing
White box testing is basically just testers who perform with
the knowledge of the security and I NT staff. So the I T department knows that these guys are coming in and they will be doing different penetration tests on the system. They're also given a lot of the system. Resource is right. There are. They're given, like network blueprints, plan test times
and any type of assistance from the I T department.
Now, this is good and bad. It's good because they have the full cooperation of the organization
and the fixes can occur much, much faster.
And it's good for testing incident response procedures, right? It sees how well you're incident response plan. Um, it's
cons off white box testing. An accurate picture off the network is produced
um the organization is prepared for attack during white box testing, so defenses might be beefed up more than what they normally would be
breadbox testing some information is given to the penetration testing team.
A lot of organizations used his approach when they want the focus to be on accessing the system and not
information discovery. So with the great box testing the penetration testing team, they have some information rather than all of the single information.
Now, this is really great because it is like the best of both worlds between white box testing and black box testing, and really allows for focus testing scenarios, considering they have all the necessary information to do your job properly. But at the same time, they don't have everything too
skewed. The picture of the system
problem of the problems of this testing coverage maybe a little bit limited due to the access level that has been granted since they don't have access to everything, they might not be able to do certain aspects of testing.
Now, I'm sure you realize at this point that black box testers is really just testing that is completely unannounced that nobody knows about on The objective is to whatever they can get into, obviously, without causing harm on black box testing. Usually, only upper management knows they're doing this. Even the like the I T staff
has no idea this is even
going on, and this is great.
I personally like the concept of black box testing simply because it gives
a good look from the organization's true responses. Right It gives it shows with the organization, truly is, and also gives you the point of view from an attacker who's trying to attack from the outside. In
some of cons of this
staff like it, their feelings a little bit hurt, especially if, um,
black box testing guys. They get into quite a lot of things right. They could easily make the ikey staff look bad if they are not up to date on security,
Let's get the penetration Testing
step. One is to define goals for the penetration testing exercise. It's very important to be find a scope here, right? You want to be very specific on what your test that you can't just say, Oh, I'm testing the system
bad. That tells nobody anything. That's a huge scoop. And at that pulling its
country step things almost pointless. And it's going to be very, very costly if you choose to do that.
So you never wanna have a very good scope. You want to know exactly what you'll be testing? Not part of this step is to choose the right penetration tools, those important as setting the goals right. You want to let the environment drives the tools, right? You want to see your environment first, and then you want to pick
penetration testing tools which matched that environment. You do not want to always use certain tools simply because you like those tools and you try to use them for re environment. Some tools are very specific
to the environment in which they work, and so you definitely wanna mac set up as good as possible for best results.
Also, you want to analyze any put off testing results, right? You want to use you wanna set up a graphics one steps ratings or reading vulnerability index whenever possible that when you're actually done tests that you put all the results and have the analysis together, you get a very clear picture of how
adequate or inadequate your system is
step. Number two is the information gathering. You definitely want to know about the network and get re con on any type of information from the organization.
And the other type of information gathering is network mapping, right? You definitely want to.
I had to piece together how the network has been set up and how it works and how the information flows just so you can kind of get a good idea of your organization In general, you can do this through automated software. There's a lot of software
that you confined or you can use, which will give you a really good network mapping picture.
Reconnaissance is definitely needed by a pen tester who has not been granted regular access to a system. So really any kind of pentastar who's doing black box pen testing so infinitely greater access to the system? They need to rely on one thing such a social engineering
and, you know, kind of like low tech reconnaissance.
So in case anyone doesn't know, social engineering is an activity that involves the manipulation of persons to get information
this usually involves, you're talking people wore calling them up and pretending to be something else trying to trick them too, revealing some sort of sensitive information.
They can also acquire information from the website Any type of news articles about the organization you can google around and find things and especially social media specifically linked in
a little more higher mid tech re Kon is using who is or central ops for Is this a system that records Internet registration information? So this gives you information about
D. N s? Usually it's some sort of contact number for someone in the department who the websites registered to that that kind of thing. Also a good way to get the reconnaissance information is D. N s stone transfers, which is really in easy way for D. N s administrators
to move DNA databases to different Dina servers.
So our class directed at D. N s server that asked the server for information of the domain. That service was basically to asking for the Dean s database, right, that could come to you the new Mogo, to find some information based on that
network mapping process that paints a picture of which hosts are up and running.
Now we're mapping, get very deep, very fast. So it was important to kind of limited to the scope off the project. It's also could be considered a precursor to vulnerability testing.
Network mapping techniques include you know, a lot of things like Echo over Quest connects can since gan thin skin you different types of skin, using, um, TCP and network flags. We'll get into TCP on I c M P a little bit later.
But these air just different ways that a person king
figure out which hosts are on and which ones are often kind of get an idea of how the network works.
There's also a bunch of built in operating system commands and network mapping of these things, like, you know, trace route, which shows all the different routers or the different path a packet gooses. It goes a system. You have the ping, which I'm sure most people are familiar with. You have
tell that also and
who is
now. There's also plenty of other available tools, which you can acquire
on. There's a lot of free ones. There's also a lot off what you could pay for, obviously and maths always really good. And then solar winds Super Stan and Lance are also very good tools as well.
So finally we got all the information. We define our project. So this is the risk analysis part we have to figure out based on all the information. We want to figure out what are the most critical on most important things, which we can
formulate risk now salon and find any risks which we can actively exploit. Now we have to be careful with this because there are
certain devices which are mission critical in business. So if we decide to, you know, play around with them a little bit, we could disrupt normal business operations.
Finally, time for the pen testing. We started doing our thing. We start exploiting different vulnerabilities and seeing we could get into a couple of heads up a warning. Always think twice before attempting to exploit a phoner build and may harm the system.
Always think twice. Always, please err on the side of caution. Sometimes it's better to just
say here's a vulnerability that spirit serious and needs to be fixed immediately rather than showing them have serious it is and bringing down the whole says
So Step five. After the penetration testing is done, it's very important that documentation and analysis are reported to management. Always present the problems that things they should be working on but also present solutions. Give them ideas to work on or to implement that in their organization, which
they might not even be aware of. Some of these things
always Taylor to the report to the person looking at it. So as always, usually you people speaking with someone who has very low I t related knowledge and skills. So you always want to use your charts, graphs, summaries, that kind of thing.
In today's lecture, we discussed the five steps of pen testing
with Time
John from ABC. Penetration testing is given the job of testing a system
he is given system documentation notes at a time. What kind of penetration tester would jump be considered
a gray box tester?
Be white box tester,
see black box tester or D social engineering tester.
If you said big white box tester than you are correct, remember, white box testing is when all of the system documentation and notes are given ahead of time so the pen tester can actually focus on the test thing and not so much on the reconnaissance and network mapping.
Thanks for watching guys and really hope you learned a lot in this video and I'll see you next time.
Up Next