lgkm.org field notes The state of modern IT and security https://lgkm.org/notes/ 2026-10-29T00:00:00Z Simon Bennett The AI supply chain: models, plugins and tool servers as third parties https://lgkm.org/notes/ai-supply-chain-third-parties/ 2026-10-29T00:00:00Z An AI feature is assembled from parts other people made: a hosted model, downloaded weights, editor plugins, tool servers and SaaS connectors. Each is a supplier with access, and the incidents of the last two years came through exactly those parts. Most third-party registers list only the first. DNSSEC: why it exists, who uses it and what it has broken https://lgkm.org/notes/dnssec-why-who-and-what-broke/ 2026-10-27T00:00:00Z DNSSEC lets a resolver check that a DNS answer really came from the owner of the name. It was built to stop forged answers, it is switched on far more by resolvers than by domain owners, and when it fails it takes whole domains, and once a whole country's zone, offline. Email was built to trust everyone: TLS, SPF, DKIM and DMARC, and what each one breaks https://lgkm.org/notes/email-security-patches/ 2026-10-27T00:00:00Z Email still runs on a 1980s protocol that lets any server claim to be anyone and send in the clear. Opportunistic TLS, SPF, DKIM and DMARC were added on top, one problem at a time. Each fixes something real, each breaks something else, and none of them stops a lookalike domain. Jev, the model that only decides: where it fits in security work https://lgkm.org/notes/jev-use-cases/ 2026-10-27T00:00:00Z Jev is a new kind of AI model that writes no text. It reads something and answers typed questions with a choice, a score or a yes/no probability, in a fraction of a second and for a fraction of a cent. That makes it a good first sorter for alerts, data labels and agent actions, and a poor final judge. Which language model for which job https://lgkm.org/notes/which-language-model-for-which-job/ 2026-10-27T00:00:00Z Large language models now come in four kinds, not one: frontier models for the hardest work, workhorses for most of it, small fast models for volume, and open-weight models you run yourself. The names change every month and the kinds do not, so choose by job, test one size down, and write policy about kinds rather than names. IP address or identity: what should actually let someone in? https://lgkm.org/notes/ip-address-or-identity/ 2026-10-26T00:00:00Z An IP allowlist says where a request comes from. Identity says who or what is asking. Both still have a place, on the internet and inside the network, but each only works when certain things are in place, and each fails in its own way. Post-quantum migration starts with a cryptography inventory https://lgkm.org/notes/post-quantum-starts-with-inventory/ 2026-10-26T00:00:00Z The new quantum-safe algorithms are standard and the deadlines are set: 2028 to know what you have, 2035 to finish. The hard part is not the maths. It is finding every place an organisation uses cryptography, and most cannot list them yet. Blast radius belongs in the board pack https://lgkm.org/notes/blast-radius-board-pack/ 2026-10-22T00:00:00Z Boards are told how many vulnerabilities were patched and how many people did the training. The question they actually need answered is how far one intruder could get. Blast radius can be measured, tested and reported in a line, and it belongs in the board pack. Governing AI agents: keep the record, expire the access https://lgkm.org/notes/governing-ai-agents/ 2026-10-21T00:00:00Z Identity governance, access reviews and privileged access management can all cope with AI agents, once each agent is split into a lasting record with a human sponsor and access that is granted for a task and then expires. What that looks like in practice, and why the borrowed login defeats all of it. Agents are the new insiders, with API keys https://lgkm.org/notes/agents-are-the-new-insiders/ 2026-10-19T00:00:00Z An AI agent that can read mail, call APIs and change records is a privileged insider that can be talked into things. Treat it like one: an owner, the least access that works, and a record of what it did. DLP after generative AI: the leak is now a prompt https://lgkm.org/notes/dlp-after-generative-ai/ 2026-10-19T00:00:00Z Data used to leave by email, upload or USB stick. Now it leaves as text pasted into an AI assistant. Banning the tools does not work; giving people a safe one, and watching the prompt, does. DORA in practice: what the third-party register reveals https://lgkm.org/notes/dora-third-party-register/ 2026-10-19T00:00:00Z DORA made every EU financial firm list its ICT suppliers in one standard register. The first lesson is not about suppliers at all. It is how hard it is to say which services depend on which contracts. Identity is the perimeter, so what guards identity? https://lgkm.org/notes/identity-is-the-perimeter/ 2026-10-19T00:00:00Z Once identity decides access, stolen credentials and forgotten accounts become the way in. Guarding identity means phishing-resistant sign-in, owners for every account, and watching sessions, not only logins. Is an AI agent just another non-human identity? https://lgkm.org/notes/is-an-agent-just-another-non-human-identity/ 2026-10-19T00:00:00Z An AI agent is a non-human identity only when it has credentials of its own. If it carries a person's delegated authority or borrows their login, it is something else, and the route decides whether PAM, access reviews and IGA can see it. Labels before rules: why microsegmentation projects stall https://lgkm.org/notes/labels-before-rules/ 2026-10-19T00:00:00Z Microsegmentation projects stall because nobody can say what each workload is. Label the estate first, by application, environment and role, and the rules almost write themselves. Machine identities outnumber people; few organisations can list them https://lgkm.org/notes/machine-identities-outnumber-people/ 2026-10-19T00:00:00Z Service accounts, API keys, tokens and certificates now far outnumber staff, and most have no owner and no end date. Start with an inventory that names an owner for each, then shorten how long their secrets live. Shared responsibility still fails at the same seam https://lgkm.org/notes/shared-responsibility-same-seam/ 2026-10-19T00:00:00Z Cloud providers rarely get breached through their own platform. Their customers do, at the seam where the provider's controls end and the customer's settings begin: identity, configuration and data access. Vulnerability counts are the wrong number https://lgkm.org/notes/vulnerability-counts-wrong-number/ 2026-10-19T00:00:00Z A falling count of open vulnerabilities feels like progress and says little about risk. What matters is which weaknesses an attacker can reach and use, on the things the business depends on, and how fast those get closed. Security runs on pub-sub: the mesh, the logs and the monitoring https://lgkm.org/notes/security-runs-on-pub-sub/ 2026-10-18T00:00:00Z Most of what makes a security architecture work is one pattern in disguise, publish and subscribe. Seeing it explains why logging, monitoring and the mesh succeed or fail together. Where security architecture stands, and why most organisations run several at once https://lgkm.org/notes/where-security-architecture-stands/ 2026-10-18T00:00:00Z Security architecture has moved through seven stages, from ad hoc to AI-native. Most organisations live in several at once, and that mix is the real starting point.