Bringing new software or SaaS into your organization is a security risk - how do you assess it? Richard chats with Jessie Schofer about her experiences in HR software acquisition, which led to the creation of secureless.ai. Jessie tells the story of evaluating various SaaS and other software products and realizing that, while the website says they are compliant with GDPR and/or SOC 2, are they really? This leads to a conversation about the product procurement process and about actually understanding the security risk you take on every time a new product is added to your organization. At what point does security block an acquisition? And after being acquired, how often do you reassess? Supply chain security hygiene starts at procurement - are you part of the evaluation?

Links

• Secureless.ai
• GDPR Enforcement Tracker

Recorded June 23, 2026

How are large language models changing the way security vulnerabilities are found? Richard chats with Sami Laiho about the rapidly changing landscape in security exploits. Certain LLM models like Anthropic's Mythos and Microsoft MDASH are optimized to find software vulnerabilities - and potentially fix them. And so there is an arms race of sorts, repairing old vulnerabilities before LLMs in the hands of black hats can exploit them. But what about everyone else? Sami talks about getting LLMs working for your organization to test for potential security risks and assess the impact of new vulnerabilities as they appear.

Links

• Palo Alto Networks
• Claude Mythos
• Microsoft MDASH
• Zero Day Clock
• Security Update Guide

Recorded June 19, 2026

How can Azure Policies help you? While at Techorama in Belgium, Richard sat down with Barbara Forbes to discuss how Azure Policies have evolved and the techniques sysadmins are using to improve security, cost controls, efficiency, and more. Barbara talks about how the default policies are designed to get folks started in Azure quickly - not necessarily optimally. And there are plenty of policy templates out there, but before you implement them, it's worthwhile to review each policy and ask the question "why?" Keeping good documentation on policies makes it easier to know intent, especially when it comes to changing them - and you'll need to change them! There are a number of ways to apply policies, but in the end, they are just more Infrastructure-as-Code, and so easily repeatable. Azure Policies are there to help you provide freedom with guardrails if you implement them carefully!

Links

• Azure Policy
• Microsoft Cloud Security Benchmark
• Azure Management Groups
• Azure Bicep
• Terraform on Azure

Recorded May 12, 2026