WEBVTT

00:00:00.000 --> 00:00:09.870 align:middle line:90%


00:00:09.870 --> 00:00:12.690 align:middle line:84%
To better understand where your
customer, where the company is

00:00:12.690 --> 00:00:16.350 align:middle line:84%
coming from, let's actually
dive into what audits look like

00:00:16.350 --> 00:00:17.220 align:middle line:90%
and what they do.

00:00:17.220 --> 00:00:19.840 align:middle line:90%


00:00:19.840 --> 00:00:23.290 align:middle line:84%
So a company may be doing
an audit for compliance.

00:00:23.290 --> 00:00:25.870 align:middle line:84%
They want to take
credit card information

00:00:25.870 --> 00:00:28.150 align:middle line:84%
and so they have to
be in compliance.

00:00:28.150 --> 00:00:31.940 align:middle line:84%
Perhaps they're working
with the US government

00:00:31.940 --> 00:00:33.880 align:middle line:84%
and they have to be
in compliance there.

00:00:33.880 --> 00:00:36.860 align:middle line:84%
Or maybe a company just wants
to do their due diligence.

00:00:36.860 --> 00:00:39.580 align:middle line:84%
Maybe they're not compelled
by any regulation,

00:00:39.580 --> 00:00:43.648 align:middle line:84%
but they just want to be
secure because they have--

00:00:43.648 --> 00:00:45.580 align:middle line:84%
they feel that they
need to provide that

00:00:45.580 --> 00:00:48.640 align:middle line:84%
to themselves and
to their customers.

00:00:48.640 --> 00:00:54.187 align:middle line:84%
Well, auditing is the way that
a company can check and see

00:00:54.187 --> 00:00:56.020 align:middle line:84%
whether they, themselves,
are in compliance.

00:00:56.020 --> 00:00:58.900 align:middle line:84%
Or a third party can
come in and run an audit

00:00:58.900 --> 00:01:03.640 align:middle line:84%
to see if they are
following the guidelines.

00:01:03.640 --> 00:01:05.890 align:middle line:90%
It can start with interviews.

00:01:05.890 --> 00:01:10.510 align:middle line:84%
Interviewing your CISO,
your system admins,

00:01:10.510 --> 00:01:14.740 align:middle line:84%
whoever is touching,
creating, using information

00:01:14.740 --> 00:01:20.860 align:middle line:84%
that is included, they could all
be brought in for interviews.

00:01:20.860 --> 00:01:24.220 align:middle line:84%
Were-- maybe your workers,
they could be asked,

00:01:24.220 --> 00:01:28.150 align:middle line:84%
were you given any security
awareness training this year?

00:01:28.150 --> 00:01:29.560 align:middle line:84%
What practices do
you know about?

00:01:29.560 --> 00:01:31.480 align:middle line:84%
What practices are
you forced into?

00:01:31.480 --> 00:01:33.520 align:middle line:90%
Can you plug in USBs?

00:01:33.520 --> 00:01:37.510 align:middle line:84%
Do you have access to the
building via some sort

00:01:37.510 --> 00:01:39.040 align:middle line:90%
of multi-factor authentication?

00:01:39.040 --> 00:01:41.260 align:middle line:84%
Do you have access to
your machine via some sort

00:01:41.260 --> 00:01:43.300 align:middle line:90%
of multi-factor authentication?

00:01:43.300 --> 00:01:48.220 align:middle line:84%
By doing interviews, they don't
just get one person's view

00:01:48.220 --> 00:01:48.850 align:middle line:90%
on things.

00:01:48.850 --> 00:01:50.980 align:middle line:84%
They get the full
scope, picture,

00:01:50.980 --> 00:01:55.880 align:middle line:90%
of the whole environment.

00:01:55.880 --> 00:01:58.160 align:middle line:84%
Often, there's
review of paperwork.

00:01:58.160 --> 00:01:59.990 align:middle line:84%
So a lot of
compliance is you have

00:01:59.990 --> 00:02:01.950 align:middle line:84%
to keep these
records in this way

