WEBVTT

00:00:00.000 --> 00:00:01.360
[Autogenerated] Jacob In the theory section,

00:00:01.360 --> 00:00:06.060
I talked about scope reduction and how to segment your network into smaller

00:00:06.060 --> 00:00:10.170
networks on how to do other techniques such as token ization,

00:00:10.830 --> 00:00:15.340
orcs on cryptography or outsourcing to reduce the scope

00:00:15.700 --> 00:00:18.550
of PC ideas s in an organization.

00:00:19.530 --> 00:00:20.170
There's a QS.

00:00:20.170 --> 00:00:23.630
I'm sure you've seen lots of organizations do scope reduction to

00:00:23.630 --> 00:00:26.040
reduce the scope and complexity of PC OD assessed.

00:00:26.050 --> 00:00:29.080
Yes, Could you give me a flavor of what's good and what's bad?

00:00:29.090 --> 00:00:29.490
Sure.

00:00:29.820 --> 00:00:32.750
So the good examples, right?

00:00:32.940 --> 00:00:36.500
Maybe our cases where you can sort of clearly outsource some functionality

00:00:37.350 --> 00:00:41.680
or or sort of airlift that that component out of your organization and get

00:00:41.680 --> 00:00:43.360
somebody else toe to sort of do it right.

00:00:43.440 --> 00:00:47.090
And then the components, the networking pieces,

00:00:47.090 --> 00:00:48.290
the systems, the people,

00:00:48.290 --> 00:00:52.500
the processes that you used to have in your environment are now.

00:00:52.510 --> 00:00:53.510
Somebody else is right,

00:00:53.510 --> 00:00:56.000
and all you're doing is kind of managing that business relationship.

00:00:56.170 --> 00:00:57.860
Those air, usually pretty successful.

00:00:58.610 --> 00:01:00.810
There are success cases where somebody has

00:01:00.910 --> 00:01:02.730
implemented some network segmentation.

00:01:02.740 --> 00:01:05.330
Thes two networks used to be commingle.

00:01:05.330 --> 00:01:09.850
They used to be one, and they have sort firmly divided them,

00:01:09.850 --> 00:01:13.010
right, the where your packets don't get for one to the other,

00:01:13.020 --> 00:01:13.320
right?

00:01:13.530 --> 00:01:14.830
Good, well and good.

00:01:14.930 --> 00:01:17.930
And sometimes you have to then build some other network,

00:01:17.940 --> 00:01:20.580
you know, some other infrastructure pieces to service.

00:01:20.580 --> 00:01:23.610
Now both sides of that divide right and and very

00:01:23.610 --> 00:01:25.090
often that sort of worth the effort.

00:01:25.090 --> 00:01:25.900
So you might have.

00:01:25.990 --> 00:01:29.220
You might split yourself into two domains friends on Exactly right.

00:01:29.220 --> 00:01:32.460
That's there's one very common case where that sort of thing happens.

00:01:33.130 --> 00:01:35.880
I've seen this go badly also where,

00:01:35.890 --> 00:01:40.820
and organizations that it fails to understand what segmentation really is on.

00:01:40.820 --> 00:01:46.090
And they don't really engage us as the assessor early on in the process, right?

00:01:46.100 --> 00:01:48.370
And there's so many cases where I tell my clients,

00:01:48.370 --> 00:01:49.840
I wish we could have done this.

00:01:49.840 --> 00:01:53.040
I wish we could have had this conversation four months ago, right?

00:01:53.050 --> 00:01:53.350
Right,

00:01:53.490 --> 00:01:56.660
And then we could have at least sort of steered you in a better direction

00:01:57.180 --> 00:02:00.970
because they sort of burrow themselves underground and ______ away at at

00:02:00.970 --> 00:02:04.100
working on their networking devices on their segmentation,

00:02:04.260 --> 00:02:05.630
and they come back up and they say, Look,

00:02:05.630 --> 00:02:07.070
these air now totally separate,

00:02:07.080 --> 00:02:09.350
except for these 18 ports and services that we

00:02:09.350 --> 00:02:11.160
allow between the two environments.

00:02:11.450 --> 00:02:15.600
And I say That's not segmentation, right?

00:02:15.640 --> 00:02:19.260
And that's not what you want to hear after you've committed so

00:02:19.260 --> 00:02:21.550
much time and energy and exercise like that.

00:02:22.240 --> 00:02:25.490
So again, that's get your que essa early.

00:02:25.500 --> 00:02:28.190
If you're going to try and do scope reduction by segmentation to

00:02:28.190 --> 00:02:29.900
make sure that it's actually proper segment,

00:02:29.910 --> 00:02:35.030
right, right and then be prepared to put together a meaningful strategy.

00:02:35.040 --> 00:02:35.180
I mean,

00:02:35.180 --> 00:02:38.080
this is true of just about any major engineering effort that

00:02:38.080 --> 00:02:39.660
you're going to do in your compliance effort.

00:02:40.010 --> 00:02:41.810
Put together a useful project plan.

00:02:41.810 --> 00:02:44.480
Put together a useful description of what you would tend to do,

00:02:44.850 --> 00:02:45.150
right,

00:02:45.150 --> 00:02:49.650
your assessor review it and critique it right and then commit to that effort.
