Search

Perceptions of randomized security schedules

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" 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">
  <record>
    <leader>00000cab a2200000   4500</leader>
    <controlfield tag="001">MAP20140018192</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20140530130427.0</controlfield>
    <controlfield tag="008">140523e20140407esp|||p      |0|||b|spa d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
      <subfield code="d">MAP</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">7</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20140009299</subfield>
      <subfield code="a">Scurich, Nicholas</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Perceptions of randomized security schedules</subfield>
      <subfield code="c">Nicholas Scurich, Richard S. John</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">Security of infrastructure is a major concern. Traditional security schedules are unable to provide omnipresent coverage; consequently, adversaries can exploit predictable vulnerabilities to their advantage. Randomized security schedules, which randomly deploy security measures, overcome these limitations, but public perceptions of such schedules have not been examined. In this experiment, participants were asked to make a choice between attending a venue that employed a traditional (i.e., search everyone) or a random (i.e., a probability of being searched) security schedule. The absolute probability of detecting contraband was manipulated (i.e., 1/10, 1/4, 1/2) but equivalent between the two schedule types. In general, participants were indifferent to either security schedule, regardless of the probability of detection. The randomized schedule was deemed more convenient, but the traditional schedule was considered fairer and safer. There were no differences between traditional and random schedule in terms of perceived effectiveness or deterrence. Policy implications for the implementation and utilization of randomized schedules are discussed.</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="w">MAP20077000345</subfield>
      <subfield code="t">Risk analysis : an international journal</subfield>
      <subfield code="d">McLean, Virginia : Society for Risk Analysis, 1987-2015</subfield>
      <subfield code="x">0272-4332</subfield>
      <subfield code="g">07/04/2014 Volumen 34 Número 4 - abril 2014 </subfield>
    </datafield>
    <datafield tag="856" ind1=" " ind2=" ">
      <subfield code="y">MÁS INFORMACIÓN</subfield>
      <subfield code="u">mailto:centrodocumentacion@fundacionmapfre.org?subject=Consulta%20de%20una%20publicaci%C3%B3n%20&body=Necesito%20m%C3%A1s%20informaci%C3%B3n%20sobre%20este%20documento%3A%20%0A%0A%5Banote%20aqu%C3%AD%20el%20titulo%20completo%20del%20documento%20del%20que%20desea%20informaci%C3%B3n%20y%20nos%20pondremos%20en%20contacto%20con%20usted%5D%20%0A%0AGracias%20%0A</subfield>
    </datafield>
  </record>
</collection>