Counting the costs of a cyber breach

<?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>Counting the costs of a cyber breach</title>
</titleInfo>
<typeOfResource>text</typeOfResource>
<genre authority="marcgt">periodical</genre>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">sgp</placeTerm>
</place>
<dateIssued encoding="marc">2017</dateIssued>
<issuance>serial</issuance>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
<extent>2 p.</extent>
</physicalDescription>
<abstract displayLabel="Summary">Cyber risks, and their accompaying costs, are something that many organisations still struggle to fully come to terms with. In attempting to quantify the potential costs of cyberattacks, many businesses are limited to listing the costs of replacing their IT assets, without realising that their software and hardware replacement costs are merely the tip of the proverbial iceberg. It is no wonder that there have been numerous cases of profitable corporations of various sizes having gone the way of the Titanic after experiencing a cyber breach. Mr Kegan Chan of Marsh explains.</abstract>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20140022700">
<topic>Ciberseguridad</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080557515">
<topic>Cibernética</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20160007633">
<topic>Ciberriesgos</topic>
</subject>
<classification authority="">86</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>03/07/2017 Número 7 - julio 2017 , p. 85-86</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">170817</recordCreationDate>
<recordChangeDate encoding="iso8601">20170825124131.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20170026679</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>