Indeed, we might want to use dev containers more widely in the profession. If you're developing something for the desktop you're out of luck though.
This is what you're signing up to with such ecosystems. Can't use those for backups even though people are led this way. Sure technically the data is safe on their infrastructure, but is your access to said infrastructure guaranteed? This gilded cage looks less like a gift when you loose access.
I keep being surprised at how common this kind of mistakes are. I probably shouldn't, it's actually kind of easy to fall into such traps.
TLS inspection software is indeed a very bad idea. You'd better not have them in your organisation.
This is now critical infrastructure in my opinion. It's nice to see how much progress was made.
IDEs allowing to spawn actions in the user environment are still a big security risk.
This is a nice application level sandboxing feature on Linux. We should probably have more applications use it.
Good list of hardening options indeed. That's a lot to deal with of course, let's hope this spreads and some defaults are changed to make it easier.
Interesting work from Apple and Google to have better hardening in libc++. It's nice to see it ripples through the upcoming C++26 standard as well.
Looks like an interesting tool to go with mise.
Git pre-commit hooks indeed bring nice benefits. Like everything else they're not a panacea though.
A very long read but contains lots of insights. Goes from two very famous security related failure, to highlighting how a test first approach could have helped. It then finishes with a long section on how to foster a testing culture in an organisation.
An old one but it shows quite well how social engineering works. It's often way more powerful than the technical defense you try to raise.
Interesting take. Indeed risks shouldn't be considered in isolation. They actually compound and that can add up fairly quickly.
Your digital life is secure? Good... now is it really safe? Can you recover in case of a catastrophic event?
Nice overview of where we stand regarding supply chain security. Code reuse has never been so widespread and we still have fundamental issues leading to security problems.
Unsurprisingly ends up with an advertisement for their own security tool. That said the vector used for the attack is interesting, with more npm like ecosystems available nowadays, should we expect to see more such attacks?
A good explanation of why you likely don't want a centralised package manager for your ecosystem.
Good idea to standardise this for vendors just like we do using CVEs for software components. This would definitely improve dealing with breaches.
Bad actors will go to great length to try to compromise your supply chain.