WEBVTT

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


00:00:09.780 --> 00:00:12.390 align:middle line:84%
Now that we've covered the
basics and some regulations

00:00:12.390 --> 00:00:17.180 align:middle line:84%
and compliance, let's dive
into how it's all implemented.

00:00:17.180 --> 00:00:20.480 align:middle line:84%
We talked about business
needs, whether you're small--

00:00:20.480 --> 00:00:22.340 align:middle line:84%
working with a
small organization

00:00:22.340 --> 00:00:27.420 align:middle line:84%
or a large organization, it all
comes down to business needs.

00:00:27.420 --> 00:00:31.090 align:middle line:84%
How do we implement
them, though?

00:00:31.090 --> 00:00:34.060 align:middle line:84%
Fortunately, some
organizations and governments

00:00:34.060 --> 00:00:35.980 align:middle line:84%
have put together some
frameworks for us,

00:00:35.980 --> 00:00:38.830 align:middle line:84%
things that they either
require or things

00:00:38.830 --> 00:00:40.000 align:middle line:90%
that we can start with.

00:00:40.000 --> 00:00:43.920 align:middle line:90%


00:00:43.920 --> 00:00:47.850 align:middle line:84%
We're going to go through these
frameworks-- the ISO/IEC 27000

00:00:47.850 --> 00:00:51.390 align:middle line:84%
COBIT; NIST, a
cybersecurity framework;

00:00:51.390 --> 00:00:57.395 align:middle line:84%
the CIS; the US government's
CMMC, and the Australian's ASD.

00:00:57.395 --> 00:01:00.580 align:middle line:90%


00:01:00.580 --> 00:01:04.360 align:middle line:84%
So ISO/IEC 27000, it comes from
the International Organization

00:01:04.360 --> 00:01:08.920 align:middle line:84%
for Standardization and the
International Electrotechnical

00:01:08.920 --> 00:01:09.910 align:middle line:90%
Commission.

00:01:09.910 --> 00:01:11.440 align:middle line:90%
It's part of them.

00:01:11.440 --> 00:01:15.790 align:middle line:84%
Now, their guidelines are
deliberately broad in scope.

00:01:15.790 --> 00:01:18.580 align:middle line:84%
They're covering more than just
privacy and confidentiality

00:01:18.580 --> 00:01:20.140 align:middle line:90%
and cybersecurity issues.

00:01:20.140 --> 00:01:22.610 align:middle line:84%
It goes into a lot
of different parts.

00:01:22.610 --> 00:01:25.570 align:middle line:84%
It's a large organization
that covers a lot.

00:01:25.570 --> 00:01:28.210 align:middle line:84%
So the applicability
to organizations

00:01:28.210 --> 00:01:31.420 align:middle line:84%
fits no matter the size of
the organization, a big one

00:01:31.420 --> 00:01:34.000 align:middle line:90%
or a small one.

00:01:34.000 --> 00:01:38.110 align:middle line:84%
It's broken down into many
different publications.

00:01:38.110 --> 00:01:43.420 align:middle line:84%
But the ISO 27001
is the requirements.

00:01:43.420 --> 00:01:44.930 align:middle line:90%
It's the basis.

00:01:44.930 --> 00:01:46.570 align:middle line:90%
It's the guidelines, really.

00:01:46.570 --> 00:01:49.300 align:middle line:84%
If you're going to follow
something, follow these.

00:01:49.300 --> 00:01:55.840 align:middle line:84%
And then the 27002,
it's a code of practice

00:01:55.840 --> 00:02:01.090 align:middle line:84%
for how you can implement
those things, very useful, used

00:02:01.090 --> 00:02:04.930 align:middle line:84%
widely around the world,
and by many organizations

00:02:04.930 --> 00:02:05.980 align:middle line:90%
and governments even.

00:02:05.980 --> 00:02:08.650 align:middle line:90%


