May 2017 - cooperation-wg - mailman.ripe.net

FYI: From the European Commission: human rights guidance for 3 business sectors
by Patrik Fältström 20 Jul '19

20 Jul '19

Hi, As you can see below European Commission just released human rights guidance for 3 business sectors. I have helped COM and specifically IHRB with their piece of the work, and I know others on this list have also helped. Everything from more formal support to extremely good comments that have helped making the documents what they finally ended up being. Patrik Fältström Head of Research and Development Netnod Begin forwarded message: > From: <entr-csr(a)ec.europa.eu> > Subject: From the European Commission: human rights guidance for 3 business sectors > Date: 17 juni 2013 18:23:09 CEST > To: <entr-csr(a)ec.europa.eu> > > We are pleased to announce the publication of the European Commission Sector Guides on Implementing the UN Guiding Principles on Business and Human Rights. > > > Download the Guides here: http://ec.europa.eu/enterprise/newsroom/cf/itemdetail.cfm?item_id=6711&lang… > > The Guides – for employment and recruitment agencies, ICT companies, and oil and gas companies – were developed over the past 18 months by Shift and IHRB through extensive research and multistakeholder consultation with representatives from the three industries as well as governments, trade unions, civil society, academia and other experts. Read more about the Guides’ development here. > > Each Guide offers practical advice on how to implement the corporate responsibility to respect human rights in day-to-day business operations in each industry through step-by-step guidance. At each step, they summarise what the UN Guiding Principles expect, offer a range of approaches and examples for how to put them into practice, and link users to additional resources that can support their work. They are intended to help companies “translate” respect for human rights into their own systems and cultures. > > Many thanks to all those who have contributed to this process. > > Best regards, > > > CSR Team > > European Commission > Enterprise and Industry Directorate-General > Unit ENTR.D.1 >

6 12

WannaCry Ransomware
by Richard Leaning 23 May '17

23 May '17

