4 Key cyberrisk management questions for directors and officers

<?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>4 Key cyberrisk management questions for directors and officers</title>
</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">Courts have historically made it difficult to hold directors and officers personally liable for breaches of fiduciary duties. But as cyberrisk management liability standards evolve, directors and officers increasingly face the risk of personal exposure.</abstract>
<note type="statement of responsibility">Richik Sarkar</note>
<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="MAPA20160007633">
<topic>Ciberriesgos</topic>
</subject>
<subject xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="MAPA20080605742">
<topic>Directivos de empresas</topic>
</subject>
<classification authority="">7</classification>
<relatedItem type="host">
<titleInfo>
<title>Risk Management Magazine</title>
</titleInfo>
<originInfo>
<publisher>New York : Risk and Insurance Management Society, 1982-</publisher>
</originInfo>
<identifier type="issn">0035-5593</identifier>
<identifier type="local">MAP20077000291</identifier>
<part>
<text>04/09/2017 Volumen 64 Número 8 - septiembre 2017 , p. 31-34</text>
</part>
</relatedItem>
<recordInfo>
<recordContentSource authority="marcorg">MAP</recordContentSource>
<recordCreationDate encoding="marc">170925</recordCreationDate>
<recordChangeDate encoding="iso8601">20171005132556.0</recordChangeDate>
<recordIdentifier source="MAP">MAP20170031123</recordIdentifier>
<languageOfCataloging>
<languageTerm type="code" authority="iso639-2b">spa</languageTerm>
</languageOfCataloging>
</recordInfo>
</mods>
</modsCollection>