00:02:08.650 --> 00:02:11.350 align:middle line:84%
Next one we'll cover is
COBIT, Control Objectives

00:02:11.350 --> 00:02:13.810 align:middle line:84%
for Information
Related Technologies.

00:02:13.810 --> 00:02:16.090 align:middle line:84%
Now COBIT, created
by ISACA, it's

00:02:16.090 --> 00:02:18.760 align:middle line:84%
more than just IT
management, IT governance.

00:02:18.760 --> 00:02:23.290 align:middle line:84%
It covers some business
goals and generic processes

00:02:23.290 --> 00:02:26.930 align:middle line:84%
for the management of IT,
not just cybersecurity.

00:02:26.930 --> 00:02:29.140 align:middle line:84%
So it's kind of
a bigger picture.

00:02:29.140 --> 00:02:31.510 align:middle line:84%
And it's quite useful
for many organizations.

00:02:31.510 --> 00:02:34.650 align:middle line:90%


00:02:34.650 --> 00:02:39.815 align:middle line:84%
The NIST Special
Publication 800-53

00:02:39.815 --> 00:02:41.190 align:middle line:84%
comes from the
National Institute

00:02:41.190 --> 00:02:43.410 align:middle line:84%
of Standards and Technology
in the United States.

00:02:43.410 --> 00:02:47.700 align:middle line:84%
And the US government
requires it .

00:02:47.700 --> 00:02:50.760 align:middle line:84%
It's a set of-- a catalog of
security and privacy controls.

00:02:50.760 --> 00:02:53.880 align:middle line:84%
It's required for all US
federal information systems

00:02:53.880 --> 00:02:56.500 align:middle line:84%
except those related
to national security.

00:02:56.500 --> 00:03:00.270 align:middle line:84%
So internally developed by the
government for the government,

00:03:00.270 --> 00:03:02.850 align:middle line:84%
but other people can
utilize it as well.

00:03:02.850 --> 00:03:05.490 align:middle line:84%
Agencies are expected to
be compliant with security

00:03:05.490 --> 00:03:06.900 align:middle line:90%
standards and guidelines.

00:03:06.900 --> 00:03:11.910 align:middle line:84%
And the 800-53 Bravo provides
a set of baseline security

00:03:11.910 --> 00:03:13.890 align:middle line:90%
controls and privacy controls.

00:03:13.890 --> 00:03:16.980 align:middle line:84%
It's useful to look at, is
the organization that we're

00:03:16.980 --> 00:03:19.563 align:middle line:84%
assessing, that
we're working with,

00:03:19.563 --> 00:03:20.980 align:middle line:84%
are they following
some baselines?

00:03:20.980 --> 00:03:24.450 align:middle line:84%
Are they following some
security controls already?

00:03:24.450 --> 00:03:28.680 align:middle line:84%
Because that might tell us
what we need to scope out,

00:03:28.680 --> 00:03:30.900 align:middle line:84%
how our feedback
can be most useful,

00:03:30.900 --> 00:03:32.670 align:middle line:84%
what we should include
in our reports,

00:03:32.670 --> 00:03:36.120 align:middle line:84%
and how we should base all
this back to the customer.

00:03:36.120 --> 00:03:39.680 align:middle line:90%


00:03:39.680 --> 00:03:43.310 align:middle line:84%
The Center for
Internet Security,

00:03:43.310 --> 00:03:49.960 align:middle line:84%
another non-profit
organization, has

00:03:49.960 --> 00:03:51.910 align:middle line:84%
a set of 18
prioritized safeguards

00:03:51.910 --> 00:03:54.520 align:middle line:84%
to mitigate and
prevent cyber-attacks.

00:03:54.520 --> 00:03:56.980 align:middle line:84%
They were the most
prevalent cyber-attacks.

00:03:56.980 --> 00:03:58.780 align:middle line:84%
It takes a
defense-in-depth model

00:03:58.780 --> 00:04:00.860 align:middle line:84%
to help prevent
and detect malware.

