Hello, and a very warm welcome to this course,
Protective Technology with Dockle.
My name is Peter Mosmans, and I'm a lead penetration tester,
as well as DevSecOps consultant.
This is a different course than usual.
This one revolves around a single tool.
It contains lots of demos, lots and lots of demos.
So, Dockle, what exactly is it?
Dockle is a container image linter focused around security,
and it helps you to build best‑practice Docker images.
In my humble opinion,
one of the things that makes Dockle so great is how easy it is to
integrate in your continuous integration environments.
Within no time,
you'll be up and running and performing Dockle
security scans over your Docker images.
This is what we're going to do in this course.
In other words, Dockle is very easy to use.
It was originally created by Tomoya Amachi in 2019 and
written in the Go programming language.
Thank you, Tomoya, for such a great tool.
The source code of Dockle is licensed under the Apache License.
You can build it from source,
but there are also multiple binaries available for multiple platforms,
as we shall see.
And, even better, there are Docker images available,
which makes it very easy to use in continuous integration environments.
The source code and more information can be found on GitHub
under the address goodwithtech/dockle.
In order to make a good use case to start using Dockle,
let's take a brief look at the NIST Cybersecurity Framework.
This is a framework developed with the goal to reduce cyber risks.
It is voluntary guidance.
As you can see, it has multiple functions,
identify, protect, detect, respond, and recover.
Dockle fits under the protect function of the Cybersecurity Framework.
If you want to know more about the NIST Cybersecurity Framework,
I'd urge you to take a look at Pluralsight where there are
several courses available on this subject.
For Dockle, we're interested in the protect function.
That function itself is divided into multiple categories.
We have identity management and access control,
awareness and training, data security,
information protection processes and procedures,
maintenance, and protective technology.
Protective technology?
Yes, Dockle.
Subcategories that are applicable for Dockle are,
number 3,
the principle of least privilege is incorporated by configuring
systems to provide only essential capabilities,
and 4, communications and control networks are protected.
This is what you can achieve by using Dockle.
Enough about the theory about why you should use it. Let's
immediately start with a demo about the basic usage.