<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Network Security on Nalar</title>
    <link>https://nalar.dev/tags/network-security/</link>
    <description>Recent content in Network Security on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/network-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Restrict Outbound Connections to Limit Server-Side Request Risk</title>
      <link>https://nalar.dev/restrict-outbound-connections-to-limit-server-side-request-risk/</link>
      <pubDate>Tue, 08 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/restrict-outbound-connections-to-limit-server-side-request-risk/</guid>
      <description>&lt;p&gt;Applications often need to make outbound network requests. A webhook tester may fetch a URL, an image service may download a remote image, or a document processor may retrieve an external resource. The security problem begins when an attacker can influence the destination more than the application intended.&lt;/p&gt;&#xA;&lt;p&gt;If the server can reach internal services, management endpoints, or other networks that the attacker cannot reach directly, a server-side request can cross a trust boundary on the attacker&amp;rsquo;s behalf. Validating the requested URL is important, but URL parsing, redirects, name resolution, and changing network state make application-only defenses easy to overestimate.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