Dear Colleagues, The European cybercrime centre at Europol have asked us to circulate the below. I hope you find it useful and please forward it on to anyone who you may think will benefit from it. Kind regards Richard Leaning External Relations RIPE NCC > Begin forwarded message: > > From: "O3 - European Cybercrime Centre (EC3)" <o3(a)europol.europa.eu> > Subject: @EXT: WannaCry Ransomware > Date: 14 May 2017 at 19:06:20 BST > Cc: "Amann, Philipp" <Philipp.Amann(a)europol.europa.eu>, Mounier, Grégory <gregory.mounier(a)europol.europa.eu>, "Sanchez, Maria" <maria.sanchez(a)europol.europa.eu>, "O372 Advisory Groups Support" <O372(a)europol.europa.eu> > > Dear AG members, > > As you are no doubt aware, we are currently experiencing an unprecedented ransomware attack at a global scale. The malware was detected on 12 May 2017 and has the capability to spread across networks taking advantage of a critical exploit in a popular communication protocol used by Windows systems. > > Many of you have already reached out and are actively involved in containing this threat. However, since we believe that the infection and propagation rate may go up on Monday when people return to their workplaces, we would like to ask you to please help us distribute information that can help contain this threat. To this end, we have compiled a list of recommendations and also prepared an infographic (see attachment). Please feel free to use this information for reaching out to your network and to complement your advice, if and where useful. > > Also, the No More Ransom (NMR) initiative, actively supported by many of you already, remains an essential source of information. Together with you and other partners, we will continue to update the information available via the NMR portal, so it is important to watch this space as well. > > If you want to share any other prevention, protection or awareness information with us, please do not hesitate to contact us. > > Thank you again for your continued support. > > Kind regards, > EC3 Outreach & Support > > -------------------------------- > > If you are a victim or have reason to believe that you could be a victim > > This is link provides some practical advice on how to contain the propagation of this type of ransomware: https://www.ncsc.gov.uk/guidance/ransomware-latest-ncsc-guidance <https://www.ncsc.gov.uk/guidance/ransomware-latest-ncsc-guidance> > > The most important step involves patching the Microsoft vulnerability (MS17-010): > https://technet.microsoft.com/en-us/library/security/ms17-010.aspx <https://technet.microsoft.com/en-us/library/security/ms17-010.aspx> > > A patch for legacy platforms is available here: > https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-w… <https://blogs.technet.microsoft.com/msrc/2017/05/12/customer-guidance-for-w…> > > In instances where it is not possible to install the patch, manage the vulnerability becomes key. One way of doing this would be to disable the SMBv1 (Server Message Block) protocol: > https://support.microsoft.com/en-us/help/2696547 <https://support.microsoft.com/en-us/help/2696547> > and/or block SMBv1 ports on network devices [UDP 137, 138 and TCP 139, 445]. > > Another step would be to update endpoint security and AV solutions with the relevant hashes of the ransomware (e.g. via VirusTotal). > > If these steps are not possible, not starting up and/or shutting down vulnerable systems can also prevent the propagation of this threat. > > How to prevent a ransomware attack? > > Back-up! Back-up! Back-up! Have a backup and recovery system in place so a ransomware infection can’t destroy your personal data forever. It’s best to create at least two back-up copies on a regular basis: one to be stored in the cloud (remember to use a service that makes an automatic backup of your files) and one stored locally (portable hard drive, thumb drive, etc.). Disconnect these when you are done and store them separately from your computer. Your back-up copies will also come in handy should you accidentally delete a critical file or experience a hard drive failure. > Use robust antivirus software to protect your system from ransomware. Always use the latest virus definition/database and do not switch off the ‘heuristic’ functions as these help the solution to catch samples of ransomware (and other type of malware) that have not yet been formally detected. > Keep all the software on your computer up to date. When your operating system (OS) or applications release a new version, install it. If the software you use offers the option of automatic updating, enable it. > Trust no one. Literally. Any account can be compromised and malicious links can be sent from the accounts of friends on social media, colleagues or an online gaming <https://blog.kaspersky.com/teslacrypt-20-ransomware/9314/> partner. Never open attachments in emails from someone you don’t know. Similarly, don’t open attachments in emails from somebody you know but from whom you would not expect to receive such as message. Cybercriminals often distribute fake email messages that look very much like email notifications from an online store, a bank, the police, a court or a tax collection agency, luring recipients into clicking on a malicious link and releasing the malware into their system. If in doubt, call the sender at a trusted phone number to confirm the legitimacy of the message received. > Enable the ‘Show file extensions’ option in the Windows settings on your computer. This will make it much easier to spot potentially malicious files. Stay away from file extensions like ‘.exe’, ‘.com’, ‘.vbs’ or ‘.scr’. Cybercriminals can use several extensions to disguise a malicious file as a video, photo, or document (like hot-chics.avi.exe or report.doc.scr). > If you discover a rogue or unknown process on your machine, disconnect it immediately from the internet or other network connections (such as home Wi-Fi) — this will prevent the infection from spreading. > > > > > ******************* > > DISCLAIMER : This message is sent in confidence and is only intended for the named recipient. If you receive this message by mistake, you may not use, copy, distribute or forward this message, or any part of its contents or rely upon the information contained in it. > Please notify the sender immediately by e-mail and delete the relevant e-mails from any computer. This message does not constitute a commitment by Europol unless otherwise indicated. > > *******************

3 2

New IPv6 Support for Governments Programme
by Mirjam Kuehne 17 May '17

17 May '17

Dear colleagues, Governments planning IPv6 deployments can now access assistance through our new IPv6 Support for Governments Programme. This is part of our ongoing efforts to work more closely with governments and encourage IPv6 adoption throughout our service region. We have explained our approach in more detail in a RIPE Labs article here: https://labs.ripe.net/Members/arne_kiessling/ipv6-support-for-governments-p… We have also documented this on our website here: https://www.ripe.net/manage-ips-and-asns/ipv6/ipv6-for-governments If you represent a government that is planning to make an IPv6 allocation request, please get in touch with us by emailing <IPv6forGov(a)ripe.net>. Kind regards, Mirjam Kuhne RIPE NCC

1 0

Re: [cooperation-wg] cooperation-wg Digest, Vol 64, Issue 1
by Corinne Cath 04 May '17

04 May '17

