WEBVTT

00:00:00.000 --> 00:00:05.865
The fifth PCI DSS requirement demands that systems are

00:00:05.865 --> 00:00:08.000
protected against malicious software or malware.

00:00:08.000 --> 00:00:08.503
However,

00:00:08.503 --> 00:00:12.548
the requirement uses the term anti-virus rather than the

00:00:12.548 --> 00:00:15.669
more normal term nowadays of anti-malware.

00:00:15.670 --> 00:00:17.987
It's a function of the age of the standard that

00:00:17.987 --> 00:00:21.066
anti-virus was what you bought back in 2008.

00:00:21.066 --> 00:00:25.270
I'm going to keep saying anti-virus or AV to follow

00:00:25.270 --> 00:00:27.358
the words that the standard uses,

00:00:27.359 --> 00:00:32.628
but please use something more modern that protects against all types of malware.

00:00:32.628 --> 00:00:34.711
And I should point out that if you're using anti-malware software,

00:00:34.711 --> 00:00:39.621
just because it doesn't say anti-virus on the box,

00:00:39.621 --> 00:00:42.956
the QSA will understand that anti-malware software and

00:00:42.956 --> 00:00:45.213
anti-virus software are the same thing.

00:00:45.213 --> 00:00:47.261
Now like requirement 4,

00:00:47.261 --> 00:00:51.213
this one is also quite short with just four sub requirements.

00:00:51.213 --> 00:00:53.100
So first of all, you need to have anti-virus software.

00:00:53.100 --> 00:00:56.378
Next, you need to turn it on and make sure it's configured correctly.

00:00:56.378 --> 00:01:01.068
Thirdly, the standard requires that users can't turn it off,

00:01:01.068 --> 00:01:04.355
and finally, that you've got those relevant policies and procedures.

00:01:04.355 --> 00:01:07.631
So looking at our sample network,

00:01:07.631 --> 00:01:11.187
any system that will run malware is in scope of this requirement,

00:01:11.187 --> 00:01:16.024
which is going to be the point-of-sale systems or servers,

00:01:16.025 --> 00:01:18.920
and any computer used to manage the network.

00:01:18.921 --> 00:01:21.485
I'm going to mention those point-of-sale systems again,

00:01:21.485 --> 00:01:24.477
because I've often worked in companies where people didn't want

00:01:24.477 --> 00:01:28.601
to install AV software on the point-of-sale systems because of

00:01:28.601 --> 00:01:31.511
performance or availability concerns.

00:01:31.511 --> 00:01:34.605
But look; there have been countless attacks where malware was

00:01:34.605 --> 00:01:37.595
installed on PoS to read cardholder data out of RAM,

00:01:37.595 --> 00:01:40.593
and so any merchant that doesn't use AV on their point-of-sale

00:01:40.593 --> 00:01:44.673
systems is really asking for trouble now.

00:01:44.673 --> 00:01:49.018
Requirement 5.1 is to deploy anti-virus software on all

00:01:49.018 --> 00:01:53.948
systems commonly affected by malicious software.

00:01:53.948 --> 00:01:56.640
There are two parts to this requirement then.

00:01:56.641 --> 00:02:01.318
The first part is to work out which systems are of a type that are

00:02:01.318 --> 00:02:04.270
commonly affected by malicious software in your organization,

00:02:04.270 --> 00:02:10.639
and the second part then is to deploy anti-virus software on those systems.

00:02:10.639 --> 00:02:12.175
I used to joke that the phrase,

00:02:12.175 --> 00:02:16.676
systems commonly affected by malicious software was a euphemism for Windows,

00:02:16.677 --> 00:02:19.374
and to some extent people may still try to argue that it is actually

00:02:19.374 --> 00:02:22.085
only Windows systems that require AV software,

00:02:22.085 --> 00:02:26.419
not Macs or Linux systems and certainly not mainframes and mid-range systems.

00:02:26.419 --> 00:02:28.996
My advice is that if you can get an anti-malware

00:02:28.996 --> 00:02:31.476
software system then you should.

00:02:31.476 --> 00:02:33.239
I once had a client who was running Linux,

00:02:33.240 --> 00:02:36.244
and this was in the days when people used to claim that Linux

00:02:36.244 --> 00:02:39.450
wasn't a system that was commonly affected by malicious software

00:02:39.450 --> 00:02:41.799
and you didn't need anti-malware software.

00:02:41.799 --> 00:02:42.449
But anyway,

00:02:42.449 --> 00:02:45.579
my client was running anti-malware software and it was

00:02:45.579 --> 00:02:48.248
only that anti-malware software that alerted them to the

00:02:48.248 --> 00:02:49.684
fact they'd been compromised,

00:02:49.684 --> 00:02:53.949
because the anti-malware software detected that someone had uploaded and

00:02:53.949 --> 00:02:58.529
tried to run a malicious web shell on their main web server.

00:02:58.530 --> 00:03:01.422
But look; it's your responsibility,

00:03:01.423 --> 00:03:04.968
it's the organization's responsibility to determine what systems fall into the

