14,932
edits
Changes
→IoT and ICANN
IoT devices exchange data with remote services hosted on the Internet and locate these services via the DNS protocol. They operate across two ecosystems: the DNS (and its resolver operators, authoritative name server operators, and domain registration providers) and the IoT (and its device manufacturers, device operators, and remote service providers). IoT deployments introduce new security, availability, and transparency requirements because they interact with physical space, providing an opportunity for the DNS because it is a globally pervasive infrastructure.<ref>[https://www.caida.org/catalog/papers/2020_dns_in_iot/dns_in_iot.pdf The DNS in IoT, Caida, December 2020]</ref> But, IoT devices also present major risks. IoT device engineers may use the DNS naively to operate their applications or misconfigure resolvers to accept DNS queries from anyone, overwhelming the DNS. Or [[threat Actor|threat actors]] can intentionally use IoT devices as a platform for large-scale [[DDoS Attack]]s.<ref>[https://www.dnsfilter.com/blog/dns-security-internet-of-things#:~:text=IoT%20and%20DDoS,for%20network%20availability%2C%20for%20example. DNS Security and the IoT, DNS Filter Blog]</ref>
IoT devices exchange data with remote services hosted on the Internet and locate these services via the DNS protocol. They operate across two ecosystems: the DNS (and its resolver operators, authoritative name server operators, and domain registration providers) and the IoT (and its device manufacturers, device operators, and remote service providers). IoT deployments introduce new security, availability, and transparency requirements because they interact with physical space, providing an opportunity for the DNS because it is a globally pervasive infrastructure.<ref>[https://www.caida.org/catalog/papers/2020_dns_in_iot/dns_in_iot.pdf The DNS in IoT, Caida, December 2020]</ref> But, IoT devices also present major risks. IoT device engineers may use the DNS naively to operate their applications or misconfigure resolvers to accept DNS queries from anyone, overwhelming the DNS. Or [[threat Actor|threat actors]] can intentionally use IoT devices as a platform for large-scale [[DDoS Attack]]s.<ref>[https://www.dnsfilter.com/blog/dns-security-internet-of-things#:~:text=IoT%20and%20DDoS,for%20network%20availability%2C%20for%20example. DNS Security and the IoT, DNS Filter Blog]</ref>
==IoT and ICANN==
==IoT and ICANN==
The IoT operates outside [[ICANN]]'s remit. In SAC105, the SSAC explained that the IoT differs greatly from traditional Internet applications such as email and [[web]] browsing, but ultimately a significant number of IoT deployments will use the [[DNS]] to locate remote services to enable telemetry data transmission and collection for monitoring and analysis of sensor data.<ref>[https://www.icann.org/en/system/files/files/sac-105-en.pdf SAC105, SSAC, ICANN]</ref> The publication recommends: # developing a DNS library for IoT devices; # training IoT DNS professionals; # creating a shared system that enables DNS operators to share information on IoT botnets; # constructing a system to enable DNS operators to handle [[DDoS Attack]]s involving IoT devices; and # producing a system that enables DNS operators to measure how IoT uses the DNS.<ref>[https://dig.watch/updates/icann-issues-report-iot-implications-dns ICANN Report on IoT Implications for the DNS, Digital Watch]</ref>
The IoT operates outside [[ICANN]]'s remit. In SAC105, the SSAC explained that the IoT differs greatly from traditional Internet applications such as email and [[web]] browsing, but ultimately a significant number of IoT deployments will use the [[DNS]] to locate remote services to enable telemetry data transmission and collection for monitoring and analysis of sensor data.<ref>[https://www.icann.org/en/system/files/files/sac-105-en.pdf SAC105, SSAC, ICANN]</ref> The publication recommends:
# developing a DNS library for IoT devices;
# training IoT DNS professionals; # creating a shared system that enables DNS operators to share information on IoT botnets;
# constructing a system to enable DNS operators to handle [[DDoS Attack]]s involving IoT devices; and
# producing a system that enables DNS operators to measure how IoT uses the DNS.<ref>[https://dig.watch/updates/icann-issues-report-iot-implications-dns ICANN Report on IoT Implications for the DNS, Digital Watch]</ref>
In a sponsored article, Wired Magazine outlined how building bridges and other integral infrastructure with "smart cement", using sensors involved in M2M would result in superior, more thorough tracking of bridge quality and strength. This could potentially alert engineers to any issues with structural integrity--ensuring the ability to monitor cracks and stresses. <ref>[http://www.wired.com/insights/2014/11/the-internet-of-things-bigger/ The Internet of Things. Retrieved 18 October 2015.]</ref>
In a sponsored article, Wired Magazine outlined how building bridges and other integral infrastructure with "smart cement", using sensors involved in M2M would result in superior, more thorough tracking of bridge quality and strength. This could potentially alert engineers to any issues with structural integrity--ensuring the ability to monitor cracks and stresses. <ref>[http://www.wired.com/insights/2014/11/the-internet-of-things-bigger/ The Internet of Things. Retrieved 18 October 2015.]</ref>
==IoT and Web3 Techologies==
==IoT and Web3 Techologies==