00:02:01.950 --> 00:02:04.580 align:middle line:84%
and going back
and reviewing, OK,

00:02:04.580 --> 00:02:06.560 align:middle line:84%
if you've got a
policy that you have

00:02:06.560 --> 00:02:10.250 align:middle line:84%
to do exit interviews for
every new employee and maybe

00:02:10.250 --> 00:02:13.590 align:middle line:84%
at a certain date before
they leave you do this, that,

00:02:13.590 --> 00:02:16.550 align:middle line:84%
and the other to pull
their credentials

00:02:16.550 --> 00:02:21.570 align:middle line:84%
and prevent loss of data, how
do you keep records of those?

00:02:21.570 --> 00:02:24.780 align:middle line:84%
Can you show me logs of
having done this in the past?

00:02:24.780 --> 00:02:30.660 align:middle line:84%
So a review of paperwork,
or records, is quite useful.

00:02:30.660 --> 00:02:32.760 align:middle line:84%
Then there's some tools
that are automated.

00:02:32.760 --> 00:02:35.580 align:middle line:84%
So there are some
technical controls

00:02:35.580 --> 00:02:36.790 align:middle line:90%
that need to be in place.

00:02:36.790 --> 00:02:40.110 align:middle line:84%
Maybe it's firewalls,
antivirus, different rules

00:02:40.110 --> 00:02:41.880 align:middle line:84%
on your machines or
different software

00:02:41.880 --> 00:02:45.180 align:middle line:84%
that's required to be
installed to be in compliance.

00:02:45.180 --> 00:02:47.370 align:middle line:84%
And those can be
checked fairly simply

00:02:47.370 --> 00:02:52.500 align:middle line:84%
with tools like a Nessus scan
or SolarWinds auditing tools.

00:02:52.500 --> 00:02:55.020 align:middle line:84%
And they can give
you a good picture

00:02:55.020 --> 00:02:57.570 align:middle line:84%
of what the organization
already looks like.

00:02:57.570 --> 00:03:00.660 align:middle line:84%
As a pen tester, you can
utilize some of these tools.

00:03:00.660 --> 00:03:03.150 align:middle line:84%
They can be a great way
to find vulnerabilities.

00:03:03.150 --> 00:03:05.310 align:middle line:90%
A lot of that is often baked in.

00:03:05.310 --> 00:03:08.910 align:middle line:84%
Sometimes you can find
vulnerabilities and just

00:03:08.910 --> 00:03:15.060 align:middle line:84%
weaknesses that they think
they've already taken care of,

00:03:15.060 --> 00:03:18.750 align:middle line:84%
but maybe they haven't actually
mitigated or even addressed

00:03:18.750 --> 00:03:20.370 align:middle line:90%
some of their vulnerabilities.

00:03:20.370 --> 00:03:27.360 align:middle line:84%
If you have the ability to run a
Nessus scan on a victim system,

00:03:27.360 --> 00:03:29.880 align:middle line:84%
on a network that
you are auditing

00:03:29.880 --> 00:03:32.640 align:middle line:84%
and that you're pen
testing, then you

00:03:32.640 --> 00:03:37.160 align:middle line:84%
can get back quite a lot
of useful information.

00:03:37.160 --> 00:03:39.230 align:middle line:84%
As a pen tester,
if you were doing

00:03:39.230 --> 00:03:46.340 align:middle line:84%
an audit, or an
assessment, a pen test,

00:03:46.340 --> 00:03:48.430 align:middle line:84%
whatever way you were
working with the company,

00:03:48.430 --> 00:03:50.350 align:middle line:84%
you need to take
some good notes.

00:03:50.350 --> 00:03:54.760 align:middle line:84%
There are many different tools
and ways of taking good notes.

00:03:54.760 --> 00:03:58.120 align:middle line:84%
Joplin has some
auto-archiving functionality.

00:03:58.120 --> 00:04:01.270 align:middle line:84%
Sublime Text, depending-- you
can put things in markdown.

00:04:01.270 --> 00:04:02.830 align:middle line:90%
You can put them in plain text.

00:04:02.830 --> 00:04:05.500 align:middle line:84%
OneNote is often
a very useful tool

