Tackling the challenges of cyber modelling : the uniqueness of cyber risks

<?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>
<title>Tackling the challenges of cyber modelling</title>
<subTitle>: the uniqueness of cyber risks</subTitle>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">esp</placeTerm>
</place>
<dateIssued encoding="marc">2017</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">Although the industry is evolving in regards to cyber modelling, there is still a distinct lack of awareness. A 2016 Captive Cyber Survey showed that 60% of large businesses still do not have cyber insurance. Ms Kirstin McMullan of Aon Benfield explains the requirements needed for cyber risk modelling, the two approaches to it and the necessity for cyber risk profiling.</abstract>
<note type="statement of responsibility">Kirstin McMullan</note>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20160007633">
<topic>Ciberriesgos</topic>
</subject>
<classification authority="">7</classification>
<relatedItem type="host">
<titleInfo>
<title>Asia insurance review</title>
</titleInfo>
<originInfo>
<publisher>Singapore : Ins Communications Pte Ltd., 2009-</publisher>
</originInfo>
<identifier type="issn">0218-2696</identifier>
<identifier type="local">MAP20090003767</identifier>
<part>
<text>01/03/2017 Número 3 - marzo 2017 , p. 70-71</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">170405</recordCreationDate>
<recordChangeDate encoding="iso8601">20170426131334.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20170011101</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>