<?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 AT&amp;amp;T confirms data breach and resets millions of customer passcodes in Threats</title>
    <link>https://community.isc2.org/t5/Threats/AT-amp-T-confirms-data-breach-and-resets-millions-of-customer/m-p/68894#M1154</link>
    <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whether they are big or small they all fall victim, to attacks, how they cope depends on the maturity of their incident response plans.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.theverge.com/2024/3/30/24116515/att-data-leak-passcode-reset-cybersecurity-privacy" target="_blank"&gt;https://www.theverge.com/2024/3/30/24116515/att-data-leak-passcode-reset-cybersecurity-privacy&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>Sun, 31 Mar 2024 01:06:04 GMT</pubDate>
    <dc:creator>Caute_cautim</dc:creator>
    <dc:date>2024-03-31T01:06:04Z</dc:date>
    <item>
      <title>AT&amp;T confirms data breach and resets millions of customer passcodes</title>
      <link>https://community.isc2.org/t5/Threats/AT-amp-T-confirms-data-breach-and-resets-millions-of-customer/m-p/68894#M1154</link>
      <description>&lt;P&gt;Hi All&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Whether they are big or small they all fall victim, to attacks, how they cope depends on the maturity of their incident response plans.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.theverge.com/2024/3/30/24116515/att-data-leak-passcode-reset-cybersecurity-privacy" target="_blank"&gt;https://www.theverge.com/2024/3/30/24116515/att-data-leak-passcode-reset-cybersecurity-privacy&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>Sun, 31 Mar 2024 01:06:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/AT-amp-T-confirms-data-breach-and-resets-millions-of-customer/m-p/68894#M1154</guid>
      <dc:creator>Caute_cautim</dc:creator>
      <dc:date>2024-03-31T01:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: AT&amp;T confirms data breach and resets millions of customer passcodes</title>
      <link>https://community.isc2.org/t5/Threats/AT-amp-T-confirms-data-breach-and-resets-millions-of-customer/m-p/68945#M1155</link>
      <description>&lt;P&gt;I like Verizon's method of sending a random passcode via email with a 'yes' or 'no' option on if it's okay for the rep to access your account. While it's not perfect, it's leaps and bounds over storing a customer's passcode that they are more than likely using for other accounts requiring a pin or passcode. Also, most passcodes I've been forced to use are at least 6 digits now. Seems a little behind the times there as well.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2024 12:43:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/AT-amp-T-confirms-data-breach-and-resets-millions-of-customer/m-p/68945#M1155</guid>
      <dc:creator>tmekelburg1</dc:creator>
      <dc:date>2024-04-01T12:43:36Z</dc:date>
    </item>
  </channel>
</rss>

