WEBVTT

00:00:00.000 --> 00:00:03.200
[Autogenerated] now talking about scoping large organizations.

00:00:03.910 --> 00:00:06.510
Do you have any tips for very large organizations?

00:00:06.720 --> 00:00:08.480
Because I've seen, you know,

00:00:08.850 --> 00:00:12.020
organizations complain that sometimes their assessment takes six months because

00:00:12.020 --> 00:00:15.150
their organization is just so so big that that can't happen.

00:00:15.160 --> 00:00:15.490
Yes,

00:00:15.490 --> 00:00:18.550
where you get a very large organization that's got a very complex environment,

00:00:18.800 --> 00:00:20.470
really Siris of environments.

00:00:20.470 --> 00:00:22.540
In some cases, and I've seen very large organizations.

00:00:22.540 --> 00:00:25.530
I've worked with some very large organizations that break

00:00:25.530 --> 00:00:27.420
it up into individual business units.

00:00:27.470 --> 00:00:27.770
Right.

00:00:28.300 --> 00:00:33.480
This works particularly well when those business units are self contained,

00:00:33.610 --> 00:00:35.150
right arm or self contained.

00:00:35.720 --> 00:00:40.060
Uh, or, uh, you know, where there may be the results of acquisitions, right?

00:00:40.060 --> 00:00:42.960
And so they have some natural boundaries that make a lot of sense.

00:00:43.140 --> 00:00:46.590
One of the things that we have done for certain organizations is do

00:00:46.590 --> 00:00:48.930
like an infrastructure layer kind of assessment.

00:00:48.970 --> 00:00:49.260
Right?

00:00:49.270 --> 00:00:55.140
Uh, for the common aspect that when you say an assessment,

00:00:55.150 --> 00:00:57.460
would you actually write a separate report on compliance for that?

00:00:57.530 --> 00:00:58.690
Yes, right, right.

00:00:58.790 --> 00:01:00.080
Eso right.

00:01:00.080 --> 00:01:03.270
A separate report on compliance for the network services.

00:01:03.270 --> 00:01:07.120
Right for the team that manages firewalls or network devices across the whole

00:01:07.120 --> 00:01:10.490
enterprise or the team that provides the security monitoring services across

00:01:10.490 --> 00:01:14.910
the whole enterprise or the policies and procedures that apply across various

00:01:15.300 --> 00:01:20.470
parts of the business and then essentially treat that entity like a service

00:01:20.470 --> 00:01:26.120
provider to the individual business units that use those shared services for

00:01:26.120 --> 00:01:26.780
their networking,

00:01:26.780 --> 00:01:30.630
for the security monitoring for other aspects of what they do on,

00:01:30.630 --> 00:01:33.880
and then assess each individual business units for the

00:01:33.880 --> 00:01:35.260
things that are particular to them.

00:01:35.750 --> 00:01:38.430
In some cases, that slices the requirements somewhat,

00:01:38.430 --> 00:01:41.790
finally, right where there is, ah, common component that we've already assessed.

00:01:41.940 --> 00:01:43.600
We've already looked at We're not gonna do it again.

00:01:43.770 --> 00:01:46.440
But then, for that individual business unit,

00:01:46.770 --> 00:01:49.720
you've got to show me how you fulfill that,

00:01:49.730 --> 00:01:49.950
right?

00:01:50.000 --> 00:01:50.310
Right.

00:01:50.320 --> 00:01:52.160
Show me how you meet that procedure.

00:01:52.160 --> 00:01:56.460
Show me your specific instances of compliance with that on.

00:01:56.470 --> 00:02:00.020
That's acceptable to acquiring banks onto the carts.

00:02:00.020 --> 00:02:04.240
Games to do have multiple rocks covering a single, and it is it is.

00:02:04.250 --> 00:02:05.220
It can be.

00:02:05.510 --> 00:02:06.600
In many cases,

00:02:06.600 --> 00:02:08.889
it's often very useful to discuss that with those

00:02:08.889 --> 00:02:11.170
acquiring institutions or those card brands,

00:02:11.170 --> 00:02:15.040
and particularly since these air for very large organizations there,

00:02:15.040 --> 00:02:18.130
the kinds of organizations that can command the attention of car brands

00:02:18.130 --> 00:02:21.000
or requiring banks to have that conversation and say,

00:02:21.000 --> 00:02:22.180
This is our approach.

00:02:22.390 --> 00:02:23.400
We want to do it this way.

00:02:23.400 --> 00:02:24.800
And if you make a good case for it,

00:02:25.200 --> 00:02:27.300
usually those entities air pretty accepting of it.

00:02:27.460 --> 00:02:31.250
Yeah, I have great one from Ah ah managed hosting provider.

00:02:31.450 --> 00:02:33.080
They gave me two reports on compliance.

00:02:33.080 --> 00:02:36.410
One was for the infrastructure wants for their management services.

00:02:36.610 --> 00:02:38.970
So because you could buy them separately,

00:02:39.070 --> 00:02:41.860
so they had to separate reports of plants and that was really helpful.

00:02:41.950 --> 00:02:42.810
That's a great case.
