<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Attack-Trees on ShieldedBytes</title>
    <link>https://linuxeries.org/tags/attack-trees/</link>
    <description>Recent content in Attack-Trees on ShieldedBytes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 17 Nov 2026 09:52:49 +0200</lastBuildDate>
    <atom:link href="https://linuxeries.org/tags/attack-trees/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Attack Trees to Prioritize API Endpoint Protection in Microservices</title>
      <link>https://linuxeries.org/post/2026-11-17-using-attack-trees-to-prioritize-api-endpoint/</link>
      <pubDate>Tue, 17 Nov 2026 09:52:49 +0200</pubDate>
      <guid>https://linuxeries.org/post/2026-11-17-using-attack-trees-to-prioritize-api-endpoint/</guid>
      <description>&lt;h2 id=&#34;attack-trees-for-api-endpoint-prioritization-in-microservices&#34;&gt;Attack Trees for API Endpoint Prioritization in Microservices&lt;/h2&gt;&#xA;&lt;p&gt;Microservices can expose dozens, sometimes hundreds, of REST or gRPC endpoints. Each one is a potential attack vector. When the budget and bandwidth are tight, you need a systematic way to decide which endpoints deserve the most defensive effort. Attack trees give you a structured, risk‑based view that maps attacker goals to concrete API actions and lets you quantify effort versus impact.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
