WEBVTT

00:00:00.040 --> 00:00:01.150
[Autogenerated] I'm gonna ask you the pro,

00:00:01.160 --> 00:00:06.320
because this is actually the worst section for tough questions for the QS.

00:00:06.320 --> 00:00:09.830
IT is right, Because the last one I'm gonna ask you is Jacob.

00:00:09.840 --> 00:00:11.440
What's a significant change?

00:00:11.450 --> 00:00:14.870
Because you have to scam quarterly or significant change.

00:00:14.880 --> 00:00:19.760
So So that varies based on the organization, right?

00:00:19.770 --> 00:00:23.500
And and again, you know, in the USA says it depends.

00:00:23.510 --> 00:00:24.410
Asked the U.

00:00:24.410 --> 00:00:24.810
S A.

00:00:24.820 --> 00:00:26.390
On what does it depend?

00:00:26.400 --> 00:00:26.670
Right?

00:00:26.670 --> 00:00:28.080
And look for the quality of that answer.

00:00:28.090 --> 00:00:28.290
Right?

00:00:28.290 --> 00:00:34.000
So an organization that deploys all of their systems by hand,

00:00:34.010 --> 00:00:37.010
right and does so infrequently, uh, you know,

00:00:37.010 --> 00:00:38.890
or or has a very sort of manual build process,

00:00:38.890 --> 00:00:39.030
right?

00:00:39.030 --> 00:00:40.680
If they put a new server in the environment,

00:00:40.690 --> 00:00:42.770
maybe that's a significant change for them,

00:00:42.780 --> 00:00:43.470
right?

00:00:43.480 --> 00:00:46.980
An organization that lives in some sort of cloud based service where it

00:00:46.980 --> 00:00:51.760
could sort of automatically deploy systems and then and then decommissioned

00:00:51.760 --> 00:00:54.320
them based on volume based on load or activity.

00:00:54.330 --> 00:00:54.800
Right?

00:00:54.810 --> 00:00:58.450
Deploying 100 new systems might not be a significant change,

00:00:58.460 --> 00:01:04.310
all right, but But I would say if it effects so the security profile right?

00:01:04.310 --> 00:01:07.860
Or the threat profile or the attack surface um,

00:01:08.340 --> 00:01:11.190
or you you can see the where it's affecting.

00:01:11.190 --> 00:01:15.200
Maybe what you would have said about one of the PC AD DS s requirements,

00:01:15.210 --> 00:01:16.370
right then.

00:01:16.380 --> 00:01:19.130
That's absolutely a significant change, right?

00:01:19.140 --> 00:01:22.230
Uh, and then, you know,

00:01:22.230 --> 00:01:24.560
other cases where that maybe doesn't fit that qualification.

00:01:24.560 --> 00:01:26.410
It's a sort of situational, right?

00:01:26.420 --> 00:01:30.060
It's intended to be something that you again you have some sort

00:01:30.060 --> 00:01:33.500
of good faith effort to try to determine your criteria for that

00:01:33.510 --> 00:01:36.270
internal scanning cloud environments.

00:01:36.280 --> 00:01:37.320
Is that tough?

00:01:37.330 --> 00:01:38.620
It can be right.

00:01:38.620 --> 00:01:43.440
The notion of an internal network sometimes starts to fall apart, right?

00:01:43.450 --> 00:01:47.970
So the goal the goal was internal scans was to say,

00:01:48.140 --> 00:01:52.800
What can we see from an internal vantage that we can't

00:01:52.800 --> 00:01:55.680
see from an external vantage right on?

00:01:55.680 --> 00:02:00.090
And how do we avoid the situation where maybe the perimeter

00:02:00.100 --> 00:02:02.020
has all of the sort of security hardening?

00:02:02.020 --> 00:02:05.150
But once you get past that, uh, it's it's very,

00:02:05.160 --> 00:02:06.740
you know, soft and squishy, right?

00:02:06.750 --> 00:02:09.400
It's loose and easy to sort of affect things.

00:02:09.400 --> 00:02:10.240
That versus chocolate.

00:02:10.240 --> 00:02:12.920
Eminem Exactly on the outside, Soft on the inside.

00:02:12.920 --> 00:02:13.330
Exactly.

00:02:13.330 --> 00:02:13.690
Right.

00:02:13.700 --> 00:02:16.150
So the goal of the internal scan was to say,

00:02:16.940 --> 00:02:19.570
Let's look at the interior of the environment.