00:04:00.860 --> 00:04:05.680 align:middle line:84%
And they have a free tool,
as well, to self-assess.

00:04:05.680 --> 00:04:10.840 align:middle line:84%
Now, this is great because it's
based around internet security

00:04:10.840 --> 00:04:12.940 align:middle line:84%
by an organization
that looks at what

00:04:12.940 --> 00:04:17.260 align:middle line:84%
are the most prevalent
attacks and then whips up

00:04:17.260 --> 00:04:19.899 align:middle line:84%
strategies that
should be implemented

00:04:19.899 --> 00:04:23.203 align:middle line:84%
by any company that's trying
to prevent those things.

00:04:23.203 --> 00:04:24.370 align:middle line:90%
It's fairly straightforward.

00:04:24.370 --> 00:04:27.790 align:middle line:84%
And it's really great that they
have free products as well.

00:04:27.790 --> 00:04:31.410 align:middle line:90%


00:04:31.410 --> 00:04:34.280 align:middle line:84%
We'll get into another
government organization.

00:04:34.280 --> 00:04:37.550 align:middle line:84%
the US Department of Defense
has their cybersecurity maturity

00:04:37.550 --> 00:04:39.080 align:middle line:90%
model certification.

00:04:39.080 --> 00:04:40.640 align:middle line:90%
And it's on version 2 right now.

00:04:40.640 --> 00:04:43.130 align:middle line:84%
It's a training certification
and third party assessment

00:04:43.130 --> 00:04:46.730 align:middle line:84%
program of cybersecurity in
the United States government

00:04:46.730 --> 00:04:48.960 align:middle line:90%
Defense Industrial Base.

00:04:48.960 --> 00:04:56.040 align:middle line:84%
So anyone touching the DOD,
or the Defense Department

00:04:56.040 --> 00:04:58.200 align:middle line:84%
in the grander
scheme, or any company

00:04:58.200 --> 00:05:03.540 align:middle line:84%
who is working with the
DOD have to comply by CMMC.

00:05:03.540 --> 00:05:05.430 align:middle line:84%
And they're required
to have a third party

00:05:05.430 --> 00:05:09.510 align:middle line:84%
assessor verify their
cybersecurity maturation level.

00:05:09.510 --> 00:05:11.940 align:middle line:84%
This is where we start
getting into maturity.

00:05:11.940 --> 00:05:17.460 align:middle line:84%
There's five different levels
and 17 different capability

00:05:17.460 --> 00:05:18.720 align:middle line:90%
domains.

00:05:18.720 --> 00:05:20.790 align:middle line:84%
Now this is useful because
for the US government,

00:05:20.790 --> 00:05:24.430 align:middle line:84%
they have many
different levels of--

00:05:24.430 --> 00:05:26.500 align:middle line:84%
or tiers of information,
if you will,

00:05:26.500 --> 00:05:31.930 align:middle line:84%
different confidentiality
levels and security levels.

00:05:31.930 --> 00:05:35.290 align:middle line:84%
So depending on the maturity
of the organization,

00:05:35.290 --> 00:05:37.660 align:middle line:84%
they may or may not be
able to touch or work

00:05:37.660 --> 00:05:41.290 align:middle line:84%
with information at those
different security levels.

00:05:41.290 --> 00:05:43.420 align:middle line:84%
And this is quite
useful because you

00:05:43.420 --> 00:05:51.010 align:middle line:84%
want your most prized, most
important assets really secured

00:05:51.010 --> 00:05:51.880 align:middle line:90%
in this--

00:05:51.880 --> 00:05:54.670 align:middle line:84%
especially when you're
talking about national defense

00:05:54.670 --> 00:05:58.570 align:middle line:84%
in the United States
and other countries,

00:05:58.570 --> 00:06:02.300 align:middle line:84%
nation states that might be
interested in that information.

00:06:02.300 --> 00:06:04.790 align:middle line:84%
So while level
one is performed--

