<?xml version="1.0" encoding="UTF-8"?>
<record
    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"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02894nam a2200373 i 4500</leader>
  <controlfield tag="003">OSt</controlfield>
  <controlfield tag="005">20211118174751.0</controlfield>
  <controlfield tag="008">210218t20202020enk    gr     001 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9781633697997</subfield>
    <subfield code="c">RM 152.25</subfield>
    <subfield code="q">hardback</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">PPAK</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">PPAK</subfield>
    <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2="4">
    <subfield code="2">23</subfield>
    <subfield code="a">005.8</subfield>
  </datafield>
  <datafield tag="090" ind1="0" ind2="0">
    <subfield code="a">005.8</subfield>
    <subfield code="b">PAR</subfield>
    <subfield code="d">G</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Parenty, Thomas J.,</subfield>
    <subfield code="e">author</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="2">
    <subfield code="a">A Leader's Guide to Cybersecurity :</subfield>
    <subfield code="b">WHY BOARDS NEED TO LEAD - AND HOW TO DO IT / </subfield>
    <subfield code="c">Thomas J. Parenty | Jack J. Domet.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">Boston, MA :</subfield>
    <subfield code="b">Harvard Business Review Press,</subfield>
    <subfield code="c">2020</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="4">
    <subfield code="c">&#xA9;2020. </subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">viii, 218 pages ;</subfield>
    <subfield code="c">25 cm. </subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="a">text</subfield>
    <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="a">unmediated</subfield>
    <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="a">volume</subfield>
    <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references (pages 199-209) and index. </subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="g">Introduction.</subfield>
    <subfield code="t">Digital stewardship</subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="g">Part 1.</subfield>
    <subfield code="t">The problems.</subfield>
    <subfield code="t">Misleading platitudes ;</subfield>
    <subfield code="t">Hidden dynamics ;
     </subfield>
    <subfield code="t">Misguided voices</subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="g">Part 2.</subfield>
    <subfield code="t">The principles.</subfield>
    <subfield code="t">If you don't understand it, they didn't explain it ;</subfield>
    <subfield code="t">It is the business at risk ;</subfield>
    <subfield code="t">Make cybersecurity mainstream ;</subfield>
    <subfield code="t">Engage motivation </subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="g">Part 4.</subfield>
    <subfield code="t">The aides.</subfield>
    <subfield code="t">Aide m&#xE9;moire: manage cyber risks ;
       </subfield>
    <subfield code="t">Aide m&#xE9;moire: fortify the company ;</subfield>
    <subfield code="t">Aide m&#xE9;moire: lead in crisis. </subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="g">Part 3.</subfield>
    <subfield code="t">The foundation.</subfield>
    <subfield code="t">Manage cyber risks ;</subfield>
    <subfield code="t">Fortify the company ;</subfield>
    <subfield code="t">Lead in crisis 
      </subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">  Companies are investing an unprecedented amount of money 
       to keep their data and assets safe, yet cyberattacks are 
       on the rise -- and the problem is worsening. No amount of 
       technology, resources, or policies will reverse this 
       trend. Only sound governance, originating with the board, 
       can turn the tide. Protection against cyberattacks can't 
       be treated as a problem solely belonging to an IT or 
       cybersecurity department. It needs to cast a wide and 
       impenetrable net that covers everything an organization 
       does -- from its business operations, models, and 
       strategies to its products and intellectual property. And 
       boards are in the best position to oversee the needed 
       changes to strategy and hold their companies accountable. 
       Not surprisingly, many boards aren't prepared to assume 
       this responsibility. In A Leader's Guide to Cybersecurity,
       Thomas Parenty and Jack Domet, who've spent over three 
       decades in the field, present a timely, clear-eyed, and 
       actionable framework that will empower senior executives 
       and board members to become stewards of their companies' 
       cybersecurity activities. </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Computer security. </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Boards of directors. </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Organizational behavior.  </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Business planning.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
    <subfield code="a">Domet, Jack J.,</subfield>
    <subfield code="e">author. </subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">B</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">182144</subfield>
    <subfield code="d">182144</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="b">PPAK</subfield>
    <subfield code="c">G</subfield>
    <subfield code="d">2021-04-14</subfield>
    <subfield code="l">1</subfield>
    <subfield code="o">005.8 PAR</subfield>
    <subfield code="p">A01683427</subfield>
    <subfield code="r">2022-09-10 00:00:00</subfield>
    <subfield code="s">2022-08-21</subfield>
    <subfield code="y">B</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="b">SP</subfield>
    <subfield code="c">G</subfield>
    <subfield code="d">2021-04-14</subfield>
    <subfield code="l">1</subfield>
    <subfield code="m">1</subfield>
    <subfield code="o">005.8 PAR</subfield>
    <subfield code="p">A01683428</subfield>
    <subfield code="r">2022-05-24 00:00:00</subfield>
    <subfield code="s">2022-04-12</subfield>
    <subfield code="y">B</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="b">KM</subfield>
    <subfield code="c">G</subfield>
    <subfield code="d">2021-04-14</subfield>
    <subfield code="o">005.8 PAR</subfield>
    <subfield code="p">A01683429</subfield>
    <subfield code="r">2021-04-14 00:00:00</subfield>
    <subfield code="y">B</subfield>
  </datafield>
</record>
