WEBVTT

00:01.380 --> 00:08.500
Acquiring permission to conduct network scanning in this video we will talk about some ways you can

00:08.500 --> 00:14.170
get the necessary permission to conduct network scanning in your own corporate environment as well as

00:14.170 --> 00:20.790
client networks will capture our scanning activity to a log file in case we need to cross-reference

00:20.790 --> 00:27.630
it with issues that may occur during our scans and we'll walk through how to acquire permission to scan.

00:27.630 --> 00:35.730
Cloud services such as those hosted on Amazon or a juror as we've seen so far in this course network

00:35.730 --> 00:41.490
scanning can provide great visibility into not only what systems are on our network but the underlying

00:41.490 --> 00:44.280
software and services as well.

00:44.280 --> 00:50.740
However even something as basic as an end maps scan can have unpredictable effects on the target systems.

00:51.930 --> 00:57.960
To give you an example many years ago I was doing a network scan for a manufacturing company and I started

00:57.960 --> 01:01.780
with a basic unmap scan of their production submit.

01:02.000 --> 01:06.770
Midway through that scan suddenly staff all around the building were popping their heads up over their

01:06.770 --> 01:10.960
cubes in a panic as the network seemed to be completely down.

01:11.330 --> 01:16.830
We pinged the core router and indeed it wasn't responding in the logs for the router.

01:16.850 --> 01:22.720
All we could see is that the device rebooted unexpectedly within the time window of my scan.

01:23.750 --> 01:26.570
We guessed that it was the scan that took the router down.

01:26.600 --> 01:31.840
However I didn't have a good time stamped log of when exactly each system was being scanned.

01:32.150 --> 01:34.430
So I couldn't back up that guess.

01:34.550 --> 01:38.260
This experience created two learning opportunities for me.

01:38.390 --> 01:44.990
First I made sure that all future clients were well aware of the possible side effects of network scanning.

01:44.990 --> 01:50.750
I want to make it clear that network scanning while usually hassle free can cause system instability

01:51.110 --> 01:53.210
and even unavailability.

01:53.210 --> 01:58.610
I now have clients read and sign off on these warnings as part of the statement of work so that everybody

01:58.610 --> 02:01.560
is on the same page before the engagement begins.

02:02.270 --> 02:07.850
I also started keeping a log of devices that had been problematic for me in the past so that future

02:07.850 --> 02:14.130
clients could prepare for my scan Accordingly the second learning opportunity that came from the scan

02:14.130 --> 02:19.550
was the need to log all scanned activity so I can cross-reference it later.

02:19.560 --> 02:24.900
Now we're going to learn how to tune and export scans in much greater detail in future videos but at

02:24.900 --> 02:30.630
a high level it's very easy to capture a log of your network scan by simply adding the greater than

02:30.630 --> 02:38.860
sign a space and a file name to the end of your scan what this will do is log all the output to a simple

02:38.860 --> 02:40.860
text file for later reference.

02:41.740 --> 02:47.830
Note that even though I used the verbose output we learned about in our last video the council is not

02:47.890 --> 02:49.150
showing me any output.

02:50.160 --> 02:54.480
That's because everything is being written to the text file and not to the council.

02:55.610 --> 03:02.820
One way we can still watch the scan results live is by opening a new terminal window and then issue

03:02.820 --> 03:07.950
the command tail space TAC f space.

03:07.980 --> 03:09.150
The name of the log file

03:13.840 --> 03:19.360
so that takes care of some gotchas and permissions we want to consider when scanning customer internal

03:19.360 --> 03:20.380
networks.

03:20.680 --> 03:27.310
But what about cloud hosted services they may have such as within the Amazon or as your infrastructure

03:28.660 --> 03:29.050
well.

03:29.050 --> 03:34.630
A quick Google search for Amazon Penn. test will take you to a form that you can fill out to request

03:34.720 --> 03:40.480
Amazon's permission to do a network scan or penetration test against their infrastructure.

03:41.380 --> 03:46.950
A couple of interesting things to note are that first off Amazon will not grant permission to you the

03:46.960 --> 03:47.850
tester.

03:48.430 --> 03:53.940
You must have your client fill the form out and then inform you when permission has been granted.

03:55.260 --> 04:00.870
Also Amazon says that it may take up to two business days to get the form approved but I've seen it

04:00.870 --> 04:04.300
take as long as five days so please plan accordingly.

04:05.820 --> 04:12.660
The form itself is fairly self-explanatory prompting your client to enter contact information as well

04:12.660 --> 04:19.780
as detailed information about the targets in scope for testing the claim will also need to specify source

04:19.780 --> 04:26.980
IPs that your scan traffic will be coming from in-general Amazon is pretty flexible in the kinds of

04:26.980 --> 04:30.210
testing that are conducted against their infrastructure.

04:30.220 --> 04:36.370
However one important note is that they do not allow any testing where the target hosts are overwhelmed

04:36.370 --> 04:37.960
with network traffic.

04:37.960 --> 04:42.370
Typically referred to as protocol flooding or resource request flooding

04:45.520 --> 04:52.310
on the Microsoft as your side the approach is slightly different doing a quick Google search for your

04:52.400 --> 05:01.490
pen test will lead you to this page which tells you that as of June 15th 2017 Microsoft no longer requires

05:01.490 --> 05:04.530
approval ahead of a pen test.

05:04.540 --> 05:10.440
However customers are offered a pin testing notification for I'd recommend filling this out just to

05:10.440 --> 05:15.240
keep all the work you do well well-documented and auditable.

05:15.420 --> 05:22.080
Note that much like Amazon Microsoft frowns upon you engaging in activities that could exhaust resources

05:22.140 --> 05:28.930
on your target's in our next video we will look at different ways to tune our network scans in order

05:28.930 --> 05:35.620
to strike the right balance between speed efficiency and getting the desired information we need from

05:35.620 --> 05:36.320
the scam.
