WEBVTT

00:00:00.965 --> 00:00:03.928
We should talk about what it doesn't say in 4.1 or 4.2.

00:00:03.928 --> 00:00:04.588
We should.

00:00:04.588 --> 00:00:08.209
The one that said 4.3 that's not in the standard; no, actually 4.3 is.

00:00:08.209 --> 00:00:09.038
It is now.

00:00:09.038 --> 00:00:11.183
But there should be something in there that says

00:00:11.183 --> 00:00:13.263
encryption of data over internal networks.

00:00:13.263 --> 00:00:14.615
Yes.

00:00:14.615 --> 00:00:16.231
Because the standard doesn't require you to do that.

00:00:16.231 --> 00:00:17.106
It doesn't.

00:00:17.106 --> 00:00:18.321
So as an assessor you can't assist on that.

00:00:18.321 --> 00:00:19.096
I cannot.

00:00:19.096 --> 00:00:20.211
Would you recommend it?

00:00:20.211 --> 00:00:21.241
Yes.

00:00:21.241 --> 00:00:22.174
Right.

00:00:22.174 --> 00:00:24.255
For what I hope are painfully obvious reasons.

00:00:24.255 --> 00:00:24.577
Yes.

00:00:24.577 --> 00:00:26.762
And that's actually a really good point,

00:00:26.762 --> 00:00:30.105
and again, we're back to compliance versus security.

00:00:30.105 --> 00:00:32.999
There've been many attacks and the large payment processor in the U.S.

00:00:32.999 --> 00:00:36.686
that was about five or six years ago, that was an attack where,

00:00:36.686 --> 00:00:39.223
you know, if they'd been encrypting data,

00:00:39.223 --> 00:00:43.659
it wouldn't have got taken from; it was an on-the-wire attack basically.

00:00:43.659 --> 00:00:46.027
So off the network interface guard,

00:00:46.027 --> 00:00:47.577
would they had been using encryption at the TLS level

00:00:47.577 --> 00:00:48.900
they would've never gotten the data.

00:00:48.900 --> 00:00:49.179
Indeed.

00:00:49.179 --> 00:00:53.247
And so encrypting data on local networks now is more important.

00:00:53.247 --> 00:00:56.239
One of the things I always talk about with people is you know,

00:00:56.239 --> 00:01:00.583
when I started doing, well, you've been an assessor since before PCI,

00:01:00.583 --> 00:01:01.171
haven't you?

00:01:01.171 --> 00:01:02.416
Yes, I have.

00:01:02.416 --> 00:01:04.725
And we've seen that attacks used to be against stored cardholder data,

00:01:04.725 --> 00:01:07.249
because people used to store cardholder data.

00:01:07.249 --> 00:01:08.437
Right.

00:01:08.437 --> 00:01:10.837
And the attacks are now all about data in transit,

00:01:10.837 --> 00:01:16.579
whether it's memory scraping malware, or whether it's network traffic.

00:01:16.579 --> 00:01:19.065
So that's where the attack is, our defense has to be encrypting on the network.

00:01:19.065 --> 00:01:22.578
Indeed, indeed, you know, or even at the contact layer,

00:01:22.578 --> 00:01:27.284
right, so that you can protect against those memory scraping attacks.

00:01:27.284 --> 00:01:30.273
Don't let the relative lengths of the requirements fool you.

00:01:30.273 --> 00:01:36.481
Requirement is probably more important at this point than requirement 3.

00:01:36.481 --> 00:01:40.613
Yeah, because the attack is against in transmission, not against storage.

00:01:40.613 --> 00:01:41.573
Against the stored repository, yep.

00:01:41.573 --> 00:01:41.812
That's great.

00:01:41.812 --> 00:01:44.503
Anything else we should talk about, about requirement 4?

00:01:44.503 --> 00:01:45.741
I think that's the short of it.

00:01:45.741 --> 00:01:50.451
Yeah, it's a short requirement, but really involved.