00:03:04.969 --> 00:03:10.494
definition of not commonly affected and and then documented.

00:03:10.494 --> 00:03:13.299
Because although it's not part of the formal testing procedure,

00:03:13.299 --> 00:03:18.405
the QSA will want to look at your justification if you have decided some

00:03:18.405 --> 00:03:22.793
systems are not the type to be commonly affected by malicious software and that

00:03:22.793 --> 00:03:25.566
you're not going to put anti-malware software on it,

00:03:25.566 --> 00:03:30.803
and they want to do that to verify you've made this decision knowingly.

00:03:30.803 --> 00:03:33.039
The QSA is also going to check a sample of some systems

00:03:33.039 --> 00:03:36.308
that are or have anti-virus software on.

00:03:36.308 --> 00:03:39.635
They're going to probably actually look at the

00:03:39.635 --> 00:03:41.463
anti-virus console to check actually,

00:03:41.463 --> 00:03:45.081
because most anti-virus or anti-malware systems have got a console so

00:03:45.081 --> 00:03:48.022
they're going to look at the management console.

00:03:48.022 --> 00:03:50.553
There are a couple of sub requirements to 5.1.

00:03:50.553 --> 00:03:51.728
The first,

00:03:51.728 --> 00:03:57.829
requirement 5.1 .1 simply asks you to use anti-virus software that works,

00:03:57.829 --> 00:04:00.240
which means that it will detect, remove,

00:04:00.240 --> 00:04:03.543
and protect against all known types of malicious software.

00:04:03.543 --> 00:04:06.848
Now you can tell from that sentence that this requirement really was

00:04:06.848 --> 00:04:10.341
written in a data signature-based anti-virus software,

00:04:10.341 --> 00:04:12.131
because it says all known types of software,

00:04:12.131 --> 00:04:16.204
whereas hopefully now your anti-malware software will also

00:04:16.204 --> 00:04:19.146
protect you based on behavior so it will protect you

00:04:19.147 --> 00:04:21.148
against unknown types of malware.

00:04:21.149 --> 00:04:25.072
The QSA is going to observe the configuration of the anti-virus software

00:04:25.073 --> 00:04:28.587
and also check with the vendor documentation what the standard says to

00:04:28.588 --> 00:04:30.334
make sure that the AV software will detect,

00:04:30.334 --> 00:04:32.951
protect, and remove malicious applications.

00:04:32.952 --> 00:04:34.914
Personally, when I was a QSA,

00:04:34.914 --> 00:04:38.600
I always used to test the functionality of AV software by loading

00:04:38.600 --> 00:04:42.771
one of the standard EICAR test files to at least make sure it

00:04:42.771 --> 00:04:45.970
detected it and quarantined it and deleted it.

00:04:45.971 --> 00:04:51.380
Now requirement 5.1 .2 only applies to you if you have decided

00:04:51.380 --> 00:04:56.271
that some of the systems in your organization are of the type

00:04:56.271 --> 00:04:59.169
that's not commonly affected by malware.

00:04:59.169 --> 00:05:05.760
Because PCI DSS wants you to formally review that decision on a periodic basis.

00:05:05.760 --> 00:05:08.070
There's an obvious question of how long periodic is,

00:05:08.070 --> 00:05:11.491
and if you asked five QSAs, I'm sure they'd give you five different answers,

00:05:11.491 --> 00:05:15.585
but look, I'd expect this to be part of your standard vulnerability management,

00:05:15.585 --> 00:05:17.684
which we're going to look at in requirement 6.

00:05:17.684 --> 00:05:20.752
So that if during your standard vulnerability management,

00:05:20.752 --> 00:05:22.751
which is basically a monthly process,

00:05:22.751 --> 00:05:26.582
if you discover that a particular operating system is being attacked by malware,

00:05:26.582 --> 00:05:28.409
you'd review that decision.

00:05:28.410 --> 00:05:29.104
And personally,

00:05:29.104 --> 00:05:32.539
I'd also expect you to formally revisit that decision as

00:05:32.539 --> 00:05:34.448
part of your annual risk assessment,

00:05:34.448 --> 00:05:39.984
which is required by PCI DSS in requirement 12.2.

00:05:39.985 --> 00:05:40.676
Perhaps surprisingly,

00:05:40.676 --> 00:05:44.525
the testing procedure for this requirement is for the QSA to interview

00:05:44.525 --> 00:05:49.169
people involved in the decision and the ongoing evaluation.

00:05:49.170 --> 00:05:49.423
Personally,

00:05:49.423 --> 00:05:52.102
I'd always look for documented evidence that it actually

00:05:52.102 --> 00:05:54.645
happened and if there was a formal risk management process

00:05:54.646 --> 00:05:57.061
in place within an organization.

00:05:57.061 --> 00:06:01.672
I'm going to look at that risk management process to make sure this

00:06:01.672 --> 00:06:04.530
anti-virus decision making is included in it.

00:06:04.531 --> 00:06:05.978
And this is actually something that I'm going to discuss

00:06:05.978 --> 00:06:09.200
with Jacob at the end of the module.
