WEBVTT

00:00.000 --> 00:05.595
>> The OWASP Web Security
Testing Guide or WSTG.

00:05.595 --> 00:08.190
Our learning objectives
are to identify why

00:08.190 --> 00:11.430
the WSTG is important
when conducting

00:11.430 --> 00:14.430
web application security
testing and recognize

00:14.430 --> 00:19.035
how the OWASP Top 10
and WSTG intersect.

00:19.035 --> 00:20.820
A little bit of history,

00:20.820 --> 00:22.260
as you can tell, I like history.

00:22.260 --> 00:23.010
>> I think it's important.

00:23.010 --> 00:25.920
>> I think it's important to
see how these things develop,

00:25.920 --> 00:28.350
how the OWASP Top 10 develops,

00:28.350 --> 00:30.600
how the WSTG develops.

00:30.600 --> 00:32.930
But obviously, both
of these documents

00:32.930 --> 00:34.880
have been around for a while,

00:34.880 --> 00:39.900
the WSTG being around
for almost 20 years.

00:39.900 --> 00:42.825
But it was first
released in 2004.

00:42.825 --> 00:44.905
OWASP started in 2001.

00:44.905 --> 00:47.405
A few years later they come
out with the first version

00:47.405 --> 00:49.910
of the web security
testing guide.

00:49.910 --> 00:52.685
That's gone through
other iterations,

00:52.685 --> 00:54.910
1.1, 2.0,

00:54.910 --> 00:57.330
all the way up to 4.2,

00:57.330 --> 00:59.660
4.2 being released in

00:59.660 --> 01:02.615
December of 2020, so
relatively recently.

01:02.615 --> 01:06.370
They're also developing
version 5.0.

01:06.370 --> 01:09.120
The cool thing is when things

01:09.120 --> 01:11.975
are being developed,
this fifth version,

01:11.975 --> 01:15.480
you can actually see what's
being developed in "Real

01:15.480 --> 01:17.930
time" It's on the OWASP website

01:17.930 --> 01:20.150
to stable version being 4.2,

01:20.150 --> 01:22.220
meaning we're not going
to change anything.

01:22.220 --> 01:23.780
You can see what's going on with

01:23.780 --> 01:26.375
Version 5 on the OS website,

01:26.375 --> 01:29.780
but just keep in mind that
the content may change.

01:29.780 --> 01:31.250
As you can see here, it says,

01:31.250 --> 01:33.960
"The content may
change frequently."

01:33.960 --> 01:35.540
I typically go to

01:35.540 --> 01:39.140
4.2 just because I
know that it's stable.

01:39.140 --> 01:42.335
If I'm interested in just
looking at what might be new,

01:42.335 --> 01:44.840
maybe some new attack

01:44.840 --> 01:47.765
vectors or new ways
to test something.

01:47.765 --> 01:51.000
I'll look at version 5.0.

01:51.080 --> 01:55.070
Layout, we have the
introduction which goes over

01:55.070 --> 01:56.900
the prerequisites of testing

01:56.900 --> 01:59.015
and scope of as a
penetration tester,

01:59.015 --> 02:01.865
you should always know
what your scope is.

02:01.865 --> 02:05.375
Then we talk about the
OS testing framework

02:05.375 --> 02:06.740
and talks a little bit about

02:06.740 --> 02:09.185
the software
development lifecycle.

02:09.185 --> 02:11.885
As you can see, OWASP
likes to do a lot,

02:11.885 --> 02:13.340
not just pen testing,

02:13.340 --> 02:16.400
but also software
development as well.

02:16.400 --> 02:18.665
It's geared towards both
as we talked about,

02:18.665 --> 02:20.270
penetration testers,

02:20.270 --> 02:22.925
but also software
developers as well.

02:22.925 --> 02:28.375
SLDC being a huge component
of software development.

02:28.375 --> 02:31.670
As pen testers, we should
also be involved with

02:31.670 --> 02:36.220
testing in nearly all
aspects of the SLDC.

02:36.220 --> 02:38.685
Web application
security testing,

02:38.685 --> 02:40.870
part of the WSTG

02:40.870 --> 02:43.775
is we're going to spend
the majority of our time.

02:43.775 --> 02:45.470
This is the meat and potatoes.

02:45.470 --> 02:47.150
This is where we
see how to test for

02:47.150 --> 02:49.370
particular types of
vulnerabilities.

02:49.370 --> 02:51.290
Reporting. That may be

02:51.290 --> 02:53.240
very different depending
on where you work.

02:53.240 --> 02:55.325
If you're a consultancy,

02:55.325 --> 02:57.860
if you work for an
internal pen testing team,

02:57.860 --> 03:00.625
you're reporting may
be vastly different.

03:00.625 --> 03:02.510
There may be different

03:02.510 --> 03:04.370
ways that you want
to report things.

03:04.370 --> 03:06.695
There may be different
requirements

03:06.695 --> 03:07.970
depending on your vertical

03:07.970 --> 03:09.575
that you have to report things.

03:09.575 --> 03:14.300
But the WSTG has some information
on reporting generally.

03:14.300 --> 03:16.910
The appendix, don't
skip the appendix.

03:16.910 --> 03:18.470
There is some gold, there's

03:18.470 --> 03:23.125
some great information in
the appendix of the WSTG.

03:23.125 --> 03:28.460
In the WSTG scenarios are
referenced by their identifier.

03:28.460 --> 03:31.490
Version, in some cases,