00:06:04.790 --> 00:06:08.350 align:middle line:84%
so that's the baseline,
are they doing security?

00:06:08.350 --> 00:06:10.270 align:middle line:90%
Level five is optimizing.

00:06:10.270 --> 00:06:11.810 align:middle line:84%
Not only are they
doing security,

00:06:11.810 --> 00:06:13.600 align:middle line:84%
but they're doing
so in such a way

00:06:13.600 --> 00:06:15.760 align:middle line:84%
that they're coming up
with the next baselines.

00:06:15.760 --> 00:06:18.250 align:middle line:84%
They're coming up
with the newest

00:06:18.250 --> 00:06:22.895 align:middle line:84%
practices for the industry
and for the global community

00:06:22.895 --> 00:06:23.395 align:middle line:90%
as well.

00:06:23.395 --> 00:06:27.330 align:middle line:90%


00:06:27.330 --> 00:06:31.050 align:middle line:84%
The Australians have their
Australian Cyber Security

00:06:31.050 --> 00:06:35.310 align:middle line:84%
Centre and the Australian
Signals Directorate.

00:06:35.310 --> 00:06:38.130 align:middle line:84%
And they came up with
the Essential Eight.

00:06:38.130 --> 00:06:42.810 align:middle line:84%
It's a baseline and structure
to help organizations protect

00:06:42.810 --> 00:06:46.290 align:middle line:84%
themselves against various
cyber threats, developed

00:06:46.290 --> 00:06:47.340 align:middle line:90%
to help Australians.

00:06:47.340 --> 00:06:48.810 align:middle line:84%
But anyone could
implement these.

00:06:48.810 --> 00:06:49.890 align:middle line:90%
Anyone can follow them.

00:06:49.890 --> 00:06:52.890 align:middle line:90%
And it's all available publicly.

00:06:52.890 --> 00:06:54.750 align:middle line:84%
Designed to protect
Microsoft Windows-based

00:06:54.750 --> 00:06:57.090 align:middle line:84%
internet-connected
networks, because that's

00:06:57.090 --> 00:07:01.170 align:middle line:84%
what they had most prevalently
in their government.

00:07:01.170 --> 00:07:04.440 align:middle line:84%
And there's four
different maturity levels.

00:07:04.440 --> 00:07:07.020 align:middle line:84%
Depending on the level, the
implementation of these eight

00:07:07.020 --> 00:07:09.960 align:middle line:90%
security controls will vary.

00:07:09.960 --> 00:07:14.670 align:middle line:84%
Similar to the other model, a
small, new organization who's

00:07:14.670 --> 00:07:16.980 align:middle line:84%
just getting started
in cybersecurity needs

00:07:16.980 --> 00:07:18.270 align:middle line:90%
to at least implement.

00:07:18.270 --> 00:07:21.480 align:middle line:84%
And they'll build their
way up to setting best

00:07:21.480 --> 00:07:23.790 align:middle line:90%
practices for the community.

00:07:23.790 --> 00:07:27.180 align:middle line:84%
But understanding where they're
at, where they need to develop,

00:07:27.180 --> 00:07:30.930 align:middle line:84%
how they need to improve
is also tied into these.

00:07:30.930 --> 00:07:33.210 align:middle line:84%
That's what's useful
about a maturity model

00:07:33.210 --> 00:07:37.470 align:middle line:84%
in these frameworks is
they not only know, OK,

00:07:37.470 --> 00:07:40.920 align:middle line:84%
what do we need to start
doing now at our level?

00:07:40.920 --> 00:07:42.670 align:middle line:84%
But how can we get
to the next level?

00:07:42.670 --> 00:07:46.545 align:middle line:84%
How can we not just be
secure but be better?

00:07:46.545 --> 00:07:53.310 align:middle line:90%


00:07:53.310 --> 00:07:53.810 align:middle line:90%
So what?

