So that's the end of this course.
We've looked at credential leakage and how that may occur in your repos,
but we've only just scratched the surface.
If you think of all of the other areas credentials may reside
within the various different solutions, it can seem a little daunting,
but today you've neared what is hopefully the first step in what will
become a mature credential leakage program of work.
Firstly,
I've included a link to the author's website, and from there you, can
find the most up‑to‑date version of the tool with the capabilities
and documentation, and this is hosted on GitHub. I've also included
the website for testing regular expressions. I have found this to be
a great resource.
Next, there is the public repo that I've created, and you are
welcome to use this for testing the example I provided. In that
repo are some Azure Storage key examples.
The final link is for students that are working in an enterprise and
use GitHub. Since I've covered GitHub in this course,
this vendor do have a secret scanning feature as part
of their advanced security license.
A license is required.
It's not free, but recommended to look at if it fits your
requirements. All the detail for that feature can be found on that
page. Thank you so much for attending and completing this course,
and I really hope it helps you in your career and makes the
workplace a little more secure.
And please don't forget to follow me here at Pluralsight. If you follow,
you'll get updates and information on new course releases.
Also, if you've enjoyed this course, then please take the time to leave a rating.
Thanks, and bye for now. Until next time.