<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ISO 27001 controls re: engineering data bridges set up between companies in Governance, Risk, Compliance</title>
    <link>https://community.isc2.org/t5/Governance-Risk-Compliance/ISO-27001-controls-re-engineering-data-bridges-set-up-between/m-p/45700#M389</link>
    <description>&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/985787817"&gt;@Midude2000&lt;/a&gt; - without knowing the specifics of your situation and the scope&lt;BR /&gt;of your ISMS, it would be difficult to offer more, but given the example&lt;BR /&gt;you gave about data exchange, here are some things that might come into&lt;BR /&gt;play from an ISO 27001 perspective:&lt;BR /&gt;&lt;BR /&gt;- *Information Classification Policy*: this would typically outline the&lt;BR /&gt;various classifications you have in place for your data. In this case,&lt;BR /&gt;company B (the ISO 27001-certified company) would normally have specific&lt;BR /&gt;classification levels in place to distinguish the different types of data&lt;BR /&gt;and how to protect each group. This would be important to consider in the&lt;BR /&gt;exchange of data, because company B would need to ensure that the exchange&lt;BR /&gt;process is in line with their policies around handling and protection of&lt;BR /&gt;each type of data, depending on how it's classified. Some examples of&lt;BR /&gt;classifications are "sensitive/regulated," "restricted," "confidential,"&lt;BR /&gt;and "public."&lt;BR /&gt;&lt;BR /&gt;- *Information Labeling Policy*: this would typically set forth&lt;BR /&gt;requirements around how information is labeled in order to provide a visual&lt;BR /&gt;cue/reminder to people about the sensitivity of that information. I would&lt;BR /&gt;expect company B to have this kind of policy in place.&lt;BR /&gt;&lt;BR /&gt;- *Information Transfer Policy*: this policy would typically outline&lt;BR /&gt;general requirements around how information must/mustn't be transferred&lt;BR /&gt;that apply to all information. Additionally, it would also normally include&lt;BR /&gt;specific requirements for which transfer modes (email, text, IM, phone,&lt;BR /&gt;fax, etc.) can/cannot be used for transferring different classes of data,&lt;BR /&gt;and how data must be protected depending on the mode that is being used for&lt;BR /&gt;the transfer (e.g. encryption).&lt;BR /&gt;&lt;BR /&gt;Those are just a few that come to mind, but depending on the specifics of&lt;BR /&gt;your situation, there may be a few other policies from company B's ISMS&lt;BR /&gt;that may come into play.&lt;BR /&gt;&lt;BR /&gt;Hope this is somewhat helpful.</description>
    <pubDate>Thu, 27 May 2021 00:26:05 GMT</pubDate>
    <dc:creator>joeadu</dc:creator>
    <dc:date>2021-05-27T00:26:05Z</dc:date>
    <item>
      <title>ISO 27001 controls re: engineering data bridges set up between companies</title>
      <link>https://community.isc2.org/t5/Governance-Risk-Compliance/ISO-27001-controls-re-engineering-data-bridges-set-up-between/m-p/45641#M388</link>
      <description>&lt;P&gt;Hi All:&lt;BR /&gt;Does anyone have some guidance related to ISO 27001 risks and related controls/policies which become important to consider for a company going through an acquisition process? For example, if company A is being acquired by Company B (which is ISO 27001 compliant), and Company A and B have set up 'data exchange bridges' to exchange data during the acquisition process...what controls (specific to ISO 27001) come into play? what would a audit plan/communication plan for such a control set look like?&lt;/P&gt;</description>
      <pubDate>Mon, 24 May 2021 21:52:58 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Governance-Risk-Compliance/ISO-27001-controls-re-engineering-data-bridges-set-up-between/m-p/45641#M388</guid>
      <dc:creator>Midude2000</dc:creator>
      <dc:date>2021-05-24T21:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISO 27001 controls re: engineering data bridges set up between companies</title>
      <link>https://community.isc2.org/t5/Governance-Risk-Compliance/ISO-27001-controls-re-engineering-data-bridges-set-up-between/m-p/45700#M389</link>
      <description>&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/985787817"&gt;@Midude2000&lt;/a&gt; - without knowing the specifics of your situation and the scope&lt;BR /&gt;of your ISMS, it would be difficult to offer more, but given the example&lt;BR /&gt;you gave about data exchange, here are some things that might come into&lt;BR /&gt;play from an ISO 27001 perspective:&lt;BR /&gt;&lt;BR /&gt;- *Information Classification Policy*: this would typically outline the&lt;BR /&gt;various classifications you have in place for your data. In this case,&lt;BR /&gt;company B (the ISO 27001-certified company) would normally have specific&lt;BR /&gt;classification levels in place to distinguish the different types of data&lt;BR /&gt;and how to protect each group. This would be important to consider in the&lt;BR /&gt;exchange of data, because company B would need to ensure that the exchange&lt;BR /&gt;process is in line with their policies around handling and protection of&lt;BR /&gt;each type of data, depending on how it's classified. Some examples of&lt;BR /&gt;classifications are "sensitive/regulated," "restricted," "confidential,"&lt;BR /&gt;and "public."&lt;BR /&gt;&lt;BR /&gt;- *Information Labeling Policy*: this would typically set forth&lt;BR /&gt;requirements around how information is labeled in order to provide a visual&lt;BR /&gt;cue/reminder to people about the sensitivity of that information. I would&lt;BR /&gt;expect company B to have this kind of policy in place.&lt;BR /&gt;&lt;BR /&gt;- *Information Transfer Policy*: this policy would typically outline&lt;BR /&gt;general requirements around how information must/mustn't be transferred&lt;BR /&gt;that apply to all information. Additionally, it would also normally include&lt;BR /&gt;specific requirements for which transfer modes (email, text, IM, phone,&lt;BR /&gt;fax, etc.) can/cannot be used for transferring different classes of data,&lt;BR /&gt;and how data must be protected depending on the mode that is being used for&lt;BR /&gt;the transfer (e.g. encryption).&lt;BR /&gt;&lt;BR /&gt;Those are just a few that come to mind, but depending on the specifics of&lt;BR /&gt;your situation, there may be a few other policies from company B's ISMS&lt;BR /&gt;that may come into play.&lt;BR /&gt;&lt;BR /&gt;Hope this is somewhat helpful.</description>
      <pubDate>Thu, 27 May 2021 00:26:05 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Governance-Risk-Compliance/ISO-27001-controls-re-engineering-data-bridges-set-up-between/m-p/45700#M389</guid>
      <dc:creator>joeadu</dc:creator>
      <dc:date>2021-05-27T00:26:05Z</dc:date>
    </item>
  </channel>
</rss>

