<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>MFA on Nalar</title>
    <link>https://nalar.dev/tags/mfa/</link>
    <description>Recent content in MFA on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/mfa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Treat MFA Recovery Codes as Real Credentials</title>
      <link>https://nalar.dev/treat-mfa-recovery-codes-as-real-credentials/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/treat-mfa-recovery-codes-as-real-credentials/</guid>
      <description>&lt;p&gt;Multifactor authentication can fail for ordinary reasons: a phone is lost, a hardware key breaks, or a device is replaced before an authenticator is migrated. Recovery codes give users a way back into an account without asking support staff to improvise an identity check.&lt;/p&gt;&#xA;&lt;p&gt;That convenience creates a security boundary of its own. If a recovery code can bypass the normal second factor, anyone who obtains that code may be able to do the same. A recovery system that is easier to attack than the authentication it replaces can quietly become the preferred path into the account.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
