Security

AI agents are already being trusted with real work, but handing them raw credentials is a dangerous shortcut. That's why the next security challenge is controlling what an agent can do once it gets access.

A new kind of builder is emerging inside organizations - one that works fast, ships often, and rarely follows the instincts of a software engineer. That raises a simple question: what happens to security?

AI moves faster than your last commit - and so do hackers. Security can’t be an afterthought; it has to run alongside your code, like invisible, always-on seatbelts keeping users safe.

Every time a password is typed or a message is sent, the internet asks: ‘Can anyone else see this?’ - and without proper encryption, the answer is usually yes.

This is especially critical in AI workflows, where unchecked open source dependencies can create security blind spots.

Did a cybersecurity company really push an update to production to all of its users at once?!

Developers are now expected to take an active role in security. Here's what we've learned on how to make it easier for them.

What do you do when the developer of the mission-critical application goes missing while leaving no documentation behind? Try to hack it!

How does end-to-end encryption work, and is it genuinely secure? Paolo Insogna from Node.js explains in the upcoming interview.

The Lazy Developer pushes code to production without testing and doesn't follow security best practices. Why? Because processes and protocols slow them down. 

Privacy isn’t a feature, or an afterthought once you've built and scaled everything. It should be a day 1 priority; privacy needs to be part of the culture of a company.