The use of certification and labelling can encourage better
understanding and transparency in terms of IoT security
and can additionally benefit end users and consumers by
educating them and making them more aware of IoT
security. Alternatively and perhaps complementarily,
liability laws can be strengthened and modernised to hold
manufacturers accountable in the event of a breach.
Certification
Liability
Figure 9: Regulatory Approaches to IoT Security
Regardless of the regulatory approach adopted, it is
important for cybersecurity regulators as well as the
industry to work together and act as a global community
that learns from incidents and vulnerabilities proactively.
This requires an open culture of sharing incidents and
mutual learning.
Liability
Product liability is the area of law in which manufacturers,
distributors, suppliers, retailers, and others who make
products available to the public are held responsible for
damage caused by those products. The Dutch roadmap for
safe hardware and software154 has identified liability laws
as a key driver for IoT security.
50
154 https://www.rijksoverheid.nl/documenten/rapporten/2018/04/02/
roadmap-digitaal-veilige-hard-en-software - Roadmap digitaal veilige hard en
software, 2018. By Ministry of Economic Affairs, the Netherlands, in Dutch.
155 https://en.wikipedia.org/wiki/Strict_liability
Liability litigation historically focused on negligence on the
part of the vendor, or a breach of warranty. Under the notion
of strict liability, the manufacturer is liable if the product is
defective even if the manufacturer was not negligent in
making that product defective155. The manufacturer thus
becomes a de facto insurer against its defective products,
with premiums built into the product's price. Strict liability
also seeks to diminish the impact of information asymmetry
between manufacturers and consumers: manufacturers
have better knowledge of their own products' dangers than
do consumers; therefore, manufacturers should bear the
burden of finding, correcting, and warning consumers of
those dangers.
The 1985 European Product Liability Directive156 created a
regime of strict liability for defective products: according
to this Directive, a product is “defective” when it does not
provide the “safety which a person is entitled to expect”
(Article 6). While one may assume that this provides a
baseline of liability for IoT devices, the use of the term
“safety” is telling – security issues that are not outright
safety defects may not be addressed at all unless those
security issues can be proven to cascade into safety losses
or traditional damage such as harm to human health or
property. Even more fundamentally, Article 2 of the
Directive states that it applies to “movables” – while this
may have seemed perfectly reasonable in the 80s for
products such as toasters or lawn mowers, for modern
connected devices this terminology may entirely exclude
the connectivity and server-side components. A recent EU
research report157 identifies that vendors may take
advantage of this by simply placing critical functionality on
the server in order to escape liability.
156 Council Directive 85/374/EEC of 25 July 1985 on the approximation of the
laws, regulations and administrative provisions of the Member States
concerning liability for defective products, https://eur-lex.europa.eu/
LexUriServ/LexUriServ.do?uri=CELEX:31985L0374:en:HTML
157 Standardisation and Certification of Safety, Security and Privacy in the
‘Internet of Things’, JRC Technical Report, Leverett et al.
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents