<story><title>CircleCI security alert: Rotate any secrets stored in CircleCI</title><url>https://circleci.com/blog/january-4-2023-security-alert/</url></story><parent_chain></parent_chain><comment><author>bamboozled</author><text>&lt;i&gt;&amp;gt; We wanted to make you aware that we are currently investigating a security incident, and that our investigation is ongoing. We will provide you updates about this incident, and our response, as they become available. At this point, we are confident that there are no unauthorized actors active in our systems; however, out of an abundance of caution, we want to ensure that all customers take certain preventative measures to protect your data as well.&lt;/i&gt;&lt;p&gt;Is anyone else a little annoyed by the messaging here, I read it as, &amp;quot;We think something bad happened to your ultra secret data, but we don&amp;#x27;t know, so we&amp;#x27;re asking teams to spend potentially hours or days fixing things while we aren&amp;#x27;t really able to tell you if your stuff was actually compromised&amp;quot;?&lt;p&gt;What I find more troubling is, if they don&amp;#x27;t quite know what happened, or aren&amp;#x27;t telling us, and we do the work to change everything, how do they know it won&amp;#x27;t just happen again in the next day or so and people are still accessing our systems, where is the details?&lt;p&gt;&lt;i&gt;&amp;gt; At this point, we are confident that there are no unauthorized actors active in our systems.&lt;/i&gt;&lt;p&gt;Confident isn&amp;#x27;t really a good enough word to use here in my opinion. We&amp;#x27;ve just blocked Circle CI from all our systems for now until we hear more, likely start to move to another build system.&lt;p&gt;I know accidents happen but this is likely the beginning of the end for our teams relationship with Circle CI. Trust has been broken.</text></comment>
<story><title>CircleCI security alert: Rotate any secrets stored in CircleCI</title><url>https://circleci.com/blog/january-4-2023-security-alert/</url></story><parent_chain></parent_chain><comment><author>sickmate</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;sanitybit&amp;#x2F;status&amp;#x2F;1610829345676996609&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;twitter.com&amp;#x2F;sanitybit&amp;#x2F;status&amp;#x2F;1610829345676996609&lt;/a&gt;&lt;p&gt;&amp;gt;I&amp;#x27;ve been investigating the use of a @ThinkstCanary AWS token that was improperly accessed on December 27th and suspected as much.</text></comment>