3 ms·
Oh fun! At my employer the "security team" misunderstands that criticality score and takes it as a "vulnerability score". Everything scoring high is a security
by Tomte 4y ago
Oh fun! At my employer the "security team" misunderstands that criticality score and takes it as a "vulnerability score". Everything scoring high is a security risk, everything scoring low is secure.
- transpute 4y agoOMG :) OpenSSF will love that story! Straight into the documentation Hall of Fame. They can check out the Securing Critical Projects working group, https://github.com/ossf/wg-securing-critical-projects https://github.com/ossf/wg-securing-critical-projects
- Tomte 4y agoThey link to that page in their documentation. I can only assume that they misunderstand this: > 1. Identify critical open source software (OSS) projects. > 2. Secure those projects. Not as "those projects are widely in use, we should really make sure that they are looked at", but as "we have identified those projects as insecure and will secure them".