<?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 Simple effective cloud adoption and strategy for better L2 assurance work in Governance, Risk, Compliance</title>
    <link>https://community.isc2.org/t5/Governance-Risk-Compliance/Simple-effective-cloud-adoption-and-strategy-for-better-L2/m-p/47075#M461</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Hi All,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As line two looking and cloud risk, I want to know what strategy / architecture can be adopted for a customer (banking) who has so far adopted cloud in a fragmented manner with no centralized model (dump things here and there, open tenants here tenants there across AWS, Azure, Google) causing whole painful and time-consuming yet inefficient cloud / tenant reassessment for risk and security teams every time they open a tenant or introduce a cloud service, etc. With the aim to achieve simplification and consistency across cloud controls and ongoing cloud assurance and assessment. I am looking for a recommendation / strategy to rectify what is already in place and avoid ad-hoc ineffective cloud adoption as business initiatives come up. A robust model / approach to address above mentioned challenges. Please also share any article / resources for this matter.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 23 Aug 2021 11:13:36 GMT</pubDate>
    <dc:creator>rami99</dc:creator>
    <dc:date>2021-08-23T11:13:36Z</dc:date>
    <item>
      <title>Simple effective cloud adoption and strategy for better L2 assurance work</title>
      <link>https://community.isc2.org/t5/Governance-Risk-Compliance/Simple-effective-cloud-adoption-and-strategy-for-better-L2/m-p/47075#M461</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi All,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;As line two looking and cloud risk, I want to know what strategy / architecture can be adopted for a customer (banking) who has so far adopted cloud in a fragmented manner with no centralized model (dump things here and there, open tenants here tenants there across AWS, Azure, Google) causing whole painful and time-consuming yet inefficient cloud / tenant reassessment for risk and security teams every time they open a tenant or introduce a cloud service, etc. With the aim to achieve simplification and consistency across cloud controls and ongoing cloud assurance and assessment. I am looking for a recommendation / strategy to rectify what is already in place and avoid ad-hoc ineffective cloud adoption as business initiatives come up. A robust model / approach to address above mentioned challenges. Please also share any article / resources for this matter.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Thank you in advance.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Aug 2021 11:13:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Governance-Risk-Compliance/Simple-effective-cloud-adoption-and-strategy-for-better-L2/m-p/47075#M461</guid>
      <dc:creator>rami99</dc:creator>
      <dc:date>2021-08-23T11:13:36Z</dc:date>
    </item>
    <item>
      <title>Re: Simple effective cloud adoption and strategy for better L2 assurance work</title>
      <link>https://community.isc2.org/t5/Governance-Risk-Compliance/Simple-effective-cloud-adoption-and-strategy-for-better-L2/m-p/47409#M479</link>
      <description>&lt;P&gt;It is a decent methodology to pick applications that are independent and easy to relocate so the disturbance is restricted to that application and spotlight is on gaining from the cloud reception measures.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Sep 2021 09:45:58 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Governance-Risk-Compliance/Simple-effective-cloud-adoption-and-strategy-for-better-L2/m-p/47409#M479</guid>
      <dc:creator>Purdy95</dc:creator>
      <dc:date>2021-09-09T09:45:58Z</dc:date>
    </item>
  </channel>
</rss>

