IEEE Technology and Society Magazine - June 2018 - 75

development costs in this area are high. They are more
likely to move quickly to the next, more advanced version of their models because that is where the greatest
profit lies. The performance of previous models is not
likely to concern them, particularly once they're out of
warranty. Manufacturers are also aware that consumers
who own webcams and digital video recorders used in
DDoS attacks do not personally know the victims, and
are not likely to pay too much attention to security features. In such cases, security is something that affects
people who are not involved in the transaction between
buyer and seller - an "externality" in economic terms.
Insurers should reconsider their approach to manufacturers and consumers of IoT devices. The cyber insurance
market is said to be worth $3 billion to $4 billion per year,
and is growing at 60 percent annually [10]. Companies
that sell IoT devices may need to be insured against the
possibility that their products may cause harm to their
customers, or others. Effective policy is needed to ensure
businesses that produce devices unfit for purpose, or that
are repeatedly hacked, cannot continue to do so. A business that is compromised, but has taken reasonable
steps to resolve the issue - and shows no negligence -
should be able to claim on its insurance.
Recently IoT devices have also been made available
for extremely intimate and sexual applications with
devices enabling remote logging and control [11], even
incorporating cameras. In this context other security
researchers have identified significant flaws in the
implementation of connectivity, privacy, and data management, which they argue is through the poor choice
of source code reused from public repositories [12]. In
one case privacy protections in the U.S. meant that customers could receive compensation for breaches of
their usage data after a court finding that the breach
had not been disclosed to customers.
In this context the potential for serious sexual
assault leaves device manufacturers clearly open to
adverse judgement and reputational damage even if
perpetrators of such crimes are difficult to identify
and pursue.
For these and other reasons, there may be no feasible market based solution to the issue of poor IoT security, meaning the onus may fall on regulators.

Proposal
Resolution of the security risks identified in our study is
hampered by the siloed nature of regulation that is now
becoming more broadly applicable due to the expansion of communications and forming the IoT. Functions
and objects are the responsibility of discrete government departments and regulatory agencies, but the
agencies now find themselves potentially responsible
for new areas. Further exacerbating this problem is that
JUNE 2018

∕

regulatory standards and benchmarks that apply in one
jurisdiction do not necessarily apply within another.
Medical, traffic control, and building management
systems, cameras, light bulbs and cars with driver-assist
features use an increasing number of IoT devices, yet
are regulated by separate government departments. In
Australia for example, the Therapeutic Goods Administration within the Department of Health regulates medical devices, whereas the Australian Communications
and Media Authority regulates telecommunications,
broadcasting, radio communications, and the Internet,
and the Australian Competition and Consumer Commission regulates consumer safety and fair trade. Regulating IoT devices will involve input from elements within
each of these entities, and complexity is only likely to
increase over time. The Australian government Department of Infrastructure and Regional Development regulates vehicle safety, and may require real-time access to
data feeds from vehicles using IoT devices. As driverassistance technologies develop in cars, the need for
cross-departmental attention will increase. As in Australia, today's regulatory agencies across the world were
created to respond to the rise of earlier technologies.
The coming IoT revolution will require new regulatory
expertise that cuts across the current set of agencies.
We therefore propose a more coordinated and exhortative approach to regulation. Manufacturers will
need to be encouraged to build security at the design
phase. A "security by default" attitude would see consumers having to deliberately disable rather than deliberately enable security features. A mechanism may
need to be found to coordinate software updates
among third-party vendors, and to facilitate the coordinated disclosure of vulnerabilities. Here, a role may be
found for national cybersecurity agencies, such as the
Australian Cyber Security Centre, to coordinate the
security knowledge-sharing of developers, manufacturers, and service providers.
Bodies and services that may have been exempt in
the past from regulation may also come under future
scrutiny due to the evolving need for consumer and
community protection. Because of the serious threat to
infrastructure, it is conceivable that governments may in
the future require Internet service provider networks to
comply with network security standards or meet performance benchmarks. Devices provided by manufacturers or Internet service providers to perform network
boundary roles, such as home gateways, could be
expected to come under higher levels of requirements.
This would mean devices shipped with default passwords, for example, could become a thing of the past.
Further research along the lines of the STEP model is
needed in order to continue to shed light on the burgeoning field of IoT devices.

IEEE Technology and Society Magazine

75



Table of Contents for the Digital Edition of IEEE Technology and Society Magazine - June 2018