Dear all, I have been heavily involved in that IEEE work, do let me know if you would like more info on it. Best, On Thu, May 4, 2017 at 11:00 AM, <cooperation-wg-request(a)ripe.net> wrote: > Send cooperation-wg mailing list submissions to > cooperation-wg(a)ripe.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ripe.net/mailman/listinfo/cooperation-wg > or, via email, send a message with subject or body 'help' to > cooperation-wg-request(a)ripe.net > > You can reach the person managing the list at > cooperation-wg-owner(a)ripe.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cooperation-wg digest..." > > > Today's Topics: > > 1. Re: [iot-discussion] Cerf on the ethics of IoT (Filiz Yilmaz) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 4 May 2017 11:00:22 +0200 > From: Filiz Yilmaz <koalafil(a)gmail.com> > To: Marco Hogewoning <marcoh(a)ripe.net>, cooperation-wg(a)ripe.net > Cc: iot-discussion(a)ripe.net > Subject: Re: [cooperation-wg] [iot-discussion] Cerf on the ethics of > IoT > Message-ID: > <CAHWoQeNdJShaUR0vBtFy_Tbqz=NJKusGbnyN7YtgjL0ZHgxoHw@mail. > gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi Marco, all, > > Apologies if this was noted in these lists before: > > There is also an IEEE initiative which was open for public comments up > until recently, on a related note: > > The IEEE Global Initiative for Ethical Considerations in Artificial > Intelligence and Autonomous Systems > > http://standards.ieee.org/develop/indconn/ec/autonomous_systems.html > > Wanted to share. > > Kind regards > Filiz > > > > On Thu, May 4, 2017 at 10:32 AM, Marco Hogewoning <marcoh(a)ripe.net> wrote: > > > Dear colleagues, > > > > Somebody drew my attention to an article by Vint Cerf and Francine Berman > > on the ethics of IoT, some of you might find it an interesting read as > well. > > > > http://www.cs.rpi.edu/~bermaf/Berman+Cerf_IoT.pdf > > > > Following this, an interview with Berman was published on The Atlantic > > earlier this week > > > > https://www.theatlantic.com/technology/archive/2017/05/ > > internet-of-things-ethics/524802/ > > > > As a reminder, we are still setup to have a BoF aiming to discuss some of > > this space as well, in particular the expected or desired role of the > > parties providing connectivity to these devices. > > > > This ?IoT Security BoF? will take place after the main RIPE 74 program, > on > > Tuesday May 9 at 18:00 in the Tutorial Room of the meeting venue. > > Unfortunately, due to this being a BoF and as this room only has a very > > limited technical setup there won?t be any remote participation offered. > > > > So hope to see many of you in the room in Budapest next week, > > > > Groet, > > > > MarcoH > > > > > > _______________________________________________ > > iot-discussion mailing list > > iot-discussion(a)ripe.net > > https://lists.ripe.net/mailman/listinfo/iot-discussion > > >

1 0

Re: [cooperation-wg] [iot-discussion] Cerf on the ethics of IoT
by Filiz Yilmaz 04 May '17

04 May '17

Hi Marco, all, Apologies if this was noted in these lists before: There is also an IEEE initiative which was open for public comments up until recently, on a related note: The IEEE Global Initiative for Ethical Considerations in Artificial Intelligence and Autonomous Systems http://standards.ieee.org/develop/indconn/ec/autonomous_systems.html Wanted to share. Kind regards Filiz On Thu, May 4, 2017 at 10:32 AM, Marco Hogewoning <marcoh(a)ripe.net> wrote: > Dear colleagues, > > Somebody drew my attention to an article by Vint Cerf and Francine Berman > on the ethics of IoT, some of you might find it an interesting read as well. > > http://www.cs.rpi.edu/~bermaf/Berman+Cerf_IoT.pdf > > Following this, an interview with Berman was published on The Atlantic > earlier this week > > https://www.theatlantic.com/technology/archive/2017/05/ > internet-of-things-ethics/524802/ > > As a reminder, we are still setup to have a BoF aiming to discuss some of > this space as well, in particular the expected or desired role of the > parties providing connectivity to these devices. > > This “IoT Security BoF” will take place after the main RIPE 74 program, on > Tuesday May 9 at 18:00 in the Tutorial Room of the meeting venue. > Unfortunately, due to this being a BoF and as this room only has a very > limited technical setup there won’t be any remote participation offered. > > So hope to see many of you in the room in Budapest next week, > > Groet, > > MarcoH > > > _______________________________________________ > iot-discussion mailing list > iot-discussion(a)ripe.net > https://lists.ripe.net/mailman/listinfo/iot-discussion >

1 0