WEBVTT

00:00:01.140 --> 00:00:03.960
[Autogenerated] requirement 12.3 is a very strange one.

00:00:04.340 --> 00:00:08.890
It requires there to be what the DSS calls usage policies for

00:00:08.890 --> 00:00:12.260
something it refers to as critical technologies.

00:00:12.840 --> 00:00:13.540
Honestly,

00:00:13.640 --> 00:00:17.230
when most people think about what a critical technology is in

00:00:17.230 --> 00:00:19.600
respect to the security of payment card data,

00:00:19.730 --> 00:00:24.270
they think of firewalls of hardware, security modules and payment systems.

00:00:24.940 --> 00:00:29.080
And, annoyingly, if you look at the PC IDE CSS glossary,

00:00:29.270 --> 00:00:32.560
critical technology is sort of defied like that.

00:00:32.630 --> 00:00:35.960
It talks about systems or technologies that are essential for

00:00:35.960 --> 00:00:38.860
business operations or security functions.

00:00:39.940 --> 00:00:44.410
But this requirement isn't anything to do with that

00:00:44.420 --> 00:00:46.750
type of critical technologies.

00:00:47.540 --> 00:00:51.970
It should really say something like and use the technologies which,

00:00:52.010 --> 00:00:56.870
if not correctly used by people, can create or course security vulnerabilities.

00:00:57.740 --> 00:01:00.050
And as the standard says in the note,

00:01:00.440 --> 00:01:04.220
critical technologies are things like email laptops,

00:01:04.230 --> 00:01:08.930
USB drives on Web browsing, so the core end user computing.

00:01:08.930 --> 00:01:10.550
In most organizations,

00:01:11.240 --> 00:01:16.190
the requirement is that the organization developed usage policies for

00:01:16.190 --> 00:01:19.550
these types of technologies to minimize the risk of them,

00:01:19.550 --> 00:01:21.560
causing a security vulnerability.

00:01:22.440 --> 00:01:26.720
The standard gets pretty and almost annoyingly prescriptive about

00:01:26.720 --> 00:01:29.110
the 10 things that need to be in the usage policy.

00:01:29.220 --> 00:01:31.040
But before we go through these,

00:01:31.200 --> 00:01:34.650
I want to remind you of something I said at the beginning of Requirement 12.

00:01:35.540 --> 00:01:40.030
Be careful that you make sure these requirements only apply to people and

00:01:40.030 --> 00:01:43.010
technology and scope of the PC IDE AD CS requirements.

00:01:43.180 --> 00:01:48.070
So it might not be that all the critical technology using your

00:01:48.070 --> 00:01:51.850
organization and it might not be all of the people.

00:01:52.340 --> 00:01:54.380
So with that very clearly in your mind,

00:01:54.440 --> 00:02:00.350
let's look at the 10 things that PC IDE CSS wants to be in the usage policies.

00:02:02.240 --> 00:02:07.110
The first is the use of all of the defined critical technologies has approved.

00:02:07.230 --> 00:02:09.759
The guidance implies that such approval needs to be

00:02:09.759 --> 00:02:11.750
actually on an individual basis.

00:02:12.240 --> 00:02:12.960
Secondly,

00:02:13.340 --> 00:02:16.500
the policy needed to find that the use of technology needs to

00:02:16.510 --> 00:02:20.050
be a tied to an authenticated user next.

00:02:20.440 --> 00:02:24.390
And remember these error requirements for a policy that a register is kept of

00:02:24.390 --> 00:02:28.060
who has been authorized to use what critical technology.

00:02:28.540 --> 00:02:31.960
Now, of course, this register could be something like your directory services,

00:02:32.120 --> 00:02:35.790
where the technology, like the use of email or the use of Web browsing,

00:02:35.830 --> 00:02:36.970
is actually provisioned.

00:02:37.640 --> 00:02:40.900
The fourth requirement for the policy is that some sort of way of

00:02:40.900 --> 00:02:44.540
tying physical devices to owners it is implemented on.

00:02:44.540 --> 00:02:47.200
The next thing that the policy has to define is how

00:02:47.200 --> 00:02:48.800
the technology should be used.

00:02:48.890 --> 00:02:52.370
So a traditional, acceptable usage policy is what's needed here.

00:02:52.940 --> 00:02:57.250
The six thing that the policy has to define is the physical location.

00:02:57.360 --> 00:03:01.410
Where such technologies could be used in the seventh is to maintain a

00:03:01.410 --> 00:03:04.690
list of company approved products such as phones,

00:03:04.800 --> 00:03:07.840
laptops and USB devices that can be used.

00:03:07.970 --> 00:03:13.060
And also the policy must prohibit the use of non approved technologies.

00:03:14.140 --> 00:03:15.360
We're almost at the end now,

00:03:15.440 --> 00:03:18.050
and you may be surprised to see the next to policy

