<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Application Security on Nalar</title>
    <link>https://nalar.dev/tags/application-security/</link>
    <description>Recent content in Application 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/application-security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Practical Threat Modeling with Trust Boundaries and Abuse Cases</title>
      <link>https://nalar.dev/practical-threat-modeling-with-trust-boundaries/</link>
      <pubDate>Tue, 01 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/practical-threat-modeling-with-trust-boundaries/</guid>
      <description>&lt;p&gt;Threat modeling is most useful before a vulnerability becomes a patch request. It gives a team a structured way to ask how a system can be misused, which assumptions are security-sensitive, and where defenses should exist.&lt;/p&gt;&#xA;&lt;p&gt;A useful threat model does not need to be a large document. For many services, a one-page data-flow sketch plus a prioritized set of abuse cases is enough to improve design decisions.&lt;/p&gt;&#xA;&lt;h2 id=&#34;begin-with-assets-and-security-goals&#34;&gt;Begin with assets and security goals&lt;/h2&gt;&#xA;&lt;p&gt;Start by identifying what the system is trying to protect.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
