Insuring against social engineering attacks

<?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">MAP20170016748</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20170621130141.0</controlfield>
    <controlfield tag="008">170530e20170501esp|||p      |0|||b|spa 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">7</subfield>
    </datafield>
    <datafield tag="100" ind1=" " ind2=" ">
      <subfield code="0">MAPA20170006220</subfield>
      <subfield code="a">Kandel, Elan</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Insuring against social engineering attacks</subfield>
      <subfield code="c">Elan Kandel, Alexander Selarnick</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">Despite the rise of social engineering, many businesses are still not prepared, or insured, for these risks, which can involve coses such as revenue loss, business disruption, legal fees, public relations expenses and forensic analysis. When such an attack occurs, policyholders have historically turned to their crime insurance policies for coverage. Social engineering attacks may fall outside che scope of coverage afforded by tradicional crime policies, however </subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080591182</subfield>
      <subfield code="a">Gerencia de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080629755</subfield>
      <subfield code="a">Seguro de riesgos extraordinarios</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080587628</subfield>
      <subfield code="a">Riesgo tecnológico</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080611088</subfield>
      <subfield code="a">Ingeniería de seguridad</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="w">MAP20077000291</subfield>
      <subfield code="t">Risk Management Magazine</subfield>
      <subfield code="d">New York : Risk and Insurance Management Society, 1982-</subfield>
      <subfield code="x">0035-5593</subfield>
      <subfield code="g">01/05/2017 Volumen 64 Número 5 - mayo 2017 , p. 12-14</subfield>
    </datafield>
  </record>
</collection>