WEBVTT

00:00:00.140 --> 00:00:05.310
[Autogenerated] 8.7 is one that always clients get quite confused about.

00:00:05.320 --> 00:00:07.650
It is about access to databases.

00:00:07.650 --> 00:00:07.960
Yes.

00:00:07.960 --> 00:00:11.470
And that you're not allowed to have effectively network level

00:00:11.480 --> 00:00:13.880
jQuery AD CS direct query access to the database.

00:00:13.880 --> 00:00:14.240
Right.

00:00:14.250 --> 00:00:16.740
Eso the deal is And let's because this is about

00:00:16.740 --> 00:00:19.310
database is with cardholder data.

00:00:19.320 --> 00:00:20.880
So not any database in the cardholder.

00:00:20.990 --> 00:00:21.780
Correct?

00:00:21.790 --> 00:00:22.300
Correct.

00:00:22.300 --> 00:00:23.870
So if there's a database that's just managing

00:00:23.870 --> 00:00:27.130
configurations or something like that, 8.7 doesn't apply to that,

00:00:27.140 --> 00:00:27.460
right?

00:00:27.610 --> 00:00:30.580
8.7 applies to a database containing cardholder data,

00:00:30.580 --> 00:00:32.960
and the goal is the database.

00:00:32.960 --> 00:00:36.310
Add Mons should be able to sort of connect directly to

00:00:36.310 --> 00:00:39.110
the database and and make you know, unstructured queries.

00:00:39.120 --> 00:00:41.670
Right, Because they're the database, Edmonds.

00:00:41.860 --> 00:00:47.190
But other users should go through some sort of application, right?

00:00:47.200 --> 00:00:47.550
Right.

00:00:47.890 --> 00:00:50.850
Should go through some sort of interface that,

00:00:51.340 --> 00:00:53.300
you know, restricts what they could do, right?

00:00:53.310 --> 00:00:53.530
Right.

00:00:53.530 --> 00:00:56.920
Because you don't want them making whatever queries to the database.

00:00:57.080 --> 00:01:00.450
So they couldn't just log in and do a select statement, right?

00:01:00.450 --> 00:01:00.620
Yeah.

00:01:00.630 --> 00:01:02.830
Dump out a table and walk away with it.

00:01:02.830 --> 00:01:07.260
What about giving her accounts to just let them execute stored procedures?

00:01:07.840 --> 00:01:10.320
Um not because that's that's an argument to be made to make.

00:01:10.330 --> 00:01:14.460
You know, I I think I think you could conceivably evaluate that on its merits.

00:01:14.460 --> 00:01:15.950
What are those stored procedures?

00:01:15.950 --> 00:01:16.770
What do they do?

00:01:16.780 --> 00:01:22.980
Uh, and then how do you make sure that they can only execute those right?

00:01:22.990 --> 00:01:27.780
And, you know, if you're sort of sufficiently restrictive,

00:01:27.780 --> 00:01:30.530
then then URL east meeting the intent of the requirement There.

00:01:30.540 --> 00:01:31.290
Is this a problem?

00:01:31.300 --> 00:01:32.710
Because this used to be a problem.

00:01:32.710 --> 00:01:34.610
I know that seems to be quite a big problem in assessment.

00:01:34.620 --> 00:01:35.530
Is it still a problem,

00:01:35.530 --> 00:01:37.860
or is it Sort of tends to go away as people got more mature,

00:01:37.870 --> 00:01:38.610
I think.

00:01:38.620 --> 00:01:42.710
I think, uh, you know, it splits into sort of two camps, right?

00:01:43.000 --> 00:01:48.300
Where for many organizations, they've sort of figured this out.

00:01:48.310 --> 00:01:51.150
They have limited the number of people who can directly access the database.

00:01:51.150 --> 00:01:52.200
It all goes through an application.

00:01:52.200 --> 00:01:54.970
Anyhow, um, this is good for for, you know,

00:01:54.970 --> 00:01:58.150
like, particularly sort of tech savvy or fast moving,

00:01:58.160 --> 00:02:00.080
you know, companies that are that error using,

00:02:00.090 --> 00:02:03.440
uh, you know, cloud infrastructure or suffer defined infrastructure.

00:02:03.450 --> 00:02:04.260
Um,

00:02:04.340 --> 00:02:09.070
and then if you've got sort of legacy organizations with a lot of big kind of,

00:02:09.639 --> 00:02:13.790
you know, commercial database products operating there,

00:02:13.790 --> 00:02:14.680
database infrastructure.

00:02:14.680 --> 00:02:16.450
This is harder to sort of move on.