00:03:18.050 --> 00:03:21.330
requirements because at first reading, you might think hang on.

00:03:21.570 --> 00:03:24.250
They should have already been covered off Been Requirement eight.

00:03:25.140 --> 00:03:28.560
They are both concerned with the critical technology of remote access.

00:03:29.140 --> 00:03:32.770
12.3 point eight wants to make sure that remote access

00:03:32.770 --> 00:03:36.470
sessions are disconnected after they've been idle for an

00:03:36.470 --> 00:03:39.250
organization defined period of in activity.

00:03:39.940 --> 00:03:43.880
This isn't just a policy requirement because the testing procedures says the

00:03:43.880 --> 00:03:46.750
QoS A is going to look at remote access configurations,

00:03:47.340 --> 00:03:50.710
and 12.3 point nine is concerned with remote access

00:03:50.710 --> 00:03:52.350
for vendors and business partners,

00:03:52.740 --> 00:03:55.410
and you may think that this was already comprehensively

00:03:55.410 --> 00:03:57.870
covered in requirement 8.1 point five.

00:03:58.440 --> 00:04:03.060
But that requirement was about the user ID used for remote access on that

00:04:03.190 --> 00:04:05.970
that user IDE should only being able to error needed.

00:04:06.340 --> 00:04:09.530
Where is this requirement is about only having the remote

00:04:09.540 --> 00:04:12.760
access technology enabled when needed.

00:04:13.740 --> 00:04:17.440
This has been a massive course of data breaches at retailers with criminals.

00:04:17.440 --> 00:04:20.600
Been able to access every single store in a retailer's estate,

00:04:20.700 --> 00:04:23.670
using the same remote access technology in credentials.

00:04:24.340 --> 00:04:26.470
But on the other hand, where you've got managed,

00:04:26.470 --> 00:04:28.290
I t service providers there,

00:04:28.290 --> 00:04:31.060
the people with the control of the remote access technology.

00:04:31.440 --> 00:04:35.300
So here is really vital you take a sensible approach discussion with your

00:04:35.300 --> 00:04:39.720
QoS a on maybe Go back over requirement 8.1 point five,

00:04:39.730 --> 00:04:42.400
where we discuss some of the problems with remote access

00:04:42.410 --> 00:04:45.450
technology and outsourced IT providers.

00:04:46.940 --> 00:04:51.120
The last critical use policy is another is concerned with remote access,

00:04:51.310 --> 00:04:54.760
but on this occasion is concerned with remote access that's given to

00:04:54.760 --> 00:04:59.620
cardholder Data on the requirement is that anyone accessing cardholder

00:04:59.620 --> 00:05:05.240
data must not be able to copy move or store it locally unless that's

00:05:05.240 --> 00:05:06.650
been specifically authorized.

00:05:06.730 --> 00:05:08.670
And if it is allowed,

00:05:08.790 --> 00:05:11.780
the policy needs to specify that it's copy to an environment

00:05:11.870 --> 00:05:14.960
where all the PC GUID CSS requirements apply.

00:05:16.140 --> 00:05:19.310
Now the QoS a has got lots to check in this requirement

00:05:19.440 --> 00:05:21.450
on the majority of its documentation.

00:05:21.840 --> 00:05:26.010
But some of the requirements also specify the QoS A needs to look at settings,

00:05:26.120 --> 00:05:26.960
for example,

00:05:26.970 --> 00:05:29.590
how remote access software is configured or where

00:05:29.590 --> 00:05:31.050
the requirement Astra Register.

00:05:31.050 --> 00:05:33.270
The QoS is going to look for that register.

00:05:33.640 --> 00:05:34.500
But firstly,

00:05:34.600 --> 00:05:39.010
because the scope of what's determined to be a critical technology is

00:05:39.010 --> 00:05:41.950
something the organization needs to workout itself,

00:05:42.160 --> 00:05:46.070
the QoS is going to look to see where this has been defined on then,

00:05:46.090 --> 00:05:51.850
how that definition ties in with the requirement for a risk assessment in 12.2.

00:05:53.140 --> 00:05:55.230
Finally, as I said at the beginning,

00:05:55.520 --> 00:05:59.650
don't fall into the trap of using this as the benchmark for the

00:05:59.650 --> 00:06:03.030
whole end user computing acceptable usage policy.

00:06:03.210 --> 00:06:07.110
Will your entire organization remember that this

00:06:07.110 --> 00:06:10.770
requirement only applies to critical technology on people

00:06:10.780 --> 00:06:13.160
who are in scope of the PC IDE S s.

00:06:13.230 --> 00:06:16.690
In many cases, we have a lock down cardholder environment.

00:06:16.850 --> 00:06:20.500
The answer is a number of policy statements that say technology,

00:06:20.500 --> 00:06:21.240
ex wife said,

00:06:21.240 --> 00:06:26.650
like USB drives are not permitted to be used in the cardholder data environment.