00:04:05.500 --> 00:04:08.860 align:middle line:84%
because you can collaborate
with other members of your team

00:04:08.860 --> 00:04:14.230 align:middle line:84%
or ship things into a useful
format for your report.

00:04:14.230 --> 00:04:16.029 align:middle line:84%
It allows for--
all of these allow

00:04:16.029 --> 00:04:19.029 align:middle line:84%
for different sorts of
structuring so that you can

00:04:19.029 --> 00:04:21.070 align:middle line:84%
take the information
that you gather

00:04:21.070 --> 00:04:23.230 align:middle line:84%
doing your pen
test or your audit

00:04:23.230 --> 00:04:27.380 align:middle line:84%
and making a useful
report in the end.

00:04:27.380 --> 00:04:29.860 align:middle line:84%
Another useful way of
sharing information

00:04:29.860 --> 00:04:32.980 align:middle line:84%
at the end of your
report is a mind map,

00:04:32.980 --> 00:04:35.650 align:middle line:84%
putting useful information
together in such a way

00:04:35.650 --> 00:04:38.350 align:middle line:84%
that it flows and is
followable by your customer.

00:04:38.350 --> 00:04:41.360 align:middle line:90%


00:04:41.360 --> 00:04:44.120 align:middle line:90%
Reports are crucial.

00:04:44.120 --> 00:04:46.460 align:middle line:84%
You're not getting
paid for your pen test.

00:04:46.460 --> 00:04:49.190 align:middle line:84%
You're getting paid
for your report that

00:04:49.190 --> 00:04:50.600 align:middle line:90%
goes with your pen test.

00:04:50.600 --> 00:04:53.000 align:middle line:84%
That might be something
new to think about.

00:04:53.000 --> 00:04:55.580 align:middle line:84%
A lot of training around
penetration testing

00:04:55.580 --> 00:05:00.470 align:middle line:84%
focuses on scans and
vulnerabilities, zero days

00:05:00.470 --> 00:05:01.910 align:middle line:90%
and exploits.

00:05:01.910 --> 00:05:05.300 align:middle line:84%
In the end, what you, as a
pen tester, gets paid for

00:05:05.300 --> 00:05:09.770 align:middle line:84%
is turning in a report that
adds value to the company.

00:05:09.770 --> 00:05:12.860 align:middle line:84%
What they do with the report
is largely up to them.

00:05:12.860 --> 00:05:14.690 align:middle line:84%
What you include
in the report will

00:05:14.690 --> 00:05:18.170 align:middle line:84%
come from your technical
expertise as well

00:05:18.170 --> 00:05:21.530 align:middle line:84%
as some of your acumen and
understanding of their business

00:05:21.530 --> 00:05:22.190 align:middle line:90%
needs--

00:05:22.190 --> 00:05:26.180 align:middle line:84%
what the frameworks, what their
compliance and regulations

00:05:26.180 --> 00:05:27.320 align:middle line:90%
sets fort--

00:05:27.320 --> 00:05:30.830 align:middle line:84%
and making that into a very
useful package for them

00:05:30.830 --> 00:05:33.428 align:middle line:90%
at the end.

00:05:33.428 --> 00:05:37.040 align:middle line:84%
And with that, we're going to
do a little bit of auditing,

00:05:37.040 --> 00:05:38.490 align:middle line:90%
play with some of these tools.

00:05:38.490 --> 00:05:41.930 align:middle line:84%
We can use them ourselves,
and we do use them ourselves,

00:05:41.930 --> 00:05:43.190 align:middle line:90%
for pen testing.

00:05:43.190 --> 00:05:45.410 align:middle line:90%
But how can we mesh those two?

00:05:45.410 --> 00:05:47.420 align:middle line:84%
How can we understand
where they're coming from

00:05:47.420 --> 00:05:53.060 align:middle line:84%
as well as make some useful
reaches for our own needs

00:05:53.060 --> 00:05:55.060 align:middle line:90%
as pen testers?

00:05:55.060 --> 00:05:56.148 align:middle line:90%