<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
NANOGers -
<div class=""><br class="">
</div>
<div class="">A consultation opened today on potentially requiring use of 2-factor authentication to login into ARIN Online – this would take place once SMS 2FA is deployed. If you think that this is: a) a great idea, b) a bad idea, c) anything else, then
feel free to subscribe to the arin-consult mailing list (open to all at <a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a>) and provide your feedback.</div>
<div class=""><br class="">
</div>
<div class="">Best wishes,</div>
<div class="">/John</div>
<div class=""><br class="">
</div>
<div class="">
<div class="">John Curran</div>
<div class="">President and CEO</div>
<div class="">American Registry for Internet Numbers</div>
<div class=""><br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">Begin forwarded message:</div>
<br class="Apple-interchange-newline">
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">ARIN <<a href="mailto:info@arin.net" class="">info@arin.net</a>><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[arin-announce] Consultation on Requiring Two-Factor Authentication (2FA) for ARIN Online Accounts</b><br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">24 May 2022 at 12:45:48 PM EDT<br class="">
</span></div>
<div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class="">
<span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To:
</b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">"<a href="mailto:arin-announce@arin.net" class="">arin-announce@arin.net</a>" <<a href="mailto:arin-announce@arin.net" class="">arin-announce@arin.net</a>><br class="">
</span></div>
<br class="">
<div class="">
<div class="">**Background**<br class="">
<br class="">
In 2015, ARIN deployed a Time-Based One-Time password (TOTP) implementation of Two-Factor Authentication (2FA). Since the time of implementing that login security feature, 3.2 percent of ARIN Online users have opted to use 2FA with their accounts.<br class="">
<br class="">
Since October 2020, the ARIN Online system has been subject to a series of dictionary-based password guessing attacks. In March of 2021, we conducted ACSP Consultation 2021.2: Password Security for ARIN Online Accounts (<a href="https://www.arin.net/participate/community/acsp/consultations/2021/2021-2/" class="">https://www.arin.net/participate/community/acsp/consultations/2021/2021-2/</a>)
on proposed improvements to increase account security. This consultation resulted in an agreement to move forward with several improvements that have subsequently been deployed. However, we continue to see frequent attacks on our log-in systems, and ARIN staff
continues to be heavily engaged in mitigating these attacks. Accounts not using 2FA are susceptible to these attacks. We recently updated the community on this topic during ARIN 49 held in Nashville and online in April. You can review this information from
the ARIN 49 Meeting Report (<a href="https://www.arin.net/participate/meetings/ARIN49/" class="">https://www.arin.net/participate/meetings/ARIN49/</a>) by looking for the presentation titled “Brute Force Login Attacks”. <br class="">
<br class="">
It is our intention to make 2FA mandatory for all existing and new ARIN Online accounts going forward. The security of ARIN Online accounts is paramount to the success of the registry, and we do not believe it is tenable to continue without making 2FA required
for all ARIN Online accounts. <br class="">
<br class="">
We are currently developing a second method of 2FA use with ARIN Online to add to our long-deployed TOTP implementation. In the coming months, we will deploy a Short Message Service (SMS) 2FA implementation, thereby adding a second 2FA option for ARIN Online
users. At that time, users will be able to choose between two types of 2FA – SMS and TOTP. Adoption of TOTP 2FA has been limited in part due to perceived complexity, and the addition of SMS-based 2FA will provide a second option that is easier to use for
many customers – and provide much more protection than the simple username-password condition of many ARIN Online user accounts today. (ARIN also plans on adding support for a third 2FA option in the future – Fast Identity Online 2 (FIDO2) – in response to
community suggestions, but we do not believe it is prudent to delay requiring 2FA on ARIN Online accounts until that third option becomes available.)<br class="">
<br class="">
**Requiring 2FA For ARIN Online Accounts**<br class="">
<br class="">
By requiring 2FA for ARIN Online accounts that control number resources, the ARIN community should see stronger security for the registry, reduced risk of account fraud attempts, and increased confidence in the integrity of their ARIN resources. <br class="">
<br class="">
ARIN intends to require 2FA for all ARIN Online accounts shortly after SMS-based 2FA authentication is generally available. We are seeking confirmation from the ARIN community regarding this plan, and ask the following consultation question: <br class="">
<br class="">
-------------------<br class="">
Once SMS-based two-factor authentication (2FA) is available for ARIN Online, do you believe ARIN *should not* proceed with requiring 2FA authentication (SMS-based or TOTP) for all ARIN Online accounts? If so, why?<br class="">
-------------------<br class="">
<br class="">
The feedback you provide during this consultation will help form our path forward to increasing the security of ARIN Online for all customers. Thank you for your participation in the ARIN Consultation and Suggestion Process. Please provide comments to
<a href="mailto:arin-consult@arin.net" class="">arin-consult@arin.net</a>. You can subscribe to this mailing list at:<br class="">
<br class="">
<a href="http://lists.arin.net/mailman/listinfo/arin-consult" class="">http://lists.arin.net/mailman/listinfo/arin-consult</a><br class="">
<br class="">
This consultation will remain open through 5:00 PM ET on 24 June 2022.<br class="">
<br class="">
Regards,<br class="">
<br class="">
John Curran<br class="">
President and CEO<br class="">
American Registry for Internet Numbers (ARIN)<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
ARIN-Announce<br class="">
You are receiving this message because you are subscribed to<br class="">
the ARIN Announce Mailing List (ARIN-announce@arin.net).<br class="">
Unsubscribe or manage your mailing list subscription at:<br class="">
https://lists.arin.net/mailman/listinfo/arin-announce<br class="">
Please contact info@arin.net if you experience any issues.<br class="">
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>