August 2013 - anti-abuse-wg - mailman.ripe.net

Automatic IP -> abuse email address mapping
by Olaf van der Spek 15 Dec '13

15 Dec '13

Hi, I hope this is the right list for such a question. How does one map an IP address to an abuse email address in an automated way? I assume scripts exist, but I haven't found any. Does everyone roll their own? -- Olaf

13 38

Clarification Regarding Needs Assessment and Audits
by Andrew de la Haye 01 Sep '13

01 Sep '13

Dear colleagues, We have been following the recent discussions on the mailing list and would like to offer clarification in relation to a couple of points that were raised. According to "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" [1], address space is distributed based on demonstrated technical need in order to deliver services. This need is evaluated according to addressing requirements, network infrastructure, equipment and number of customers. The exact services for which the resources are being requested are not considered as part of the evaluation process. As an example, if address space is requested for the technical need of a mail server, it is not verified what type of mails are being sent through that server. This practice is in line with the current IPv4 policy [1]. It is important to note that technical need is evaluated for assignments. The need for an additional allocation is considered based on past and future usage, taking into account all assignments that have been made by the LIR previously. The RIPE NCC does not have a mandate to deregister allocations if the expected growth was less or different than expected. Nevertheless, we do see LIRs voluntarily returning allocations in the event that they no longer have a need for the addresses. As above, this practice is based on current RIPE Policies. When a policy is changed through the RIPE Policy Development Process (PDP) [2], we adjust our processes accordingly. When the RIPE NCC conducts an audit of an LIR, it checks that: - RIPE Policies are followed correctly - Assignments are registered properly and being used for the purpose they were requested for (if not, the technical need is re-evaluated) - Contact information is still correct An LIR is either randomly selected for an audit, or selected following a community report against that member [3]. Last year, the RIPE NCC created a report form to facilitate and simplify reporting on policy violations, provision of untruthful information to the RIPE NCC and incorrect RIPE Database data [4]. Once the reported information and evidence is evaluated, the RIPE NCC investigates the claim and proceeds according to RIPE Policies and RIPE NCC procedures. This can result in address space being deregistered. More detailed information on reasons for deregistration of address space is available in "Closure of Member and Deregistration of Internet Number Resources" [5]. Kind regards Andrew de la Haye Chief Operations Officer RIPE NCC [1] "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region" http://www.ripe.net/ripe/docs/v4policy [2] "RIPE Policy Development" http://www.ripe.net/ripe/policies [3] "RIPE NCC Audit Activity" http://www.ripe.net/ripe/docs/audit [4] "RIPE NCC Reporting Procedure" http://www.ripe.net/contact/ripe-ncc-complaints-procedure [5] "Closure of Member and Deregistration of Internet Number Resources" http://www.ripe.net/ripe/docs/closure

10 21

next step on abuse-c deployment
by Denis Walker 21 Aug '13

21 Aug '13

Dear Brian and Tobias We are approaching the end of quarter 3 when all LIRs should have an abuse-c otherwise we said we would add it. Having talked to our customer service guys they have the impression that many LIRs had problems adding abuse-c despite all the documentation, Labs articles and videos. So we had a think about the next step. What we would suggest is: -for us to do a short presentation in the AA WG session at RIPE 67 reviewing how this first phase went with latest stats. -Then propose a new feature to add to the LIR Portal. Allow LIRs who don't yet have an abuse-c to simply enter an email address in a box that they want to use. -We will have scripts in the background that will create a new ROLE object, add this email as abuse-mailbox in that ROLE and add an abuse-c to their ORGANISATION object referencing the new ROLE object. -Then extend the deadline for LIRs to the end of October -After October we will use the same scripts to add the internal LIR contact email address, held by the RIPE NCC, in the same way for any LIR that still does not have one Then in November we start the next phase for PI holders. As they don't have access to the LIR Portal we can offer the same simple process with a web page having 3 boxes. Enter the email address they want to use, the name of their ORGANISATION object and the password to authorise an update to their ORGANISATION object. Using the same scripts we will create a ROLE and make the connections. What do you think? cheers denis

2 2

Update on "abuse-c:" coverage in RIPE Database
by Johan Åhlén 20 Aug '13

20 Aug '13

Dear colleagues, We would like to update you on the current "abuse-c:" coverage in the RIPE Database now that we have sent out the second batch of reminders. The last update you received was at the end of June; you can find the archived message at http://www.ripe.net/ripe/mail/archives/anti-abuse-wg/2013-June/002273.html -------- NETWORK NUMBERS: Total number of IPv4 allocations listed: 21,068 Number of IPv4 allocations covered with "abuse-c:": 10,901 or 51.7% of IPv4 allocations Total number of IPv4 PI assignments listed: 28,542 Number of IPv4 PI assignments covered with "abuse-c:": 1,591 or 5.6% of IPv4 assignments Total number of IPv6 allocations listed: 6,037 Number of IPv6 allocations covered with "abuse-c:": 3,223 or 53.4% of IPv6 allocations Total number of IPv6 assignments: 1,493 Number of IPv6 assignments covered with "abuse-c:": 190 or 12.7% of IPv6 assignments Total number of objects: 57,140 (IPv4: 49,610 / IPv6: 7,530) Number of objects covered with "abuse-c:": 15,905 or 27.8% (IPv4: 25.2% / IPv6: 45.3%) -------- IPv4 NETWORK SIZES: Total size of IPv4 allocations listed: 594,555,904 Size of IPv4 allocations covered with "abuse-c:": 337,556,992 or 56.8% Total size of IPv4 PI assignments listed: 169,707,896 Size of IPv4 PI assignments covered with "abuse-c:": 14,646,192 or 8.6% Total size of listed IPv4 addresses: 764,263,800 Size of listed IPv4 addresses covered with "abuse-c:": 352,203,184 or 46.1% In our last update, the coverage of IPv4 allocations, by size, was 41.1%. Today it is at 56.8%. -------- LIR NUMBERS: LIRs with "abuse-c:": 4,024 LIRs without "abuse-c:": 5,404 If you have any questions about theses figures, please feel free to contact us. Kind regards, Johan Åhlén Assistant Manager, Database Group RIPE NCC

1 0

Call For Agenda Items - RIPE67
by Brian Nisbet 12 Aug '13

12 Aug '13

Colleagues, While Europe is still enjoying its summer, the next RIPE meeting is slowly approaching. This meeting will be taking place in Athens from the 14th - 18th October 2013 and all the details can be found at http://ripe67.ripe.net As always Tobias and I are hoping the Anti-Abuse WG session will be full of interesting presentations and discussions. If you have anything you would like to present at the meeting, please email us at aa-wg-chairs(a)ripe.net Thanks, Brian

1 0

SQL injection attacks from Kyivstar GSM
by Roy Vij 02 Aug '13

02 Aug '13

We have seen a rush of SQL injection attacks from Ukraine based Kyivstar GSM. How can I query the ripe database to provide all IP blocks from Kyivstar GSM? -Regards

3 2