[ARIN-consult] Consultation on Expanding 2FA Options for ARIN Online

[Chris Woodfield]

> On Jan 24, 2023, at 11:16 AM, Ross Tajvar <ross at tajvar.io> wrote:
> 
> > 1. Would you support ARIN offering email as an additional 2FA method?
> No. Email can be used to reset one's password. If it's used for one-time login codes as well, that's only one authentication factor. An email compromise could therefore easily result in account takeover, which defeats the purpose of 2FA.

Agreed. The password-reset mechanism and standard 2FA login process should not both use the same auth path.

> 
> > 2. Given that 13% of web user accounts list phone numbers outside the ARIN service region, should we widen the availability of SMS, or are the other offered 2FA options sufficient to meet the needs of these users?
> I am against SMS 2FA being offered as an option at all, so I'm ambivalent about this.

I’m not a fan of SMS as a 2FA for all the obvious reasons, but also recognize that requiring FIDO/TOTP as the *only* supported 2FA is a sure path to tepid adoption. I believe that we should highly encourage users to prefer those mechanisms over SMS but not prohibit SMS as an option.

> 
> > 3. We agree that users should be allowed to register multiple hardware security keys. The question is: What is the optimal number of keys that should be allowed to be registered?
> I can't see someone reasonably needing to register more than a handful, but I also don't think there's a good reason to set a low limit. I think 10 is a reasonable upper bound.
> 

The only reason I can see to limit the number of keys is to discourage the use of a single account by multiple employees in an organization. I think a good approach is to have a soft limit (say, 8)  that can be increased on request to help combat this. There should also be a mechanism to delete no-longer-used 2FA keys instead of simply disabling them (Seems obvious, but I have accounts on sites that don’t allow this, leading to a ever-growing list of registered auth apps on various phones shown in my account) 

Separate question - is there a workflow for manually resettting/removing user 2FA when users lose their tokens/auth apps/phone numbers/etc? How would ARIN staff authenticate those requests? Please, please don’t make that process involve a notary (I’m looking at you, AWS).

Thanks,

-Chris

> On Tue, Jan 24, 2023 at 1:53 PM ARIN <info at arin.net <mailto:info at arin.net>> wrote:
>> On 1 November 2022, ARIN  announced that we will require two-factor authentication (2FA) on all ARIN Online accounts beginning 1 February 2023. ARIN currently has three options for customers to set up 2FA on their ARIN Online accounts:
>> 
>> - Time-based One-time Password (TOTP) using an authenticator of your choice
>> - Short Message Service (SMS) for customers within the ARIN service region
>> - FIDO2/Passkey-enabled Security Key
>> 
>> Please note: Voice 2FA is not currently available for new 2FA activations; it is still available to those customers who already have that method set up on their accounts.
>> 
>> Following the announcement of the planned enforcement date of 1 February 2023, we received several suggestions for further expansion of our authentication offerings, including:
>> 
>> - Allowing email as an authentication method
>> - Enabling SMS support for customers who reside outside of the ARIN service region
>> - Allowing registration of multiple hardware security keys.
>> 
>> We are seeking community feedback on these suggestions as well as additional input on our 2FA options. Specifically:
>> 
>> 1. Would you support ARIN offering email as an additional 2FA method?
>> 
>> 2. Given that 13% of web user accounts list phone numbers outside the ARIN service region, should we widen the availability of SMS, or are the other offered 2FA options sufficient to meet the needs of these users?
>> 
>> 3. We agree that users should be allowed to register multiple hardware security keys. The question is: What is the optimal number of keys that should be allowed to be registered?
>> 
>> The feedback you provide during this consultation will help us decide the path forward regarding our 2FA options for ARIN Online. Thank you for your participation in the ARIN Consultation and Suggestion Process.
>> 
>> Please provide comments to arin-consult at arin.net <mailto:arin-consult at arin.net>. You can subscribe to this mailing list at: https://lists.arin.net/mailman/listinfo/arin-consult
>> 
>> This consultation will remain open through 5:00 PM ET on 7 February 2023.
>> 
>> Regards,
>> 
>> John Curran
>> President and CEO
>> American Registry for Internet Numbers (ARIN)
>> 
>> Helpful Resources:
>> 
>> Consultation: https://www.arin.net/participate/community/acsp/consultations/2023/2023-1/
>> Two-Factor <https://www.arin.net/participate/community/acsp/consultations/2023/2023-1/Two-Factor> Authentication at ARIN: https://arin.net/2FA
>> 
>> 
>> _______________________________________________
>> ARIN-Consult
>> You are receiving this message because you are subscribed to the ARIN Consult Mailing
>> List (ARIN-consult at arin.net <mailto:ARIN-consult at arin.net>).
>> Unsubscribe or manage your mailing list subscription at:
>> https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
>> Help Desk at info at arin.net <mailto:info at arin.net> if you experience any issues.
> _______________________________________________
> ARIN-Consult
> You are receiving this message because you are subscribed to the ARIN Consult Mailing
> List (ARIN-consult at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> https://lists.arin.net/mailman/listinfo/arin-consult Please contact the ARIN Member Services
> Help Desk at info at arin.net if you experience any issues.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-consult/attachments/20230124/54cf880d/attachment.htm>