WEBVTT

00:00:00.140 --> 00:00:02.220
[Autogenerated] testing segmentation is a new requirement.

00:00:02.220 --> 00:00:04.710
Is APIs added to the pen testing?

00:00:04.720 --> 00:00:07.620
So if you're using segmentation to isolate your cart,

00:00:07.620 --> 00:00:10.080
all the data environment from, say, your corporate network,

00:00:10.090 --> 00:00:13.760
you have to test that isolation by pen testing IT.

00:00:13.940 --> 00:00:17.220
So I find I find a lot of problems with this.

00:00:17.230 --> 00:00:21.380
If I don't get in front of that and intervene right with the client,

00:00:21.390 --> 00:00:24.560
I find a lot of organizations just essentially running like port

00:00:24.560 --> 00:00:29.230
scans from some arbitrary point to some other arbitrary point and

00:00:29.230 --> 00:00:31.490
finding no ports open and saying, Yeah, segmentation,

00:00:31.490 --> 00:00:32.189
right, we're done.

00:00:32.200 --> 00:00:34.860
And and maybe that's part of it.

00:00:35.340 --> 00:00:37.880
Yeah, sure.

00:00:37.890 --> 00:00:42.850
But you know, the scoping guidance document talks about more than just,

00:00:43.640 --> 00:00:47.490
uh, network A C l's right being part of your segmentation controls,

00:00:47.490 --> 00:00:47.640
right?

00:00:47.640 --> 00:00:50.550
You're the remote access gateways is part of that.

00:00:50.560 --> 00:00:53.550
Uh, you know, maybe some I t shirt services error part of that.

00:00:53.560 --> 00:00:57.680
And I think, uh, you know, very particularly again in the methodology.

00:00:57.690 --> 00:00:58.680
Uh, you know,

00:00:58.680 --> 00:01:03.130
you want to have some point where you engage with the assessor and you

00:01:03.130 --> 00:01:06.580
engage with the pen tester and you work out together.

00:01:07.440 --> 00:01:11.440
What are the segmentation scenarios that error worth testing, right?

00:01:11.450 --> 00:01:13.770
We talked about this way back in requirement one, right?

00:01:13.770 --> 00:01:18.300
Like maybe the the administrator laptop with a personal firewall

00:01:18.300 --> 00:01:20.040
software on it or whatever controls on it,

00:01:20.050 --> 00:01:20.430
Right?

00:01:20.430 --> 00:01:23.910
Maybe you want to test from that vantage if I'm the bad guy and I'm

00:01:23.910 --> 00:01:27.450
adjacent to that administrator laptop in the corporate domain,

00:01:27.840 --> 00:01:31.900
can I suborn or impersonate that workstation?

00:01:31.910 --> 00:01:35.650
Or go to the remote access gateway and pretend to be that

00:01:35.650 --> 00:01:38.010
administrative work station and get through right,

00:01:38.020 --> 00:01:40.480
So So So in this one, I actually agree with you.

00:01:40.480 --> 00:01:43.420
It's It's almost essential for someone who really understands

00:01:43.420 --> 00:01:46.790
the network and have the segmentation set up to work with the

00:01:46.790 --> 00:01:48.760
pen testers to work out to test it.

00:01:48.740 --> 00:01:51.350
And it's very likely that the pen tester just doesn't have

00:01:51.350 --> 00:01:53.160
that familiarity with the environment, right?

00:01:53.160 --> 00:01:55.960
And they're going to say, you know, this is what you told us to do,

00:01:55.960 --> 00:01:57.640
and we did it right now.

00:01:57.650 --> 00:02:03.050
I was on the council when this requirement was drafted and put there.

00:02:03.040 --> 00:02:05.460
It's there for a really good reason,

00:02:05.470 --> 00:02:09.840
because this was a source of masses of compromises that people would

00:02:09.850 --> 00:02:13.040
actually get into the corporate network and then escalate themselves

00:02:13.040 --> 00:02:15.080
across to the cardholder days for environment because the

00:02:15.080 --> 00:02:17.030
segmentation was segmentation was lousy,

00:02:17.030 --> 00:02:19.810
and they just believed it was in place or someone to tweak the

00:02:19.810 --> 00:02:22.200
segmentation after being put in place on.

00:02:22.200 --> 00:02:23.210
You don't see it with the firewall.

00:02:23.210 --> 00:02:23.770
Real check.

00:02:23.780 --> 00:02:27.670
You actually want a proper pen test and you'll notice if your

00:02:27.670 --> 00:02:29.290
service provider you're doing this every six months,

00:02:29.290 --> 00:02:30.560
not every 12 months.

00:02:30.540 --> 00:02:32.590
Because this what I weigh in to lots of service

00:02:32.590 --> 00:02:35.450
providers and it probably still is right.

00:02:35.460 --> 00:02:37.970
It probably It probably still is because I think a lot of assessors

00:02:37.970 --> 00:02:41.180
don't have sort of the wherewithal for whatever reason,

00:02:41.180 --> 00:02:42.700
to really sort of hold people to this.

00:02:42.700 --> 00:02:44.580
And a lot of pen testers, you know,

00:02:44.590 --> 00:02:48.210
are running and map scans because that's what they know how to do.

