<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Phishing Resistance on Nalar</title>
    <link>https://nalar.dev/tags/phishing-resistance/</link>
    <description>Recent content in Phishing Resistance on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/phishing-resistance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Design Push MFA to Resist Prompt Fatigue</title>
      <link>https://nalar.dev/design-push-mfa-to-resist-prompt-fatigue/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/design-push-mfa-to-resist-prompt-fatigue/</guid>
      <description>&lt;p&gt;Push-based multi-factor authentication can make sign-in convenient: after a password is accepted, the user receives a prompt on a trusted device and approves the attempt. The weakness appears when the prompt itself becomes easy to approve without understanding what it represents.&lt;/p&gt;&#xA;&lt;p&gt;If an attacker obtains a password and can repeatedly trigger approval requests, the legitimate user may eventually approve one because the prompts are confusing, disruptive, or mistaken for a request they initiated. The second factor still exists, but its security value has been reduced to a repeated yes-or-no question.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
