Programming Throwdown cover image

158: Software Supply Chain with Bill Manning

Programming Throwdown

00:00

The Worst Part of What You Do as a Security Analyst

Security analysts should always be hands-on deck but contextually you're actually not affected by this because you're not using that function interesting so we actually provide the information now is it applicable or is it not applicable perfect example. What made solar winds so dangerous was is that when it went in and affected 18 000 customers the actual issue didn't happen for 14 days It actually had a timer that when the software started it waited for 14 days in wait before it did its attack. The proper way to do this is at the developer level and then the build level rightYou kind of go through and if you follow your sdlc  you should actually have it at every phase dev qa staging

Transcript
Play full episode

The AI-powered Podcast Player

Save insights by tapping your headphones, chat with episodes, discover the best highlights - and more!
App store bannerPlay store banner
 Get the app