Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lightning Talk: Why and how you should keep your dependencies in check #29

Open
yhtMinceraft1010X opened this issue Feb 16, 2023 · 2 comments

Comments

@yhtMinceraft1010X
Copy link
Contributor

yhtMinceraft1010X commented Feb 16, 2023

Synopsis:

A chain is only as strong as the weakest link. Sometimes, the weakest link is a dependency that you cannot manually change and have to rely on updates for. Using OWASP Dependency Check, you can keep your dependencies in check so that they do not checkmate you.

7bckg1

What's In It For You:

Take stock of all your dependencies. Know where your vulnerabilities lie, what they are and how to get rid of them.

Key Points:

  • Vulnerable dependencies are bad
  • We use many dependencies so they are difficult to keep track of manually
  • OWASP Dependency Check easily helps you out with managing these dependencies

Impact:

Start checking on your dependencies today.

Slides:

CS3282 Lightning Talk – Round B Slides Tay Yi Hsuen.pptx

@yhtMinceraft1010X yhtMinceraft1010X self-assigned this Feb 16, 2023
@yhtMinceraft1010X yhtMinceraft1010X changed the title Lightning Talk: Keep your dependencies in check with OWASP Dependency Check! Lightning Talk: Why and how you should keep your dependencies in check Feb 16, 2023
@damithc
Copy link
Contributor

damithc commented Mar 24, 2023

@yhtMinceraft1010X can you upload the round C slides?

@yhtMinceraft1010X
Copy link
Contributor Author

@yhtMinceraft1010X can you upload the round C slides?

Here are the slides. Sorry Prof.

CS3282 Lightning Talk – Round C Slides Tay Yi Hsuen.pptx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants