<?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: Threat Actors Can Leverage AWS STS to Infiltrate Cloud Accounts in Cloud Security</title>
    <link>https://community.isc2.org/t5/Cloud-Security/Threat-Actors-Can-Leverage-AWS-STS-to-Infiltrate-Cloud-Accounts/m-p/65209#M380</link>
    <description>Well, we do have service providers and identity providers separated for some reason in all the pretty architecture pictures… &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Though in fairness to Amazon this looks like you have to audit account use, have proper procedures and watch for the little credential squirrels wheresoever they may be.</description>
    <pubDate>Fri, 08 Dec 2023 09:20:11 GMT</pubDate>
    <dc:creator>Early_Adopter</dc:creator>
    <dc:date>2023-12-08T09:20:11Z</dc:date>
    <item>
      <title>Threat Actors Can Leverage AWS STS to Infiltrate Cloud Accounts</title>
      <link>https://community.isc2.org/t5/Cloud-Security/Threat-Actors-Can-Leverage-AWS-STS-to-Infiltrate-Cloud-Accounts/m-p/65200#M378</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It appears that AWS Security Token Service (STS) has issues, so read this explanation and take action:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://thehackernews.com/2023/12/alert-threat-actors-can-leverage-aws.html" target="_blank" rel="noopener"&gt;https://thehackernews.com/2023/12/alert-threat-actors-can-leverage-aws.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Caute_Cautim&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 19:54:49 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Cloud-Security/Threat-Actors-Can-Leverage-AWS-STS-to-Infiltrate-Cloud-Accounts/m-p/65200#M378</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2023-12-07T19:54:49Z</dc:date>
    </item>
    <item>
      <title>Re: Threat Actors Can Leverage AWS STS to Infiltrate Cloud Accounts</title>
      <link>https://community.isc2.org/t5/Cloud-Security/Threat-Actors-Can-Leverage-AWS-STS-to-Infiltrate-Cloud-Accounts/m-p/65209#M380</link>
      <description>Well, we do have service providers and identity providers separated for some reason in all the pretty architecture pictures… &lt;span class="lia-unicode-emoji" title=":face_with_tongue:"&gt;😛&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;Though in fairness to Amazon this looks like you have to audit account use, have proper procedures and watch for the little credential squirrels wheresoever they may be.</description>
      <pubDate>Fri, 08 Dec 2023 09:20:11 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Cloud-Security/Threat-Actors-Can-Leverage-AWS-STS-to-Infiltrate-Cloud-Accounts/m-p/65209#M380</guid>
      <dc:creator>Early_Adopter</dc:creator>
      <dc:date>2023-12-08T09:20:11Z</dc:date>
    </item>
  </channel>
</rss>

