<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web Security on Nalar</title>
    <link>https://nalar.dev/tags/web-security/</link>
    <description>Recent content in Web Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/web-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Preventing SSRF in Backend Services That Fetch User-Supplied URLs</title>
      <link>https://nalar.dev/prevent-ssrf-backend-services/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/prevent-ssrf-backend-services/</guid>
      <description>&lt;p&gt;Features that fetch a URL supplied by a user appear in webhook testers, image importers, link previewers, document converters, and integration platforms. They also create a server-side request forgery (SSRF) boundary: an attacker can try to make the backend send requests to destinations the attacker cannot reach directly.&lt;/p&gt;&#xA;&lt;p&gt;A secure design needs more than a blacklist of suspicious strings.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understand-the-trust-boundary&#34;&gt;Understand the trust boundary&lt;/h2&gt;&#xA;&lt;p&gt;The dangerous capability is not URL parsing itself. It is allowing untrusted input to influence a network connection made with the server&amp;rsquo;s network identity.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