00:02:48.210 --> 00:02:49.150
I mean, absence, um,

00:02:49.150 --> 00:02:52.740
more guidance or direction from the client about what to test,

00:02:52.750 --> 00:02:53.320
right?

00:02:53.330 --> 00:02:54.550
I mean, if you go to them and say, Hey,

00:02:54.550 --> 00:02:56.230
I want you to test this remote access gateway.

00:02:56.230 --> 00:02:58.320
Can you get around?

00:02:58.330 --> 00:03:00.770
You know this mechanism, Can you suborn it?

00:03:00.770 --> 00:03:02.840
Can you defeat the multi factor authentication?

00:03:02.850 --> 00:03:05.260
They know how to do that right or that should,

00:03:05.270 --> 00:03:06.070
uh,

00:03:06.040 --> 00:03:08.150
but you have to sort of point them in the right direction because

00:03:08.150 --> 00:03:09.580
they're not going to know the environment as well.

00:03:09.590 --> 00:03:09.830
Yeah.

00:03:09.830 --> 00:03:12.910
I mean, this has to be white box testing, not black box testing.

00:03:12.910 --> 00:03:16.330
It's not like there's a port CDs over there.

00:03:16.330 --> 00:03:16.960
Off you go.

00:03:16.970 --> 00:03:17.530
It has to be.

00:03:17.540 --> 00:03:18.650
Here's our segmentation.

00:03:18.650 --> 00:03:19.980
Here's what the network looks like.

00:03:19.980 --> 00:03:21.640
You know, pretend you're a criminal.

00:03:21.650 --> 00:03:24.410
You've got You've found all that access.

00:03:24.420 --> 00:03:28.180
Found what the systems are now see if you can get through and defeat.

00:03:28.190 --> 00:03:29.280
It has to be completely white.

00:03:29.280 --> 00:03:30.400
Box e.

00:03:30.400 --> 00:03:33.090
I think it's come up with the specific scenario.

00:03:33.100 --> 00:03:33.670
Right?

00:03:33.940 --> 00:03:36.310
Uh, you know, and and work together collaboratively.

00:03:36.310 --> 00:03:39.030
I want the pen testers input on what I think the scenarios are.

00:03:39.040 --> 00:03:41.650
I want the clients input on what I think the scenarios are.

00:03:41.640 --> 00:03:42.620
You know, personally,

00:03:42.620 --> 00:03:47.090
I can't emphasize hard enough how this is nothing to do with compliance.

00:03:47.100 --> 00:03:50.790
This is getting someone to check that your stuff is working, right?

00:03:50.800 --> 00:03:51.150
Yeah.

00:03:51.160 --> 00:03:54.290
And you learn things on a pan test that you learn in no other

00:03:54.290 --> 00:03:56.560
way other than by having a good pen test.

00:03:56.560 --> 00:03:59.810
Well, this this is verifying you know requirement zero, right?

00:03:59.820 --> 00:04:02.320
Like, is your scope appropriate?

00:04:02.330 --> 00:04:03.390
You're absolutely right.

00:04:03.400 --> 00:04:05.910
And if this fails, right then,

00:04:05.920 --> 00:04:10.650
you know the scope is problematic before you need to go fix your segmentation.

00:04:10.660 --> 00:04:11.570
But if if this fails,

00:04:11.570 --> 00:04:15.130
it means you've learned it from somebody you brought in to tell you it's failed.

00:04:15.140 --> 00:04:17.220
Not because the car brands error ringing up because

00:04:17.220 --> 00:04:19.190
you're a common point of purchase,

00:04:19.200 --> 00:04:22.630
right on their detected that you've been taken by the criminals.

00:04:22.640 --> 00:04:25.580
IT great is anything else we should talk about on pan testing.

00:04:25.640 --> 00:04:27.250
Um, I think we're pretty wrapped up.

00:04:27.250 --> 00:04:31.240
I think Way did.

00:04:31.240 --> 00:04:33.040
This is a whole separate module because,

00:04:33.050 --> 00:04:36.960
you know, personally and having seen data compromise reports for many years,

00:04:36.970 --> 00:04:40.340
this is the one thing that people do really badly.

00:04:40.350 --> 00:04:44.300
They buy bad pen tests from pen testing companies on.

00:04:44.300 --> 00:04:47.250
They basically say, you know, we want to pass.

00:04:47.250 --> 00:04:50.550
It's like the passing pan test is the worst pan test ever.

00:04:50.560 --> 00:04:55.620
A pen test that finds nothing is just an absolute waste of money.

00:04:55.630 --> 00:04:58.690
All you've learned is you spent some money to find nothing.

00:04:58.690 --> 00:05:01.710
The best pen test finds lots of things for you to go

00:05:01.710 --> 00:05:03.810
away and fix on to talk about.

00:05:03.820 --> 00:05:06.550
And if it's your segmentation where someone's broken,

00:05:06.550 --> 00:05:08.710
it's like, Okay, we need to restructure our network.

00:05:08.710 --> 00:05:08.970
So?

00:05:09.040 --> 00:05:12.710
So Pan testing is probably one of the most important

00:05:12.720 --> 00:05:16.240
requirements in PC IDE s s for security,

00:05:16.250 --> 00:05:17.350
not just compliance.
