<?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 Twitter's Whistleblower in Industry News</title>
    <link>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52678#M5901</link>
    <description>&lt;P&gt;What are your thoughts on this? Is this just a disgruntled employee who couldn't make the case for better security or was it gross negligence on Twitter's part? I've always worked in a regulated environment so I have zero experience working for a tech company.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are some pretty serious security allegations being reported such as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Broad access to the production environment and user data&lt;/LI&gt;&lt;LI&gt;Minimal to no logging on changes to the production environment&lt;/LI&gt;&lt;LI&gt;Access to resources from unpatched work and BYOD devices&lt;/LI&gt;&lt;LI&gt;Datacenters didn't support data at rest (In their defense, not a lot of places have that setup)&lt;/LI&gt;&lt;LI&gt;Engineers tested on production environment instead of test environment&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;A href="https://www.wired.com/story/mudge-twitter-whistleblower-security/" target="_blank" rel="noopener"&gt;https://www.wired.com/story/mudge-twitter-whistleblower-security/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://s3.documentcloud.org/documents/22186782/whistleblower_disclosure.pdf" target="_blank" rel="noopener"&gt;https://s3.documentcloud.org/documents/22186782/whistleblower_disclosure.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 25 Aug 2022 14:47:51 GMT</pubDate>
    <dc:creator>tmekelburg1</dc:creator>
    <dc:date>2022-08-25T14:47:51Z</dc:date>
    <item>
      <title>Twitter's Whistleblower</title>
      <link>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52678#M5901</link>
      <description>&lt;P&gt;What are your thoughts on this? Is this just a disgruntled employee who couldn't make the case for better security or was it gross negligence on Twitter's part? I've always worked in a regulated environment so I have zero experience working for a tech company.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are some pretty serious security allegations being reported such as:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Broad access to the production environment and user data&lt;/LI&gt;&lt;LI&gt;Minimal to no logging on changes to the production environment&lt;/LI&gt;&lt;LI&gt;Access to resources from unpatched work and BYOD devices&lt;/LI&gt;&lt;LI&gt;Datacenters didn't support data at rest (In their defense, not a lot of places have that setup)&lt;/LI&gt;&lt;LI&gt;Engineers tested on production environment instead of test environment&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;A href="https://www.wired.com/story/mudge-twitter-whistleblower-security/" target="_blank" rel="noopener"&gt;https://www.wired.com/story/mudge-twitter-whistleblower-security/&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://s3.documentcloud.org/documents/22186782/whistleblower_disclosure.pdf" target="_blank" rel="noopener"&gt;https://s3.documentcloud.org/documents/22186782/whistleblower_disclosure.pdf&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 14:47:51 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52678#M5901</guid>
      <dc:creator>tmekelburg1</dc:creator>
      <dc:date>2022-08-25T14:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Twitter's Whistleblower</title>
      <link>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52679#M5902</link>
      <description>&lt;P&gt;Y'all remember the breach of those 100+ high-profile accounts?&amp;nbsp; I heard that was because they shared priv credentials in a slack-type environment.&amp;nbsp; The whole of these complaints, writ large, points to a culture of severe sloppiness.&amp;nbsp; I envision their offices all looking like Wayne Knight's workstation in Jurassic Park.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 16:26:40 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52679#M5902</guid>
      <dc:creator>ericgeater</dc:creator>
      <dc:date>2022-08-25T16:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: Twitter's Whistleblower</title>
      <link>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52681#M5903</link>
      <description>&lt;P&gt;The Twitter security team asking the Engineers not to test in the production environment:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="tmekelburg1_0-1661448160071.png" style="width: 400px;"&gt;&lt;img src="https://community.isc2.org/t5/image/serverpage/image-id/6357i417F229272AB33F1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="tmekelburg1_0-1661448160071.png" alt="tmekelburg1_0-1661448160071.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 25 Aug 2022 17:23:31 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Industry-News/Twitter-s-Whistleblower/m-p/52681#M5903</guid>
      <dc:creator>tmekelburg1</dc:creator>
      <dc:date>2022-08-25T17:23:31Z</dc:date>
    </item>
  </channel>
</rss>

