Counting the costs of a cyber breach
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
<record>
<leader>00000cab a2200000 4500</leader>
<controlfield tag="001">MAP20170026679</controlfield>
<controlfield tag="003">MAP</controlfield>
<controlfield tag="005">20170825124131.0</controlfield>
<controlfield tag="008">170817e20170703sgp|||p |0|||b|eng d</controlfield>
<datafield tag="040" ind1=" " ind2=" ">
<subfield code="a">MAP</subfield>
<subfield code="b">spa</subfield>
<subfield code="d">MAP</subfield>
</datafield>
<datafield tag="084" ind1=" " ind2=" ">
<subfield code="a">86</subfield>
</datafield>
<datafield tag="245" ind1="0" ind2="0">
<subfield code="a">Counting the costs of a cyber breach</subfield>
</datafield>
<datafield tag="300" ind1=" " ind2=" ">
<subfield code="a">2 p.</subfield>
</datafield>
<datafield tag="520" ind1=" " ind2=" ">
<subfield code="a">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.</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20140022700</subfield>
<subfield code="a">Ciberseguridad</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20080557515</subfield>
<subfield code="a">Cibernética</subfield>
</datafield>
<datafield tag="650" ind1=" " ind2="4">
<subfield code="0">MAPA20160007633</subfield>
<subfield code="a">Ciberriesgos</subfield>
</datafield>
<datafield tag="773" ind1="0" ind2=" ">
<subfield code="w">MAP20090003767</subfield>
<subfield code="t">Asia insurance review</subfield>
<subfield code="d">Singapore : Ins Communications Pte Ltd., 2009-</subfield>
<subfield code="x">0218-2696</subfield>
<subfield code="g">03/07/2017 Número 7 - julio 2017 , p. 85-86</subfield>
</datafield>
</record>
</collection>