- cooperation-wg - mailman.ripe.net

Fixing threat intelligence for you
by Alex Smirnoff 18 May '18

18 May '18

Hi everyone, I decided to re-animate my old project: to fix threat intelligence for vulnerability management. First of all, why is it broken? (a picture attached) because today's threat intel is massively based on attack events, which means you get it too late. My idea is to create and maintain a database of available exploit capabilities, which whould help you to know (hopefully slightly in advance) what you need to urgently patch right now. https://uisgcon.org/pdf/uisgcon13-alex-smirnoff+what-is-wrong-with-informat… sildes 23-46 contain a more precise description of how would it look like. Yet I cannot do it by myself: i need either people to help me, or money to hire people, hosting resources, or probably all of the above. Anyone could suggest me a good direction to look for?

1 0

Massive IP blockings in Russia
by Alexander Isavnin 16 May '18

16 May '18

Dear colleagues! I’m not pleased to inform you that RosComNadzor, a Russian Communication supervisory body, has started blocking huge ranges of IPs belonging to different cloud infrastructures, mostly Amazon and Google Cloud. Those ranges include: 13.52.0.0/14, 13.56.0.0/14, 18.184.0.0/15, 18.194.0.0/15, 18.196.0.0/15, 34.192.0.0/10, 34.240.0.0/13, 34.248.0.0/13, 35.156.0.0/14, 35.160.0.0/13, 35.176.0.0/15, 52.0.0.0/11, 52.192.0.0/11, 52.208.0.0/13, 52.28.0.0/15, 52.58.0.0/15, 54.144.0.0/12, 54.160.0.0/12, 54.228.0.0/15, 54.72.0.0/15, 54.88.0.0/16. Russian ISPs MUST fully block all traffic to such networks. The list is frequently updated and gets automatically propagated to ISP every once in a while, failure to block any address may result in 1500eur fine. The infrastructure listed above is being added to the blocklist under “counter-terrorist and counter-extremist” order of the General Prosecutor Office, #27-31-2015/Id4082-15, issued in 2015 and often used for blocking an arbitrary unwanted content. The real reason for such blocking is an attempt to cut access to Telegram messenger, which refused to provide end-to-end encryption keys to the Federal Security Service (previously known as KGB). This is a case similar to San-Bernardino shooter’s, where the FBI was denied access to the shooter’s iPhone, but courts in Russia have made completely opposite decision. Telegram’s infrastructure is being blocked by a different decision by RosKomNadzor, #2-1779/2018. Cloud infrastructures are being blocked for massive proxy and VPN hosting used to dodge messenger blocking. It is said, that more Apple and Google networks may be blocked soon for apps updates and push notifications delivery for Telegram. We hope to still have the global IP connectivity to keep you informed about how the situation develops. Do not be surprised if some of your services placed in cloud infrastructures will miss Russian customers. You can monitor the number of IP addresses, domains and URLs to be blocked in Russia at the https://2018.schors.spb.ru/ page (run by the famous ENOG community member Phil Kulin). Detailed information (also via API) is available at the https://reestr.rublacklist.net run by RosKomSvoboda civil society group. Kind regards, Alexander Isavnin Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum

2 1

New on RIPE Labs: The GDPR: Amendments to the RIPE Database
by Mirjam Kuehne 14 May '18

14 May '18

Dear colleagues, This is our fourth in a series of RIPE Labs articles discussing the General Data Protection Regulation (GDPR) implementation. Here we're looking at amendments that will be needed to the RIPE Database in order to ensure GDPR compliance: https://labs.ripe.net/Members/maria_stafyla/how-were-implementing-the-gdpr-… Kind regards, Mirjam Kühne RIPE NCC

1 0

RIPE NCC Hosts Workshop for Russian LEAs
by Chris Buckridge 10 May '18

10 May '18

Dear colleagues, Last week, on 31 January 2018, we held a one-day workshop for Russian Law Enforcement Agencies (LEAs) in Moscow. The workshop was attended by 19 participants. The event followed the format of similar LEA capacity-building efforts in other parts of our service region. LEAs learned about the RIR system and the respective roles of RIPE and the RIPE NCC, and there were discussions on the RIPE Database and the RIPE Policy Development Process (PDP). The concerns of LEAs were primarily around issues of attribution (knowing who is using an IP address at a given point in time). IPv6 deployment and the Internet of Things (IoT) were also topics of interest. We went over the current policy proposals in the PDP, including the proposal initiated by the LEA community, 2017-02, "Regular abuse-c Validation" and encouraged LEAs to participate. Last year, the RIPE NCC signed a Memorandum of Understanding (MoU) with the Ministry of Telecom and Mass Communications of the Russian Federation, an agreement which helped to make this initiative possible. We will be hosting similar capacity-building events with LEAs in Armenia and the UAE later this week. You can find the agenda and presentations from the workshop here: https://www.ripe.net/participate/meetings/lea-meetings/ripe-ncc-lea-meeting… <https://www.ripe.net/participate/meetings/lea-meetings/ripe-ncc-lea-meeting…> Kind regards Chris Buckridge External Relations Manager RIPE NCC

10 20

Co-op WG agenda for RIPE76
by Johan Helsingius 03 May '18

03 May '18

The current version of the Co-op WG agenda is up on https://ripe76.ripe.net/programme/meeting-plan/coop-wg/ Thursday, 17 May 09:00 - 10:30 1. CGN and an Analytical Approach to Policymaking - Marco Hogewoning 2. Consolidation in the Internet Ecosystem - Jari Arkko 3. Regulatory Developments in the EU - Chris Buckridge 4. EURALO and the RIPE Community - Oliver Crépin-Leblond 5. Protecting the Public Core of the Internet - Joanna Kulesza Julf & Achilleas

