<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mitigation on Designing Secure Software</title>
    <link>https://designingsecuresoftware.com/tags/mitigation/</link>
    <description>Recent content in Mitigation on Designing Secure Software</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://designingsecuresoftware.com/tags/mitigation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Threat modeling Duress code data wiping</title>
      <link>https://designingsecuresoftware.com/writings/duress-wiping/</link>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://designingsecuresoftware.com/writings/duress-wiping/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://yro.slashdot.org/story/26/07/28/1652243/grapheneos-defends-data-wiping-function-that-blocked-us-border-search&#34;&gt;GrapheneOS data wiping function is in the news&lt;/a&gt; due to a customer now facing serious legal jeopardy for using it at a border crossing. I don’t know the details of the case not exactly how the duress feature works, but from public knowledge we certainly can talk about learning from this.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
