Blog
125 - Self service tooling
I have long contended that one of the indicators of maturity in an organisation, and one of the drivers of efficiency is the ability of teams to self-service.
124 - Our tools are evolving
Security tooling has always been a little... peculiar.
123 - Developers are not the enemy
If you are a developer, you need to assume that your users are not the enemy, that they want to get the job done in the safest way possible. If you write code for other developers, you need to assume the same thing.
122 - Learning from the past, not dwelling in it
I believe that we fail to learn well enough from the past.
121 - Can we tell the future
For those who don't know, I started a new job recently. Leaving behind my contractor ways, I've returned to the civil service to help build security capabilities across government. Part of that role includes setting up better situational awareness and horizon scanning for Government, a better ability to know what is happening both inside government and outside, in security and technology.
120 - How we communicate
How we communicate really matters. If we want to be taken seriously, we have to be sure that everyone hears us communicate clearly and simply.
119 - The security of comms platforms
[Apologies for missing last week. I had some personal news that meant that my weekend was taken up with a lot of other stuff, and the newsletter dropped off my radar.]
118 - Do you need a threat model?
When I see people talking about threat modelling, they can be referring to two totally different kinds of activities.
117 - What is the inside threat?
Who can you trust, or sometimes what can you trust?
116 - Are we paving the path our users desire?
AI, Blockchain, Quantum Computing. These are technologies that are "set to revolutionise the world", and yet, half the time I don't feel like the world is very revolutionary.
115 - Working from home forever?
What's the future going to look like?
114 - Continuous Learning
One of the reasons that I write this newsletter is because it scratches my own itch. I read a lot of articles, blogposts and reddit forums pretty much constantly. I lose track of which ones I've read, and I found myself in meetings with people where someone would say "Oh, did you see thing X" and my response was normally "Oh yeah, I read about that weeks ago". Someone suggested that I start tracking what I read, and try to, you know, actually tell others the interesting tidbits that I read to be helpful.