<?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 jaipradeesh</title>
    <link>https://jaipradeesh.com/tags/security/</link>
    <description>Recent content in Security on jaipradeesh</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 28 Dec 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://jaipradeesh.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>LLMs are great at finding bugs, terrible at finding them twice</title>
      <link>https://jaipradeesh.com/posts/llm-discovery-deterministic-execution/</link>
      <pubDate>Sun, 28 Dec 2025 00:00:00 +0000</pubDate>
      <guid>https://jaipradeesh.com/posts/llm-discovery-deterministic-execution/</guid>
      <description>&lt;p&gt;Run an LLM-based code reviewer on a code change 10 times and it flags a SQL injection vulnerability 7 times. The other 3 runs come back clean. Same code, same vulnerability, different result.&lt;/p&gt;&#xA;&lt;p&gt;LLMs are probabilistic, but security requirements are binary. &amp;ldquo;Usually catches security issues&amp;rdquo; is a bug, not a feature.&lt;/p&gt;&#xA;&lt;p&gt;When LLMs do catch something, the finding is often good because they pick up on subtle, contextual patterns that would be hard to write rules for from scratch. The trick is using them as a discovery layer: have the model find what to look for, then encode those discoveries as deterministic rules.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
