Can three people keep a secret only if two of them are dead, as Benjamin Franklin suggested? If you'd prefer to keep your team, let's look at handling secrets in product development.

The IT industry has a history of taking simple practices and turning them into monstrous delivery frameworks with little of the original left. We'll wind back to see what's really going on.

Analogies are terrible, but the factory one has shown some use in software engineering. Let's gird our analogous loins and take a look at how we secure this digital factory.

It can be hard to know how to change your ways of working to be more secure. Here we look at the types of security controls and what monkeys have to teach us about processes.

Your security team is overloaded. There are barely enough hours in the day to keep up with incoming requests, let alone improve ways of working. What's the cause of this?

The internet is a scary place. Thankfully we've got all our services on a private network and only accessible over a dedicated link. That's more secure, right? Right? Oh no...

We specifically requested that things must be secure. It's detailed at length in our security policies and standards on Sharepoint. Why aren't things more secure?

Your instinct for safety isn't necessarily correct. Delivering slowly isn't more secure, it's fearful, and if you're afraid of changing a system then the system is not secure

In this article we explore the concepts of quality and culture within an organisation. And, in a startling break with tradition, actually define what they are and how to change them

It's hard to manage product security if all you have is a lagging indicator of it. Reacting to data breaches is not planning ahead. How do you know that things are being built securely?