<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Owasp on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</title><link>https://blog.lameiro0x.com/tags/owasp/</link><description>Recent content in Owasp on Miguel Lameiro | Cybersecurity Blog &amp; Security Writeups</description><generator>Hugo -- 0.161.1</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.lameiro0x.com/tags/owasp/index.xml" rel="self" type="application/rss+xml"/><item><title>OWASP Top 10 for LLM Applications: A Practical Security Guide</title><link>https://blog.lameiro0x.com/notes/ai-security/owasp-top-10-for-llm-applications-practical-guide/</link><pubDate>Wed, 06 May 2026 00:00:00 +0000</pubDate><guid>https://blog.lameiro0x.com/notes/ai-security/owasp-top-10-for-llm-applications-practical-guide/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;The OWASP Top 10 for LLM Applications is useful because it moves the conversation beyond &amp;ldquo;the model said something wrong.&amp;rdquo; In real systems, an LLM is connected to prompts, RAG, vector databases, tools, APIs, logs, users, permissions, providers, and business workflows.&lt;/p&gt;
&lt;p&gt;That is where the risk lives. A bad response is a quality problem. A bad response that triggers a tool call, leaks internal context, writes to a ticketing system, executes generated SQL, or retrieves another user&amp;rsquo;s documents becomes a security problem.&lt;/p&gt;</description></item></channel></rss>