WEBVTT

00:00:00.172 --> 00:00:01.374
Okay, fine, right.

00:00:01.374 --> 00:00:03.240
We know that failures here are a massive cause of compromise.

00:00:03.240 --> 00:00:08.410
Let's talk more about 6.5 so that's the anything that faces the web.

00:00:08.410 --> 00:00:09.617
Right.

00:00:09.617 --> 00:00:11.295
Yes, it says the OWASP Top 10.

00:00:11.295 --> 00:00:14.201
Should you just look at the OWASP Top 10 or should you look at more?

00:00:14.201 --> 00:00:16.733
Well, I mean I think the OWASP Top 10 is sort of the entry point.

00:00:16.733 --> 00:00:19.556
Underneath each of those top-10 vulnerabilities,

00:00:19.556 --> 00:00:23.617
if you actually go to the OWASP site, there's a whole wealth of knowledge,

00:00:23.617 --> 00:00:27.525
how these vulnerabilities sort of get exploited in the wild,

00:00:27.525 --> 00:00:29.194
how do you test for this,

00:00:29.194 --> 00:00:32.010
how do you develop to avoid these things in the first place?

00:00:32.010 --> 00:00:35.555
And so if you can go, you know,

00:00:35.555 --> 00:00:37.832
plumb some of that and then incorporate that into your practices

00:00:37.832 --> 00:00:41.720
to say here's how we check for this; here's how we make sure we

00:00:41.720 --> 00:00:43.527
don't do it in the first place.

00:00:43.527 --> 00:00:45.733
You know, that's useful, right?

00:00:45.733 --> 00:00:48.618
But again, if you've just got the OWASP Top 10 checklist,

00:00:48.618 --> 00:00:50.862
right, I checked for cross-site scripting,

00:00:50.862 --> 00:00:51.302
check!

00:00:51.302 --> 00:00:51.776
Right?

00:00:51.776 --> 00:00:53.673
I didn't find any.

00:00:53.673 --> 00:00:54.171
Fine.

00:00:54.171 --> 00:00:57.662
So obviously this is a Pluralsight course.

00:00:57.662 --> 00:00:58.592
Right.

00:00:58.592 --> 00:01:00.193
Pluralsight has loads of great training for developers,

00:01:00.193 --> 00:01:06.206
but in terms of the DSS, there's a requirement that developers are trained,

00:01:06.206 --> 00:01:08.105
as their annual requirement.

00:01:08.105 --> 00:01:09.334
Yes.

00:01:09.334 --> 00:01:10.200
What are you looking for?

00:01:10.200 --> 00:01:13.139
How are you evidencing that and what are you looking for?

00:01:13.139 --> 00:01:15.712
So I want to see, I want to see two things.

00:01:15.712 --> 00:01:18.429
I want to see the materials, right, or you know,

00:01:18.429 --> 00:01:21.358
if the materials are sort of not public,

00:01:21.358 --> 00:01:21.616
right?

00:01:21.616 --> 00:01:24.217
If they have to pay for it and they don't want to give me access,

00:01:24.217 --> 00:01:27.651
then I at least want some notion of what it contains,

00:01:27.651 --> 00:01:28.004
right?

00:01:28.004 --> 00:01:30.859
Maybe it's just I observe some of it on site while

00:01:30.859 --> 00:01:32.788
somebody who has access to it can show me,

00:01:32.788 --> 00:01:34.806
right, rather than, you know, whatever, right?

00:01:34.806 --> 00:01:36.776
Or if they're developing their own materials

00:01:36.776 --> 00:01:41.272
in-house then I want to see what is it, what does it contain?

00:01:41.272 --> 00:01:45.355
And then is that relevant to their application, right?

00:01:45.355 --> 00:01:47.527
And if they've got a lot of, if they're talking about OWASP,

00:01:47.527 --> 00:01:50.392
you know, web vulnerabilities and then everything is developed on,

00:01:50.392 --> 00:01:52.280
you know, IBM mid-range systems, right,

00:01:52.280 --> 00:01:56.518
then maybe we've sort of missed the boat here.

00:01:56.518 --> 00:01:58.727
Are you looking for just evidence that they like spent three hours

00:01:58.727 --> 00:02:02.218
being trained or would you like to do a skill assessment of like some

00:02:02.218 --> 00:02:04.384
proof that they've actually learned something?

00:02:04.384 --> 00:02:06.355
Some sort of skill assessment would be good,

00:02:06.355 --> 00:02:09.754
and then obviously like which developers attended this training,

00:02:09.754 --> 00:02:10.256
right?

00:02:10.256 --> 00:02:14.013
So some sort of attendance record, and yeah,

00:02:14.013 --> 00:02:16.347
I mean ideally some sort of skill assessment or some

00:02:16.347 --> 00:02:18.431
sort of demonstration of knowledge.

00:02:18.431 --> 00:02:18.951
Sometimes that,

00:02:18.951 --> 00:02:22.524
or you know at least the converse shakes out in

00:02:22.524 --> 00:02:25.264
sort of other pieces of evidence, right?

00:02:25.264 --> 00:02:27.810
If the code reviews, if the vulnerability scans,

00:02:27.810 --> 00:02:33.992
if the pen test results, you know, show a lot of application vulnerability,

00:02:33.992 --> 00:02:36.634
that tells me that the training isn't really doing anything.

00:02:36.634 --> 00:02:39.129
Can you compensate and control any of this?

00:02:39.129 --> 00:02:43.184
Conceivably, sure, right?

00:02:43.184 --> 00:02:49.187
I guess I don't know how you compensate for a lack of developer training.

00:02:49.187 --> 00:02:50.672
I could imagine, well,

00:02:50.672 --> 00:02:53.538
I could imagine a situation where if you've maybe

00:02:53.538 --> 00:02:56.339
outsourced the development effort to a third party over

00:02:56.339 --> 00:02:57.833
which you don't have a lot of control,

00:02:57.833 --> 00:03:01.291
but then you're doing some sort of security assessment on the

00:03:01.291 --> 00:03:08.043
deliverable that they produced for you, maybe that's a compensating control.

00:03:08.043 --> 00:03:12.737
As far as actually testing at some level in some capacity for

00:03:12.737 --> 00:03:15.198
vulnerabilities in your software development effort,

00:03:15.198 --> 00:03:15.657
right,

00:03:15.657 --> 00:03:17.974
or in the work product that you create and having some

00:03:17.974 --> 00:03:20.191
meaningful software security methodology,

00:03:20.191 --> 00:03:23.084
I mean, you know,

00:03:23.084 --> 00:03:26.419
maybe the shape it takes for your organization doesn't

00:03:26.419 --> 00:03:31.008
fit the kind of conventional mold, maybe you don't have a lot of people,

00:03:31.008 --> 00:03:34.562
but you need to do something here.