03:31.490 --> 03:33.050
as you can see in this image,

03:33.050 --> 03:34.475
it doesn't have the version.

03:34.475 --> 03:36.305
Maybe like 4.2,

03:36.305 --> 03:39.915
the category and
then the number.

03:39.915 --> 03:44.750
This has had a test HTTP
methods and WSTG 0,

03:44.750 --> 03:48.310
6, so category and number
without the version.

03:48.310 --> 03:51.240
Who uses the WSTG?

03:51.240 --> 03:55.150
In the bug bounty world
I've used this a lot.

03:55.150 --> 04:00.200
In particular, companies,
they may require that you

04:00.200 --> 04:02.300
use or ask that you use

04:02.300 --> 04:05.615
the WSTG in your
testing methodology.

04:05.615 --> 04:07.580
Obviously bug bounty hunters and

04:07.580 --> 04:11.540
penetration testers being
one and the same in many,

04:11.540 --> 04:12.740
many respects,

04:12.740 --> 04:14.700
being somewhat different
in other respects.

04:14.700 --> 04:17.590
But when looking at the WSTG,

04:17.590 --> 04:19.460
if we're testing
web application,

04:19.460 --> 04:22.535
if I'm a pen tester or
a bug bounty hunter,

04:22.535 --> 04:26.045
I'm very interested in
ways of testing that.

04:26.045 --> 04:28.805
More formulaic for
penetration testing,

04:28.805 --> 04:31.650
I'm going to have to deliver
a report to a customer.

04:31.650 --> 04:35.825
I can definitely reference
the WSTG as something,

04:35.825 --> 04:37.730
as a tool or you
are utility that I

04:37.730 --> 04:40.720
used in my testing methodology.

04:40.720 --> 04:42.500
Developers can also use this as

04:42.500 --> 04:44.390
well developed some
developers that I've met are

04:44.390 --> 04:48.920
very interested in the web
application security space

04:48.920 --> 04:51.860
and when to test their
own applications.

04:51.860 --> 04:53.600
Developers want to understand

04:53.600 --> 04:55.040
how these vulnerabilities
come about,

04:55.040 --> 04:57.260
how we as penetration testers or

04:57.260 --> 05:00.890
bug bounty hunters,
attack web applications.

05:00.890 --> 05:03.470
Developers are interested
in this as well.

05:03.470 --> 05:05.965
We'll read the WSTG.

05:05.965 --> 05:10.665
How did the OWASP Top 10
and the WSTG intersect?

05:10.665 --> 05:11.960
As you can see here,

05:11.960 --> 05:13.310
the OWASP Top 10,

05:13.310 --> 05:17.765
A4, as you can tell I told
you before, I like XXE.

05:17.765 --> 05:21.175
The WSTG maps to that.

05:21.175 --> 05:28.455
WSTG, INPV-07 is how to
test for XML injections.

05:28.455 --> 05:32.340
In every one of the Top 10
we can reference or turn to

05:32.340 --> 05:36.095
the WSTG in our
testing methodology

05:36.095 --> 05:39.630
for that particular
type of vulnerability.

05:39.980 --> 05:44.405
As I said before, don't skip
the appendix of the WSTG.

05:44.405 --> 05:46.640
They give you a
lot of resources,

05:46.640 --> 05:49.670
they give you great tools
that you can use for testing.

05:49.670 --> 05:51.535
They give you suggested reading.

05:51.535 --> 05:52.975
I love reading.

05:52.975 --> 05:54.530
If you want to get
into this space,

05:54.530 --> 05:55.820
if you're interested
in this space,

05:55.820 --> 05:59.250
it's an older book, but
I've referenced it here.

05:59.250 --> 06:02.975
The web application hackers
handbook Version 2 is

06:02.975 --> 06:08.105
the physical Bible or you can
get it on Kindle or e-book.

06:08.105 --> 06:10.730
You can get that as
well. It's a huge book,

06:10.730 --> 06:13.760
but that's a great resource
for those of us who

06:13.760 --> 06:16.564
are in the web application
hacking space.

06:16.564 --> 06:18.950
It talks about different
fuzzing vectors,

06:18.950 --> 06:21.845
different resources you
can use for fuzzing,

06:21.845 --> 06:24.620
as well as encoded injections.

06:24.620 --> 06:27.665
I talked about Web Application
Firewall as before.

06:27.665 --> 06:32.030
Sometimes using encodings
a way to bypass a WAF.

06:32.030 --> 06:36.565
They discussed that in
the appendix of WSTG.

06:36.565 --> 06:39.375
Not to be missed, don't
miss the appendix.

06:39.375 --> 06:40.790
In summary, we've discussed

06:40.790 --> 06:43.340
>> why the WSTG is important and

06:43.340 --> 06:47.525
>> how the OWASP Top
10 and WSTG intersect.

06:47.525 --> 06:49.820
While we go through
each of these modules,

06:49.820 --> 06:51.770
we are not only going to
be looking at the Top 10,

06:51.770 --> 06:54.065
we're going to be
looking at the WSTG

06:54.065 --> 06:57.915
and I encourage you
to look at that.

06:57.915 --> 06:59.220
We talk about
community injection,

06:59.220 --> 07:02.220
SQL injection to
look at the WSTG,

07:02.220 --> 07:04.440
look at the testing
methodology that they

07:04.440 --> 07:08.890
recommend and use that to
help you along the way.

