Why CISOs should embrace their cyber insurer : 6 steps to start working together today

<?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>Why CISOs should embrace their cyber insurer</title>
<subTitle>: 6 steps to start working together today</subTitle>
</titleInfo>
<name type="corporate" xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20200015185">
<namePart>CyberCube Analytics</namePart>
<nameIdentifier>MAPA20200015185</nameIdentifier>
</name>
<typeOfResource>text</typeOfResource>
<originInfo>
<place>
<placeTerm type="code" authority="marccountry">usa</placeTerm>
</place>
<issuance>monographic</issuance>
<place>
<placeTerm type="text">San Francisco</placeTerm>
</place>
<publisher>CyberCube Analytics</publisher>
<dateIssued>2020</dateIssued>
</originInfo>
<language>
<languageTerm type="code" authority="iso639-2b">eng</languageTerm>
</language>
<physicalDescription>
<form authority="marcform">print</form>
<extent>7 p.</extent>
</physicalDescription>
<abstract displayLabel="Summary">As cyber insurance emerges as an important new line of insurance, partnership between risk managers, information security professional, technology vendors and insurers becomes increasingly important to improving cyber resilience. Security professionals should not see insurers or underwriters as an unwelcome intrusion or big brother' second-guessing a company's security protocols but rather as a partner protecting the firm's assets, sometimes with tens of millions of dollars of the insurers money on the line. It's time for CISOs and insurers to take one step closer and embrace each other in a united front against cybercrime.As cyber insurance emerges as an important new line of insurance, partnership between risk managers, information security professional, technology vendors and insurers becomes increasingly important to improving cyber resilience. Security professionals should not see insurers or underwriters as an unwelcome intrusion or big brother' second-guessing a company's security protocols but rather as a partner protecting the firm's assets, sometimes with tens of millions of dollars of the insurers money on the line. It's time for CISOs and insurers to take one step closer and embrace each other in a united front against cybercrime.</abstract>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20190007504">
<topic>Chief Information Security Officer (CISO)</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="MAPA20080591182">
<topic>Gerencia de riesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080622251">
<topic>Seguridad de la información</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080590567">
<topic>Empresas de seguros</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20140016556">
<topic>Resiliencia</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20160007633">
<topic>Ciberriesgos</topic>
</subject>
<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="MAPA20100017982">
<topic>Riesgos emergentes</topic>
</subject>
<classification authority="">861</classification>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">200702</recordCreationDate>
<recordChangeDate encoding="iso8601">20200707081321.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20200022701</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>