Common regulatory issues facing third-party risk management

<?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 a22000004b 4500</leader>
    <controlfield tag="001">MAP20210031717</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20211104173243.0</controlfield>
    <controlfield tag="008">211103s2021    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">7</subfield>
    </datafield>
    <datafield tag="245" ind1="1" ind2="0">
      <subfield code="a">Common regulatory issues facing third-party risk management</subfield>
    </datafield>
    <datafield tag="260" ind1=" " ind2=" ">
      <subfield code="a">Concord, Massachusett</subfield>
      <subfield code="b">ProcessUnity</subfield>
      <subfield code="c">2021</subfield>
    </datafield>
    <datafield tag="300" ind1=" " ind2=" ">
      <subfield code="a">10 p.</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">Of course, the statement above was tongue and cheek, but far too often organizations find themselves figuring out the truth of this statement the hard way in their attempts to meet regulatory requirements. Organizations today are facing a vast and evolving regulatory landscape that makes staying on top of compliance incredibly challenging no matter what industry you are in.  Keeping track of the depth of requirements an organization faces can be a daunting task considering the growth in business complexity over the years. Business boundaries today are increasingly vague because today's extended enterprise is comprised of a web of third-party relationships, unlike the traditional brick and mortar business model of the past. The organization now needs to consider the extended enterprise when building its risk and compliance programs</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080591182</subfield>
      <subfield code="a">Gerencia de riesgos</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20140006335</subfield>
      <subfield code="a">Compliance</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20100019443</subfield>
      <subfield code="a">Requerimientos financieros</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20110024864</subfield>
      <subfield code="a">Modelos de negocio</subfield>
    </datafield>
    <datafield tag="710" ind1="2" ind2=" ">
      <subfield code="0">MAPA20180002069</subfield>
      <subfield code="a">ProcessUnity</subfield>
    </datafield>
  </record>
</collection>