1 0

EU TLD & Brexit
by Gordon Lennox 01 May '18

01 May '18

My attention was drawn to this new policy from Brussels: https://www.theregister.co.uk/2018/03/29/eu_dumps_300000_ukowned_domains_in… Of interest to people involved with domain names, people who have names registered under EU or who are still thinking about it and who are resident in the UK or thinking about moving there? Nationality does not count: residence does. Gordon

5 8

Communicating IG final report
by Michael J. Oghia 22 Mar '18

22 Mar '18

Hi everyone, Two of my colleagues and I organized a workshop at IGF 2017 that examined ways we could better discuss and communicate about Internet governance (titled: "Explaining Internet Governance to Friends and Family 101: How to Improve our Communication?"). The final report with recommendations is now available (attached), and I thought it might be relevant to some on this list. It is also available to download at: https://bit.ly/WS161Report Please reply to this email if you have any questions or comments, and feel free to share it with your networks. Best, -Michael __________________ Michael J. Oghia #Netgov consultant & researcher | editor Belgrade, Serbia Skype: mikeoghia Twitter <https://www.twitter.com/MikeOghia> *|* LinkedIn <https://www.linkedin.com/in/mikeoghia>

1 0

Fwd: Last call for presentations and Draft programme for RIPE 76
by Johan Helsingius 22 Mar '18

22 Mar '18

We could definitely use a few more submissions for the co-op wg session... Julf -------- Forwarded Message -------- Subject: [ripe-list] Last call for presentations and Draft programme for RIPE 76 Date: Tue, 20 Mar 2018 23:53:38 +0000 From: Benno Overeinder <benno(a)NLnetLabs.nl> To: ripe-list(a)ripe.net Colleagues, A list of currently accepted RIPE 76 presentations is now published at: https://ripe76.ripe.net/programme/meeting-plan/plenary/ There are still plenary, BoF, tutorial and workshop slots remaining for the final RIPE 76 programme and RIPE Programme Committee will accept new proposals until *8 April 2018*. This is our last call for you to submit your proposals. You can find the CFP for RIPE 76 below, or at https://ripe76.ripe.net/submit-topic/cfp/, for your proposals for plenary session presentations, tutorials, workshops, BoFs (Birds of a Feather sessions) and lightning talks. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings, see the "Speakers" paragraph in CFP for more information. Kind regards, Benno Overeinder RIPE PC Chair https://ripe76.ripe.net/ripe-pc -------------------->>><<<-------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. RIPE 76 will take place from 14-18 May in Marseille, France. The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 76. See the full descriptions of the different presentation formats, https://ripe76.ripe.net/submit-topic/presentation-formats/. Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *8 April 2018*. Proposals submitted after this date will be considered depending on the remaining available space in the programme. The PC is looking for presentations covering topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) Speakers Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. Also note that, on an individual basis, participants can apply for a RIPE Fellowship to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship Submissions Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe76.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non-commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes total for both presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe76.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe76.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Benno J. Overeinder NLnet Labs https://www.nlnetlabs.nl/

1 0

Fwd: [iot-wg] Fwd: Call for new ENISA Expert Group on Transport Security
by Johan Helsingius 13 Mar '18

13 Mar '18

-------- Forwarded Message -------- Subject: [iot-wg] Fwd: Call for new ENISA Expert Group on Transport Security Date: Tue, 13 Mar 2018 13:39:14 +0100 From: Marco Hogewoning <marcoh(a)ripe.net> To: iot-wg(a)ripe.net Dear Colleagues, Please find below a message received from ENISA regarding the creation of an expert group on transport security and resilience. Although quite far away from RIPE’s mission and mandate, with the ever increasing importance of Internet technology and the IP transport layer, it might be of benefit to bring expertise on these areas into that dialogue. At this stage RIPE NCC does not envision to take part in this group directly, although we will try and keep track of progress and any outcomes that might relate to the interests of the RIPE community. Regards, Marco Hogewoning Senior External Relations Officer RIPE NCC Begin forwarded message: > > Dear Experts, > > I trust this email finds you well. > > We would like to bring to your attention a call for applications for a > new ENISA Experts Group on Transport Security and Resilience. > The focus of the group will be air, rail and water transport and you > can find more information here: > https://www.enisa.europa.eu/news/enisa-news/call-for-experts-for-transsec-t… > > Please feel free to share with your networks. > > Best regards, > -Apostolos > > ------------------------------------------------------------------------------------------------------ > Dr Apostolos Malatras > > Network and Information Security Expert > European Union Agency for Network & Information Security > > Address: 1 Vass Sofias Str, Marousi 151 24, Attica, Greece > E- mail: Apostolos.Malatras(a)enisa.europa.eu > <mailto:Apostolos.Malatras@enisa.europa.eu><mailto:Apostolos.Malatras@enisa.europa.eu> > Office: +30 2814 409 630 > Mobile: +30 6985 051 401

1 0

New on RIPE Labs: Legal Grounds for Lawful Personal Data Processing and the RIPE Database (GDPR)
by Athina Fragkouli 06 Mar '18

06 Mar '18

Dear all, In our third article on the GDPR, we are looking at the legal basis for processing personal data in the RIPE Database when it refers to an individual resource holder or contact person. We will also outline the relevant obligations of the responsible parties. https://labs.ripe.net/Members/Athina/gdpr-legal-grounds-for-lawful-personal… Kind regards, Athina Fragkouli Head of Legal RIPE NCC

1 0