WEBVTT

00:00:00.682 --> 00:00:03.903
Can I just really quickly ask you about requirement 6.6?

00:00:03.903 --> 00:00:04.788
Yes.

00:00:04.788 --> 00:00:07.489
Six-point-six has always confused me as an assessor

00:00:07.489 --> 00:00:08.467
and as the one running websites.

00:00:08.467 --> 00:00:09.516
Right.

00:00:09.516 --> 00:00:12.300
So for publicly facing web applications either put a

00:00:12.300 --> 00:00:14.888
WAF in or use automated code reviews?

00:00:14.888 --> 00:00:15.771
Is that fair?

00:00:15.771 --> 00:00:20.894
Well, so the application security assessment, the alternative to the WAF, right?

00:00:20.894 --> 00:00:22.702
I mean the goal was always,

00:00:22.702 --> 00:00:25.399
like the core of vulnerability scan isn't going to find

00:00:25.399 --> 00:00:28.072
application layer vulnerabilities or not very well,

00:00:28.072 --> 00:00:28.644
right?

00:00:28.644 --> 00:00:32.423
And the penetration test, the annual exercise is you know,

00:00:32.423 --> 00:00:32.662
cost and labor intensive.

00:00:32.662 --> 00:00:35.202
Absolutely.

00:00:35.202 --> 00:00:39.303
Right, and so this seems like it was intended to sort of split the difference.

00:00:39.303 --> 00:00:39.635
Right?

00:00:39.635 --> 00:00:42.532
We're doing this on a per-release basis, right?

00:00:42.532 --> 00:00:45.757
Some sort of application security assessment, right?

00:00:45.757 --> 00:00:47.652
Now maybe the methodology looks like code review,

00:00:47.652 --> 00:00:51.027
and maybe the methodology looks like penetration testing,

00:00:51.027 --> 00:00:51.545
right?

00:00:51.545 --> 00:00:54.062
Either could work or some combination of the two.

00:00:54.062 --> 00:00:57.678
You know, probably using some sort of automation, right?

00:00:57.678 --> 00:00:57.938
Again,

00:00:57.938 --> 00:01:02.740
because you're trying to do this on a per-release basis so it's got to be

00:01:02.740 --> 00:01:05.607
compact and sort of cost effective enough to do that.

00:01:05.607 --> 00:01:07.401
So you want some of those integrated tools that fit

00:01:07.401 --> 00:01:08.341
in the development lifecycle?

00:01:08.341 --> 00:01:11.896
Ideally, ideally, right, or the WAF.

00:01:11.896 --> 00:01:13.987
Or would you recommend both?

00:01:13.987 --> 00:01:16.423
I mean, obviously I would recommend both.

00:01:16.423 --> 00:01:19.588
I think in practice,

00:01:19.588 --> 00:01:23.604
I think there maybe a little bit sort of a scanse

00:01:23.604 --> 00:01:29.288
in terms of what they check for, what they protect against.

00:01:29.288 --> 00:01:32.399
So yeah, I mean obviously you get more protection with both.

00:01:32.399 --> 00:01:32.814
And they're quite complimentary.

00:01:32.814 --> 00:01:35.023
They really are very complimentary and this is,

00:01:35.023 --> 00:01:36.005
like we talked about,

00:01:36.005 --> 00:01:39.689
one of the major areas for exploitation for bad guys to do

00:01:39.689 --> 00:01:44.016
bad stuff so putting your protection dollars here is not

00:01:44.016 --> 00:01:45.395
usually a poor investment.

00:01:45.395 --> 00:01:50.728
So this is like, you know, this sort of 6.3, 6.5, 6.6 area is important.

00:01:50.728 --> 00:01:53.128
Is there anything else we should cover here?

00:01:53.128 --> 00:01:59.040
I mean I think there's a lot of merit to continuing to

00:01:59.040 --> 00:02:01.259
refine your software security methodology,

00:02:01.259 --> 00:02:01.701
right?

00:02:01.701 --> 00:02:05.418
What you do when one of your assessment be okay?

00:02:05.418 --> 00:02:07.440
I may say, hey, that's okay, even if it's rudimentary,

00:02:07.440 --> 00:02:11.231
even it's basic, particularly if you've come from nothing,

00:02:11.231 --> 00:02:11.673
right?

00:02:11.673 --> 00:02:15.230
But if five years on you're continuing to do those same things,

00:02:15.230 --> 00:02:18.752
that's probably not sufficient for the threats that you're facing,

00:02:18.752 --> 00:02:22.368
and I may come along and say yeah, maybe I said that was okay last year,

00:02:22.368 --> 00:02:23.793
but you need to do better.

00:02:23.793 --> 00:02:26.253
So constant evaluation of that.

00:02:26.253 --> 00:02:27.503
I think so.

00:02:27.503 --> 00:02:30.322
And if you look at the way we used to write web applications three

00:02:30.322 --> 00:02:32.050
years ago or five years ago and the way we do it now,

00:02:32.050 --> 00:02:33.408
it's actually completely different.

00:02:33.408 --> 00:02:33.686
It's very different.

00:02:33.686 --> 00:02:34.527
It's very different.

00:02:34.527 --> 00:02:35.561
We're using different frameworks and different libraries.

00:02:35.561 --> 00:02:36.948
Right.

00:02:36.948 --> 00:02:39.917
There's one thing I want to pick up on before we close this course,

00:02:39.917 --> 00:02:45.249
which is you said, you know, about teaching developers,

00:02:45.249 --> 00:02:45.963
and I've done a bit of work with Troy Hunt,

00:02:45.963 --> 00:02:46.924
as you know,

00:02:46.924 --> 00:02:49.877
and Troy does this brilliant course for developers

00:02:49.877 --> 00:02:51.887
that's called Hack Yourself First,

00:02:51.887 --> 00:02:55.816
and it shows developers how to be hacked so that you're actually

00:02:55.816 --> 00:02:57.810
teaching a developer to be a baby pen tester.

00:02:57.810 --> 00:02:58.989
Right.

00:02:58.989 --> 00:03:02.307
So you teach them how to SQL inject and really grow the application.

00:03:02.307 --> 00:03:04.264
And actually showing them how easy it is to do,

00:03:04.264 --> 00:03:07.044
I actually find one the best ways of doing security,

00:03:07.044 --> 00:03:10.977
because they think, oh, oh, oh, that was my code,

00:03:10.977 --> 00:03:15.461
I just SQL injected my own; I'm not going to let that happen ever again,

00:03:15.461 --> 00:03:15.791
right?

00:03:15.791 --> 00:03:19.110
So I'm going to really emphasize that that is a really

00:03:19.110 --> 00:03:20.515
great way of teaching developers.

00:03:20.515 --> 00:03:22.059
Excellent.

00:03:22.059 --> 00:03:22.231
Jacob,

00:03:22.231 --> 00:03:26.503
thank you for partnering with me on this theory and practice of the

00:03:26.503 --> 00:03:31.662
whole logical security stack needed in PCI DSS.

00:03:31.662 --> 00:03:33.869
It's been a really great experience,

00:03:33.869 --> 00:03:39.155
and I hope that that's drawn the strands of the real training together along

00:03:39.155 --> 00:03:41.933
with the practical experience of what happens in an assessment,

00:03:41.933 --> 00:03:45.747
what an assessor is looking for, and where people just get it wrong.

00:03:45.747 --> 00:03:47.033
Thank you.

00:03:47.033 --> 00:03:49.033
Thank you.
