Home M3AAWG Blog M3AAWG 5: The Path Forward for IoT Security

Author: Sam Silberman, M3AAWG Treasurer

Welcome to M3AAWG 5, our video series where we connect with leaders and experts on the most pressing topics and issues in online anti-abuse. Today, we’re joined by Brian Scriber, Co-Chair of the IoT SIG and Ash Wilson, Vice Chair of the IoT SIG, to discuss the latest anti-abuse approaches and initiatives within the IoT space. 

Together, Brian and Ash have over 35 years of experience in the IT and Networking security space, and have led industry-wide online anti-abuse collaboration on a wide range of security challenges – both inside and outside of M3AAWG.

Scriber serves as Vice President for Security and Privacy Technologies at CableLabs where he focuses on IoT security, standards, converged network security and the role of technology in privacy policy. Wilson serves as Technical Director over IoT within the Standards and New Technology group at Valimail. Additionally, he works closely with the Internet Engineering Task Force (IETF) to standardize authentication patterns to build a safer Internet for all and is actively involved in the organization’s efforts to standardize DANE for client and sender identity via the DANISH Birds-of-a-Feather group.

With over nearly eight billion connected devices in the world at the end of 2019 – which is expected to balloon to over 24 billion by 2030 – IoT devices present one of the fastest growing technologies today, resulting in questions around the privacy and security of these technologies. In our conversation, we tackle some of the most pressing IoT security matters today, explore the shared responsibility of users, developers and distributors in ensuring the security of connected devices, and delve into the economic incentives to strengthen IoT security.

To get involved with the M3AAWG IoT SIG you can email iot-chair@mailman.m3aawg.org. If you’d like to explore some of the topics and initiatives Brian and Ash discussed in our conversation, you can visit: 


The views expressed in DM3Z are those of the individual authors and do not necessarily reflect M3AAWG policy.