<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>koolba</author><text>&amp;gt; Those sources said the breach appears to have started when the attackers somehow gained access to the company’s Gitlab code repository, and in that repository was a token or credential that gave the bad guys access to Sisense’s Amazon S3 buckets in the cloud.&lt;p&gt;So plaintext AWS credentials checked into source control.&lt;p&gt;&amp;gt; Both sources said the attackers used the S3 access to copy and exfiltrate several terabytes worth of Sisense customer data, which apparently included millions of access tokens, email account passwords, and even SSL certificates.&lt;p&gt;And those credentials can access tons of other credentials, also stored in plaintext.&lt;p&gt;Even if the security policies didn’t pick this up, didn’t they at least having billing alerts for the terabytes of AWS bandwidth?</text><parent_chain></parent_chain></comment><story><title>Why CISA Is Warning CISOs About a Breach at Sisense</title><url>https://krebsonsecurity.com/2024/04/why-cisa-is-warning-cisos-about-a-breach-at-sisense/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dboreham</author><text>This sounds nuts. Are people still entrusting bearer tokens to third parties? I haven&amp;#x27;t seen that done in at least 10 years. Surely it&amp;#x27;s prohibited by the ToS of the first party providers?</text><parent_chain></parent_chain></comment><story><title>Why CISA Is Warning CISOs About a Breach at Sisense</title><url>https://krebsonsecurity.com/2024/04/why-cisa-is-warning-cisos-about-a-breach-at-sisense/</url></story>