Contents
IEEE Technology and Society Magazine - June 2018 - Cover1
IEEE Technology and Society Magazine - June 2018 - Cover2
IEEE Technology and Society Magazine - June 2018 - 1
IEEE Technology and Society Magazine - June 2018 - Contents
IEEE Technology and Society Magazine - June 2018 - 3
IEEE Technology and Society Magazine - June 2018 - 4
IEEE Technology and Society Magazine - June 2018 - 5
IEEE Technology and Society Magazine - June 2018 - 6
IEEE Technology and Society Magazine - June 2018 - 7
IEEE Technology and Society Magazine - June 2018 - 8
IEEE Technology and Society Magazine - June 2018 - 9
IEEE Technology and Society Magazine - June 2018 - 10
IEEE Technology and Society Magazine - June 2018 - 11
IEEE Technology and Society Magazine - June 2018 - 12
IEEE Technology and Society Magazine - June 2018 - 13
IEEE Technology and Society Magazine - June 2018 - 14
IEEE Technology and Society Magazine - June 2018 - 15
IEEE Technology and Society Magazine - June 2018 - 16
IEEE Technology and Society Magazine - June 2018 - 17
IEEE Technology and Society Magazine - June 2018 - 18
IEEE Technology and Society Magazine - June 2018 - 19
IEEE Technology and Society Magazine - June 2018 - 20
IEEE Technology and Society Magazine - June 2018 - 21
IEEE Technology and Society Magazine - June 2018 - 22
IEEE Technology and Society Magazine - June 2018 - 23
IEEE Technology and Society Magazine - June 2018 - 24
IEEE Technology and Society Magazine - June 2018 - 25
IEEE Technology and Society Magazine - June 2018 - 26
IEEE Technology and Society Magazine - June 2018 - 27
IEEE Technology and Society Magazine - June 2018 - 28
IEEE Technology and Society Magazine - June 2018 - 29
IEEE Technology and Society Magazine - June 2018 - 30
IEEE Technology and Society Magazine - June 2018 - 31
IEEE Technology and Society Magazine - June 2018 - 32
IEEE Technology and Society Magazine - June 2018 - 33
IEEE Technology and Society Magazine - June 2018 - 34
IEEE Technology and Society Magazine - June 2018 - 35
IEEE Technology and Society Magazine - June 2018 - 36
IEEE Technology and Society Magazine - June 2018 - 37
IEEE Technology and Society Magazine - June 2018 - 38
IEEE Technology and Society Magazine - June 2018 - 39
IEEE Technology and Society Magazine - June 2018 - 40
IEEE Technology and Society Magazine - June 2018 - 41
IEEE Technology and Society Magazine - June 2018 - 42
IEEE Technology and Society Magazine - June 2018 - 43
IEEE Technology and Society Magazine - June 2018 - 44
IEEE Technology and Society Magazine - June 2018 - 45
IEEE Technology and Society Magazine - June 2018 - 46
IEEE Technology and Society Magazine - June 2018 - 47
IEEE Technology and Society Magazine - June 2018 - 48
IEEE Technology and Society Magazine - June 2018 - 49
IEEE Technology and Society Magazine - June 2018 - 50
IEEE Technology and Society Magazine - June 2018 - 51
IEEE Technology and Society Magazine - June 2018 - 52
IEEE Technology and Society Magazine - June 2018 - 53
IEEE Technology and Society Magazine - June 2018 - 54
IEEE Technology and Society Magazine - June 2018 - 55
IEEE Technology and Society Magazine - June 2018 - 56
IEEE Technology and Society Magazine - June 2018 - 57
IEEE Technology and Society Magazine - June 2018 - 58
IEEE Technology and Society Magazine - June 2018 - 59
IEEE Technology and Society Magazine - June 2018 - 60
IEEE Technology and Society Magazine - June 2018 - 61
IEEE Technology and Society Magazine - June 2018 - 62
IEEE Technology and Society Magazine - June 2018 - 63
IEEE Technology and Society Magazine - June 2018 - 64
IEEE Technology and Society Magazine - June 2018 - 65
IEEE Technology and Society Magazine - June 2018 - 66
IEEE Technology and Society Magazine - June 2018 - 67
IEEE Technology and Society Magazine - June 2018 - 68
IEEE Technology and Society Magazine - June 2018 - 69
IEEE Technology and Society Magazine - June 2018 - 70
IEEE Technology and Society Magazine - June 2018 - 71
IEEE Technology and Society Magazine - June 2018 - 72
IEEE Technology and Society Magazine - June 2018 - 73
IEEE Technology and Society Magazine - June 2018 - 74
IEEE Technology and Society Magazine - June 2018 - 75
IEEE Technology and Society Magazine - June 2018 - 76
IEEE Technology and Society Magazine - June 2018 - 77
IEEE Technology and Society Magazine - June 2018 - 78
IEEE Technology and Society Magazine - June 2018 - 79
IEEE Technology and Society Magazine - June 2018 - 80
IEEE Technology and Society Magazine - June 2018 - 81
IEEE Technology and Society Magazine - June 2018 - 82
IEEE Technology and Society Magazine - June 2018 - 83
IEEE Technology and Society Magazine - June 2018 - 84
IEEE Technology and Society Magazine - June 2018 - 85
IEEE Technology and Society Magazine - June 2018 - 86
IEEE Technology and Society Magazine - June 2018 - 87
IEEE Technology and Society Magazine - June 2018 - 88
IEEE Technology and Society Magazine - June 2018 - Cover3
IEEE Technology and Society Magazine - June 2018 - Cover4
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2023
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2023
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2023
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_december2022
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2022
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2022
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2022
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_december2021
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2021
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2021
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2021
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_december2020
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2020
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2020
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2020
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_december2019
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2019
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2019
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2019
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_december2018
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_september2018
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_june2018
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_march2018
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_winter2017
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_fall2017
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_summer2017
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_spring2017
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_winter2016
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_fall2016
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_summer2016
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_spring2016
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_winter2015
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_fall2015
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_summer2015
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_spring2015
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_winter2014
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_fall2014
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_summer2014
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_spring2014
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_winter2013
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_fall2013
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_summer2013
https://www.nxtbook.com/nxtbooks/ieee/technologysociety_spring2013
https://www.nxtbookmedia.com