as bad as things have gotten in the past 4 days, they are going to get a lot worse before they get better. security leaders, never let a crisis go to waste: please go to your boards and ask for help right now. not for ai, for the basics. (we need to hold on for ~18 months.)
"How can we possibly handle all the AI-induced vuln-pocalypse"? Do security fundamentals well and quickly. How fast can you push a patch? Reduce your surface area as much as possible. Know your inventory (sboms!) All the things that were good practice still are.
Hi! Grype 0.60.0 is out. This release disables CPE matching for Javascript packages by default to reduce false positives, and improves --by-cve report performance. Details here:
https://t.co/EUfEtnxH7P
🚨 Big news today, we have open sourced the pipeline that builds the Grype vulnerability database. Now you can run your own database and implement your own data sources.
Check out the details here:
https://t.co/JPbqfNfrcp
@joshbressers Curious why Solarwinds isn't included? IMO that was a big wake-up call that motivated actors could leverage highly trusted vendors calling into question a lot of aspects of the supply chain and how vendor and consumer security expectations should adapt.
Excited to pair up with @PinkyyRavi from @weaveworks today at 2pm ET to talk about @fluxcd and its connection to @SyftProject! 💕
Here's the link to register: https://t.co/BVZDnrFcbz Come hang out!
I will be talking about @SyftProject
and @GrypeProject on March 1st 2022:
https://t.co/iCSBqS0UKB
The meetup is online and usually German - but we can switch to English if we have English attendees.
The #log4j security vulnerability provides ideal conditions for a computer worm to propagate. This @securityblvd article by @joshbressers explores the dangers of that happening. https://t.co/UJ2QH5Vr2Q #security
Example project using @Goreleaser, @projectsigstore cosign and @SyftProject to publish keyless-signed releases + SBOMs!
Feel free to use it as base, as well as propose improvements :)
https://t.co/H0DcjMGpia