A Policyholder's guide to IoT claims coverage

<?xml version="1.0" encoding="UTF-8"?><modsCollection xmlns="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-8.xsd">
<mods version="3.8">
<titleInfo>
<nonSort xml:space="preserve">A  </nonSort>
<title>Policyholder's guide to IoT claims coverage</title>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">esp</placeTerm>
</place>
<dateIssued encoding="marc">2018</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
</physicalDescription>
<abstract displayLabel="Summary">According to some estimates, by 2020, the internet of things (IoT) will encompass more than 50 billion devices. But as the technology becomes more common, headlines regarding the risks of loT-enabled products are becoming more frequent, such as reports that Arnazon's digital assistant  Alexa "misheard" a toddler's inquiry and proceeded to teach him profanity  or cases where autonomous cars have been involved in accidents. Manufacturers of consumer goods, such as wearable fitness devices, baby monitors and "smart" appliances, and businesses like power plants and hospitals should be concerned about the risks associated with the use of such technology as well. In Iight of increasing liability concerns, policyholders need to examine their existing insurance policies and consider changes that expand or clarify coverage for possible IoT claims</abstract>
<note type="statement of responsibility">Catherine Serafin</note>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080556402">
<topic>Seguro D&O</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080627638">
<topic>Seguro de responsabilidad civil</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080545260">
<topic>Riesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080586546">
<topic>Nuevas tecnologías</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20150010735">
<topic>Internet de las cosas</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080567118">
<topic>Reclamaciones</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20170003779">
<topic>Seguro de ciberriesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080662257">
<topic>Interrupción de negocio</topic>
</subject>
<classification authority="">33</classification>
<relatedItem type="host">
<titleInfo>
<title>Risk Management Magazine</title>
</titleInfo>
<originInfo>
<publisher>New York : Risk and Insurance Management Society, 1982-</publisher>
</originInfo>
<identifier type="issn">0035-5593</identifier>
<identifier type="local">MAP20077000291</identifier>
<part>
<text>01/02/2018 Volumen 65 Número 1 - enero/febrero 2018 , p. 8-9</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">180322</recordCreationDate>
<recordChangeDate encoding="iso8601">20180503151850.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20180008979</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>