00:02:19.580 --> 00:02:20.140
Right?

00:02:20.150 --> 00:02:23.060
Uh, you know, inside the perimeter, right?

00:02:23.070 --> 00:02:23.840
Because, you know,

00:02:23.840 --> 00:02:27.080
we've been talking about this idea of d perimeter ization for a long,

00:02:27.080 --> 00:02:27.880
long time.

00:02:27.890 --> 00:02:34.770
Um and and see what we see right and and, you know, resolve those concerns.

00:02:34.780 --> 00:02:39.820
So if if there's not really an interior sort of vantage,

00:02:39.830 --> 00:02:40.300
right,

00:02:40.310 --> 00:02:45.530
if what you see from from an external perspective is what

00:02:45.530 --> 00:02:47.670
you see from an internal perspective, right?

00:02:47.670 --> 00:02:51.690
And that external, that internal aspect converge, uh, in a cloud environment.

00:02:51.700 --> 00:02:52.110
Yeah.

00:02:52.120 --> 00:02:52.600
Okay.

00:02:52.610 --> 00:02:54.550
But if you have a VPC with, like,

00:02:54.560 --> 00:02:56.990
internet facing stuff and non internet facing stuff,

00:02:57.000 --> 00:02:58.680
you're scanning the non internet facing.

00:02:58.690 --> 00:02:59.520
Exactly.

00:02:59.530 --> 00:03:01.100
Yeah, that's exactly right.

00:03:01.110 --> 00:03:01.570
Great.

00:03:01.940 --> 00:03:04.300
Can we go back to the full passing scans?

00:03:04.310 --> 00:03:04.990
Sure.

00:03:05.000 --> 00:03:06.760
If a merchant's missed, of course.

00:03:06.760 --> 00:03:07.820
What do they need to do?

00:03:07.830 --> 00:03:10.670
So if they've missed a quarter sometime ago,

00:03:10.680 --> 00:03:14.190
right and absent a time machine, you can't go resolve that.

00:03:14.200 --> 00:03:17.870
Uh, I mean,

00:03:18.440 --> 00:03:22.160
I would want to see historically what I would have wanted to see was

00:03:22.170 --> 00:03:25.720
obviously a current passing scans and then some sort of additional

00:03:25.720 --> 00:03:28.950
measure to make sure that this didn't happen again.

00:03:28.960 --> 00:03:29.720
Right?

00:03:29.730 --> 00:03:36.230
Uh, some of the stuff in, like, 10.8 and 12.11, which we'll talk about later.

00:03:36.240 --> 00:03:37.060
Uh,

00:03:37.540 --> 00:03:40.040
sort of already now require those additional controls

00:03:40.040 --> 00:03:41.690
to make sure things don't fall down.

00:03:41.700 --> 00:03:44.890
So that's a less sort of clear cut approach to maybe like a

00:03:44.890 --> 00:03:47.050
compensating control from missing the scans.

00:03:47.060 --> 00:03:52.060
You can You could always you could always just sort of kind of,

00:03:52.070 --> 00:03:56.350
you know, how to Just how do we prevent this from happening again?

00:03:56.440 --> 00:03:57.170
And if they're a week?

00:03:57.170 --> 00:03:59.980
Lights, I mean, how excited that you are.

00:03:59.990 --> 00:04:04.590
So So there have been some some guidance statements from

00:04:04.590 --> 00:04:07.780
the council that they really do want, you know,

00:04:07.780 --> 00:04:08.460
90 days.

00:04:08.460 --> 00:04:09.780
I really do want quarterly.

00:04:10.030 --> 00:04:13.680
Um, you know, I guess up up until that point,

00:04:13.690 --> 00:04:17.290
I have been sort of less concerned about a little bit here a little bit there.

00:04:17.300 --> 00:04:21.860
Um, you know, particularly if it's just Hey, the scan is still running, right?

00:04:21.860 --> 00:04:24.460
But we got a lot of hosts and it takes time.

00:04:24.840 --> 00:04:28.100
You know, I I guess I didn't I didn't get too bent out of shape about that.

00:04:28.110 --> 00:04:31.190
Um, but the I mean, the guidance is, you know?

00:04:31.200 --> 00:04:34.250
Yeah, you got to kind of stick the landing on the timing on.

00:04:34.250 --> 00:04:35.320
So, you know,

00:04:35.320 --> 00:04:36.640
to the extent that you could sort of hold somebody

00:04:36.640 --> 00:04:38.070
to that I think you want to do.
