Update: CrowdStrike Incident Summary and Recommended Actions
On July 18, 2024, CrowdStrike deployed an update to CrowdStrike Falcon, triggering outages across a large number of Windows computers globally. This was not a cyber incident. While only customers of CrowdStrike have been directly affected by this outage, it’s had a widespread impact on global infrastructure and operations.
Secureworks is up and running: We can confirm that we have not been impacted by this event and our systems continue to operate as normal.
If you have been impacted by this outage, we are committed to ensuring your data and operations remain secure while you focus on CrowdStrike’s recommended recovery. As you concentrate on your business operations, we are committed to ensuring your data and those operations remain secure, including 24/7 threat detection, investigation, and response for our Taegis™ ManagedXDR customers, rapid response for all customers, and continued open support of our Taegis XDR Platform. Our commitment to protecting your business remains unwavering, and we are here to support you every step of the way, including thoughtful decisions about how to build cyber resiliency in your security strategy.
If you have not been directly impacted by this outage, we recommend that you coordinate with your critical business vendors to determine any potential 3rd party impact.
Lastly, threat actors often exploit chaotic situations to launch phishing campaigns, preying on the confusion and urgency that arise during such times. While we ensure your data and operations remain secure, we also recommend you educate your teams on the heightened risks of CrowdStrike-related phishing attacks and other forms of social engineering during this time.
We will keep continue to keep you informed on our Taegis XDR Status Update Page with regular updates on the status of this event, ensuring transparency and peace of mind.
Thank you for placing your trust in Secureworks.
Posted Jul 19, 2024 - 17:06 EDT
Monitoring
Crowdstrike is rolling out a fix. Taegis was not directly affected.