<?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 Ilscipio - Enterprise Commerce Experts</title>
    <link>https://www.ilscipio.com/en/tags/security/</link>
    <description>Recent content in Security on Ilscipio - Enterprise Commerce Experts</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 07 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.ilscipio.com/en/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A SQL Injection Got Through Two Code Reviews</title>
      <link>https://www.ilscipio.com/en/blog/ai-code-review-in-ide/</link>
      <pubDate>Fri, 07 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.ilscipio.com/en/blog/ai-code-review-in-ide/</guid>
      <description>&lt;p&gt;Last month a junior developer on a client project pushed a SQL query that concatenated user input straight into the WHERE clause. Classic injection. The pull request had two approvals from senior engineers. Nobody caught it.&lt;/p&gt;&#xA;&lt;p&gt;This is not unusual. Code review catches logic bugs, style violations, missing tests. It is not great at catching security patterns. Reviewers scan for intent and correctness - does this code do what it is supposed to do. They are not running OWASP categories through their head while reading a diff.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
