This paper investigates how and with whom IoT devices communicate and how their location affects their communication patterns. Specifically, the endpoints an IoT device communicates with can be defined as a small set of domains. To study how the location of the device affects its domain set, we distinguish between the location based on its IP address and the location defined by the user when registering the device. We show, unlike common wisdom, that IP-based location has little to no effect on the set of domains, while the user-defined location changes the set significantly. Unlike common approaches to resolving domains to IP addresses at close-by geo-locations (such as anycast), we present a distinctive way to use the ECS field of EDNS to achieve the same differentiation between user-defined locations. Our solution streamlines the network design of IoT manufacturers and makes it easier for security appliances to monitor IoT traffic. Finally, we show that with one domain for all locations, one can achieve succinct descriptions of the traffic of the IoT device across the globe. We will discuss the implications of such description on security appliances and specifically, on the ones using the Manufacturer Usage Description (MUD) framework.
翻译:本文调查了IoT设备是如何与谁沟通的,以及它们的位置如何影响通信模式。 具体地说, IoT设备与一个IoT设备沟通的端点可以定义为一小组域。 为了研究该设备的位置如何影响其域集,我们根据IP地址区分了位置和用户在登记该设备时界定的位置。 我们与通常的智慧不同, 基于 IP 的位置对一组域没有多大影响, 而用户定义的位置会大大改变这套域集。 与在地理位置(如任何播种)上解决IP地址域的通用方法不同, 我们提出一种独特的方法, 使用ESS 域来在用户定义的位置之间实现相同的区别。 我们的解决方案简化了IoT制造商的网络设计,并使安全设备更容易监测 IoT 交通。 最后, 我们显示, 在所有地点使用一个域, 就可以对IoT设备在全球各地的交通进行简洁描述。 我们将讨论这种描述对安全设备的影响, 具体地说, 对使用Mrker Usinger Usation(MUA) 框架的用户。