<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>security on The Joko Engineering Blog</title>
    <link>/tags/security/</link>
    <description>Recent content in security on The Joko Engineering Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License.</copyright>
    <lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How We Used AI to Increase the Security Level of Our Code</title>
      <link>/posts/how-we-used-ai-to-increase-the-security-level-of-our-code/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      
      <guid>/posts/how-we-used-ai-to-increase-the-security-level-of-our-code/</guid>
      <description>Summary: We replaced a once-a-year external security audit with an AI-driven one we run ourselves, across 100% of our services, as frequently as we want. The core is a Claude Code skill we built in-house — within about a day it was already surfacing issues that our previous external audits had missed. We estimate it saves around $150k a year. Here&amp;rsquo;s how it works, what it found, and the areas where it does not replace a human.</description>
    </item>
    
  </channel>
</rss>