00:07:53.810 --> 00:07:55.620 align:middle line:90%
Why does any of this matter?

00:07:55.620 --> 00:07:56.840 align:middle line:90%
Why are we covering this?

00:07:56.840 --> 00:07:59.720 align:middle line:84%
Why are we doing
auditing fundamentals

00:07:59.720 --> 00:08:01.700 align:middle line:90%
in a pen testing course?

00:08:01.700 --> 00:08:05.870 align:middle line:84%
Because your pen
test is going to all

00:08:05.870 --> 00:08:10.790 align:middle line:84%
lead back to the company, to the
organization, to your customer.

00:08:10.790 --> 00:08:12.740 align:middle line:90%
You need to add value to them.

00:08:12.740 --> 00:08:16.250 align:middle line:84%
And they need to get something
useful that they can then

00:08:16.250 --> 00:08:19.760 align:middle line:84%
implement in their
organizations themselves

00:08:19.760 --> 00:08:22.410 align:middle line:84%
to mix into their risk
management; to understand,

00:08:22.410 --> 00:08:25.070 align:middle line:84%
OK, maybe you're
just recommending,

00:08:25.070 --> 00:08:26.850 align:middle line:90%
hey, do this, this, and this.

00:08:26.850 --> 00:08:30.723 align:middle line:84%
Well, what if that doesn't fit
their risk-management style?

00:08:30.723 --> 00:08:32.390 align:middle line:84%
What if that doesn't
match the framework

00:08:32.390 --> 00:08:33.473 align:middle line:90%
that they're working with?

00:08:33.473 --> 00:08:36.780 align:middle line:84%
Maybe that doesn't match
their maturity level?

00:08:36.780 --> 00:08:40.385 align:middle line:84%
So you, maybe, could tier
your recommendations.

00:08:40.385 --> 00:08:42.059 align:middle line:90%
You definitely should do this.

00:08:42.059 --> 00:08:43.640 align:middle line:90%
It's highly-- it's very severe.

00:08:43.640 --> 00:08:46.760 align:middle line:90%
And it is going to possibly--

00:08:46.760 --> 00:08:49.070 align:middle line:84%
most probably lead to
you having a breach

00:08:49.070 --> 00:08:50.690 align:middle line:90%
and losing information.

00:08:50.690 --> 00:08:52.730 align:middle line:84%
You should probably
also implement this.

00:08:52.730 --> 00:08:54.230 align:middle line:90%
You could implement that.

00:08:54.230 --> 00:08:56.510 align:middle line:84%
And I also recommend
this other thing.

00:08:56.510 --> 00:09:00.470 align:middle line:84%
Tiering your recommendations
and putting severity levels

00:09:00.470 --> 00:09:01.520 align:middle line:90%
is really important.

00:09:01.520 --> 00:09:04.280 align:middle line:84%
Understanding what they're
already working with,

00:09:04.280 --> 00:09:06.410 align:middle line:84%
using language that
they're familiar with

00:09:06.410 --> 00:09:10.280 align:middle line:84%
is crucial to adding the
most value in your reports.

00:09:10.280 --> 00:09:13.210 align:middle line:90%


00:09:13.210 --> 00:09:17.410 align:middle line:84%
Now, let's take a step
and, actually, how would we

00:09:17.410 --> 00:09:18.670 align:middle line:90%
implement some auditing?

00:09:18.670 --> 00:09:20.170 align:middle line:84%
We're going to get
into pen testing.

00:09:20.170 --> 00:09:22.690 align:middle line:84%
But, first, let's
look at how would you

00:09:22.690 --> 00:09:24.290 align:middle line:90%
even just do an audit?

00:09:24.290 --> 00:09:28.730 align:middle line:84%
How would they, without needing
a pen test, get started?

00:09:28.730 --> 00:09:30.900 align:middle line:90%
So let's dive in.

00:09:30.900 --> 00:09:31.400 align:middle line:90%