From info at arin.net Thu Dec 3 16:24:12 2020 From: info at arin.net (ARIN) Date: Thu, 03 Dec 2020 16:24:12 -0500 Subject: [ARIN-Suggestions] Response to ACSP 2020.16 Message-ID: <9BC1CB0A-9037-4760-9CAC-4439713B8914@arin.net> On 3 December, we issued our response to ACSP 2020.16 which was received on 28 October: Thank you for your recent suggestion, numbered 2020.16 upon receipt, requesting that we follow the rate limiting (throttling) advice in NIST 800-63B Section 5.2.2 when locking user accounts. We understand that the current practice of locking user accounts after a number of failed login attempts can sometimes result in legitimate users being locked out of their accounts. ARIN will implement a series of password validations based on the NIST recommendations using a CAPTCHA and account locking periods that become longer as the number of failed login attempts increase. ARIN will work with its Registration Services Department (RSD) to determine a number of failed login attempts that will trigger a notification to RSD. This notification will alert RSD to contact the customer. Thank you for participating in the ARIN Consultation and Suggestion Process. Your suggestion will remain open until implemented. The full text of the suggestion is available below and at: https://www.arin.net/participate/community/acsp/suggestions/2020/2020-16/ Description: ARIN Online should utilize the advice in NIST 800-63B in section ?5.2.2 Rate Limiting (Throttling)? to avoid locking user accounts after 5 failed attempts. In addition to increasing the number attempts to something a little closer to the NIST suggested upper limit (of 100 failed attempts), consideration should be given to use of one or more of the suggested additional techniques that may reduce the likelihood that an attacker will lock the legitimate claimant out as a result of rate limiting (e.g. captcha completion before resuming and/or an increasing wait period after each failed attempts). Value to Community: * Elimination of a fairly trivial denial of service attack against ARIN Online users * Avoidance of unnecessary calls to ARIN customer service * Potential emergence of world peace due to Increased customer satisfaction with the ARIN Online login process Timeframe: Not specified From info at arin.net Sat Dec 5 08:43:15 2020 From: info at arin.net (ARIN) Date: Sat, 05 Dec 2020 08:43:15 -0500 Subject: [ARIN-Suggestions] New ACSP 2020.18 and Closed ACSP 2020.17 Message-ID: <51D57C6E-0FEA-4B6B-940C-527E56A0DD72@arin.net> On 2 December, we received a new suggestion, numbered 2020.18 upon confirmed receipt, asking that ARIN maintain a list of law enforcement offices in our region that handle cybercrime reports and investigations. This suggestion is currently being researched and we will issue our response when it is available.? You can view the suggestion at: https://www.arin.net/participate/community/acsp/suggestions/2020/2020-18/ On 4 December, we also closed ACSP 2020.17, Provide Transfer Source Pre-Qualification Service. The text of the suggestion and our closing response follows: Description: Transfer source pre-qualification Value to Community: Sometimes the provenance of IPv4 addresses is only ?mostly? clear, and before an organization represents to another organization that is has the right to transfer the addresses, the source organization would like to go through the validation process with ARIN. At the end of the process, they would either get pre-approval to transfer the address space in question (subject to terms), or certainty that they are not the entitled registrants. The organization requesting the qualification could pay a fee to cover the service, similar to the recipient pre-qualification or transfer fees. This will ensure revenues align with expenses. Closing Response: Thank you for your suggestion, numbered 2020.17 upon confirmed receipt, requesting that ARIN provide a new service by which source organizations of IP addresses can request pre-qualification from ARIN before a transfer is initiated. ARIN has conferred with the submitter of this suggestion and is happy to say that this service is available today. All organizations that currently hold resources from ARIN or any of ARIN?s predecessor registries have the ability to ensure that their information is fully up-to-date. The three most important items to be updated are 1) Full Organization Name as it is currently registered to do business; 2) Point of Contact (POC) information that is updated and validated; and 3) the Registration Services Agreement (RSA) that is updated and signed by a current officer of the organization authorized to enter into contracts for that organization. This may require that an organization recovery ticket or a Number Resource Policy Manual (NRPM) Section 8.2 Mergers, Acquisitions, and Reorganization transfer ticket be submitted and completed. It may require a POC recovery and/or it may require a new RSA to be signed and verified. Our Registration Services Department (RSD) is available to help guide each of these actions and will advise each organization of the actions required to ensure the organization is ready to submit a source transfer ticket. If these three key pieces of information have been updated and/or validated within the past 12 months, and are still accurate at the time the source transfer ticket is submitted, then most sources of transfers should have no issues when submitting their in-region or inter-RIR transfer requests. Thank you for your participation in the ARIN Consultation and Suggestion Process. This suggestion is now closed. Regards, American Registry for Internet Numbers (ARIN)