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

Lower operational risks from BlackDuck Scan #238

Open
2 tasks
sigalsax opened this issue Sep 29, 2020 · 0 comments
Open
2 tasks

Lower operational risks from BlackDuck Scan #238

sigalsax opened this issue Sep 29, 2020 · 0 comments
Milestone

Comments

@sigalsax
Copy link
Contributor

sigalsax commented Sep 29, 2020

We have several items marked as high operational risks in our blackduck scan and we should figure out why (see image)

After speaking with Ori from Sec team, he mentioned that this could result of an using an outdated version of the 3rd party that may become deprecated soon. We should figure out if we should be bumping our components and if not, what other items could be contributing to a operational risks
Screen Shot 2020-09-29 at 8.11.33 AM.png

DOD

  • Figure out what is causing a lot of operational risks
  • Fix the problem (might be a result of a soon-to-be deprecated dependency)
@Tovli Tovli added this to the R&D Boost milestone Sep 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants