<?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>01786nab a22002657a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">55921</subfield>
    <subfield code="d">55921</subfield>
  </datafield>
  <controlfield tag="001">55921</controlfield>
  <controlfield tag="003">CL-SaANEPE</controlfield>
  <controlfield tag="005">20211029005927.0</controlfield>
  <controlfield tag="006">a||||| |||| 00| 0 </controlfield>
  <controlfield tag="008">160316t2015    xx ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">CL-SaANEPE</subfield>
    <subfield code="c">CL-SaANEPE</subfield>
    <subfield code="d">CL-SaANEPE</subfield>
  </datafield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">US.SS/4/2015</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Geist, Edward</subfield>
    <subfield code="9">49112</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Deterrence stability in the cyber age</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">9, 4 (winter 2015)  : 44-61</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Technical and operational realities make it prohibitively difficult to adapt a Cold War paradigm of "deterrence stability" to the new domain of cyber warfare. Information quality problems are likely to forestall the development of a cyber equivalent of the strategic exchange models that assessed deterrence stability during the Cold War. Since cyberspace is not firmly connected to geographic space the way other domains are, it makes modeling extremely difficult as well as muddles neat conceptual distinctions between "counterforce" (military) and "countervalue" (civilian) targets. These obstacles seriously complicate U.S. planning for a credible cyber "assured response," and also present substantial challenges to potential adversaries contemplating cyber attacks against U.S. interests. To create a maximally effective deterrent against cyber threats, the United States should seek to maximize the challenges for possible opponents by creating a cyber "strategy of technology" emphasizing resilience, denial, and offensive capabilities.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="7">
    <subfield code="a">GUERRA CIBERNETICA</subfield>
    <subfield code="9">35042</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="7">
    <subfield code="a">DISUASION</subfield>
    <subfield code="9">32240</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="7">
    <subfield code="a">ERA DE LA INFORMACION</subfield>
    <subfield code="9">32989</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="7">
    <subfield code="a">CIBERESPACIO</subfield>
    <subfield code="9">28871</subfield>
  </datafield>
  <datafield tag="651" ind1=" " ind2="7">
    <subfield code="9">46215</subfield>
    <subfield code="a">ESTADOS UNIDOS</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Strategic Studies Quarterly.</subfield>
    <subfield code="w">020904</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">REVA</subfield>
    <subfield code="2">ddc</subfield>
  </datafield>
  <datafield tag="945" ind1=" " ind2=" ">
    <subfield code="a">OSS20191022</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">BC</subfield>
    <subfield code="b">BC</subfield>
    <subfield code="d">2019-10-22</subfield>
    <subfield code="o">US.SS/4/2015</subfield>
    <subfield code="r">2019-10-22</subfield>
    <subfield code="w">2019-10-22</subfield>
    <subfield code="y">REVA</subfield>
  </datafield>
</record>
