<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Marco,<div class=""><br class=""></div><div class="">I don’t think it’s RIPE’s and this working group’s purpose to get into the name & shame game. In my opinion we should define technical solutions that can be applied to address the security issues introduced by insecure devices.</div><div class=""><br class=""></div><div class="">Ideally such solutions would affect the device operations in a way (i.e. initiall limiting&denying cloud access) that forces vendors to react - I’m not very enthusiatic about this but it’s a possibility… and would require wide adoption of the related technologies.</div><div class=""><br class=""></div><div class="">- Peter<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 10.10.2018 um 13:35 schrieb Marco Hogewoning <<a href="mailto:marcoh@ripe.net" class="">marcoh@ripe.net</a>>:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">On 10 Oct 2018, at 13:21, Peter Steinhäuser <<a href="mailto:ps@embedd.com" class="">ps@embedd.com</a>> wrote:<br class=""><br class="">Naming & Shaming can raise awareness but will unlikely help a lot solving the issue in general. I think we have to<br class="">live with the fact that there are many vendors that don’t care about security as long as it does not affect their revenue<br class="">stream.<br class=""></blockquote><br class="">Think is partially a question on who you shame them to and which name you use.<br class=""><br class="">Reputation could be made into one of the drivers for consumers, but I fear that the real problematic space is with the low cost generic OEM items that get branded and sold in a million different varieties.<br class=""><br class="">Industry itself might be easier, but also probably far less of a problem area to begin with. Also because there appears to be a bit more awareness growing with regards to risk and compliance with (existing) regulations.<br class=""><br class="">And then of course there is the risk of naming & shaming itself. Things might backfire in that you actually trigger policy measures that also have impact on “the good ones” or, given the stakes are quite high and lots of money gets put in these “solutions”, there will be legal pressure on the messenger. Especially if you aim to address end users and the retail market places.<br class=""><br class="">How hard would you need to push to get a product out of the market this way? And what if you succeed?<br class=""><br class="">Also not sure how RIPE would fit in this picture. You could of course position the community as a place to collect issues and verify them by means of discussion, but would that be something this Working Group would be willing to engage in?<br class=""><br class="">MarcoH<br class="">(RIPE NCC, but in this case just thinking out loud)<br class="">_______________________________________________<br class="">iot-wg mailing list<br class=""><a href="mailto:iot-wg@ripe.net" class="">iot-wg@ripe.net</a><br class="">https://mailman.ripe.net/</div></div></blockquote></div><div class=""><div id="sig" style="border-top: dotted 1px #999999; padding-top: 10px; padding-botton: 10px; margin: 11px 0; font-family: 'Lucida Grande', Verdana, Arial, Sans-Serif; font-size: 11px;" class=""><img src="https://www.dropbox.com/s/tgpbappyzk8y5za/embeDD_mail_sig.png?raw=1" width="180" height="38" align="left" style="margin-right: 20px; padding-top: 2px;" class=""> <div style="color: #999999;" class="">
<strong style="color: #333333;" class="">Peter Steinhäuser, CEO</strong><br class=""> embeDD GmbH · Alter Postplatz 2 · 6370 Stans · Switzerland<br class=""> Phone: +41 (41) 784 95 85 · Fax: +41 (41) 784 95 64 </div> <div style="clear: both;" class=""></div> </div>
</div>
<br class=""></div></body></html>