<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <nonSort>A </nonSort>
    <title>Leader's Guide to Cybersecurity</title>
    <subTitle>WHY BOARDS NEED TO LEAD - AND HOW TO DO IT</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Parenty, Thomas J.</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
    <role>
      <roleTerm type="text">author</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Domet, Jack J.</namePart>
    <role>
      <roleTerm type="text">author. </roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">enk</placeTerm>
    </place>
    <dateIssued encoding="marc">2020</dateIssued>
    <copyrightDate encoding="marc">2020</copyrightDate>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>viii, 218 pages ; 25 cm. </extent>
  </physicalDescription>
  <abstract>  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. </abstract>
  <tableOfContents>Introduction. Digital stewardship</tableOfContents>
  <tableOfContents>Part 1. The problems. Misleading platitudes ; Hidden dynamics ;
      Misguided voices</tableOfContents>
  <tableOfContents>Part 2. The principles. If you don't understand it, they didn't explain it ; It is the business at risk ; Make cybersecurity mainstream ; Engage motivation </tableOfContents>
  <tableOfContents>Part 4. The aides. Aide mémoire: manage cyber risks ;
        Aide mémoire: fortify the company ; Aide mémoire: lead in crisis. </tableOfContents>
  <tableOfContents>Part 3. The foundation. Manage cyber risks ; Fortify the company ; Lead in crisis 
      </tableOfContents>
  <targetAudience authority="marctarget">general</targetAudience>
  <note type="statement of responsibility">Thomas J. Parenty | Jack J. Domet.</note>
  <note>Includes bibliographical references (pages 199-209) and index. </note>
  <subject authority="lcsh">
    <topic>Computer security</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Boards of directors</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Organizational behavior</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Business planning</topic>
  </subject>
  <classification authority="ddc" edition="23">005.8</classification>
  <identifier type="isbn">9781633697997</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">PPAK</recordContentSource>
    <recordCreationDate encoding="marc">210218</recordCreationDate>
    <recordChangeDate encoding="iso8601">20211118174751.0</recordChangeDate>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
