Cybersecurity signals : connecting controls and incident outcomes

<?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>00000cam a22000004  4500</leader>
    <controlfield tag="001">MAP20250012318</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20250903093143.0</controlfield>
    <controlfield tag="008">250902s2025    usa||||       ||| ||eng 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">861</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Cybersecurity signals</subfield>
      <subfield code="b">: connecting controls and incident outcomes</subfield>
      <subfield code="c">The Cyber Risk Intelligence Center (CRIC)</subfield>
    </datafield>
    <datafield tag="260" ind1=" " ind2=" ">
      <subfield code="a">New York </subfield>
      <subfield code="b">Marsh McLennan </subfield>
      <subfield code="c">2025</subfield>
    </datafield>
    <datafield tag="300" ind1=" " ind2=" ">
      <subfield code="a">17 p.</subfield>
    </datafield>
    <datafield tag="505" ind1="0" ind2=" ">
      <subfield code="a">Looking back: 2023 top controls -- 2025 top controls -- Control deep dives -- Conclusion</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">There is no shortage of controls to implement in cybersecurity. But which ones should be prioritized? Cybersecurity leaders need objective, evidence-driven metrics to help them inform and justify cybersecurity investments. In this study, we address the question of what cybersecurity measures make the biggest impact on risk, and further the conversation about control evaluation within the cybersecurity community</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20140022700</subfield>
      <subfield code="a">Ciberseguridad</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080588953</subfield>
      <subfield code="a">Análisis de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080543556</subfield>
      <subfield code="a">Control</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080601522</subfield>
      <subfield code="a">Evaluación de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080571009</subfield>
      <subfield code="a">Vulnerabilidad</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20210011863</subfield>
      <subfield code="a">Resultados</subfield>
    </datafield>
    <datafield tag="710" ind1="2" ind2=" ">
      <subfield code="0">MAPA20080449025</subfield>
      <subfield code="a">Marsh & McLennan Companies</subfield>
    </datafield>
  </record>
</collection>