Secureworks Outage History

Secureworks experienced a delay in Entra sign-in event ingestion that lasted 17.3 hours. The issue affected the timely processing of authentication events within the security platform. The team implemented a fix and monitored the results before confirming full resolution.

Secureworks experienced a delay in alert triaging within their Echo system that lasted 55 minutes. The issue affected the normal processing and review of security alerts. The problem was identified and resolved through a deployed solution, with alert triage returning to normal operations.

Secureworks experienced a workflow error that caused delays in case escalations for 1.9 hours. The incident affected the case handling system's ability to properly escalate cases through normal processes. The issue was resolved by manually re-escalating the impacted cases.

Secureworks experienced delays in alert and detection triage within their Echo system for approximately 2.8 hours. The incident affected the timely processing of security alerts and detections. The issue was resolved after investigation and remediation efforts.

Secureworks experienced a delay in processing a subset of alerts in their Charlie system for 3.2 hours. The incident affected alert processing functionality, causing delays in security alert handling. The issue was actively investigated and subsequently resolved.

Secureworks experienced a 1.1-hour incident where users were unable to attach alerts to cases (investigations) across all environments. Engineers identified the root cause and deployed a fix to restore the alert attachment functionality. Alerting continued to work normally throughout the incident with no risk of data loss.

Secureworks experienced an automation system backlog that caused an increase in notifications as automated jobs caught up on processing. The incident affected users through a higher than normal volume of notifications from the automation system. The issue was resolved after 7.9 hours once the backlog was cleared and the automation system returned to normal operation.

Users experienced login issues with the Secureworks Taegis Platform for 38 minutes. A workaround was provided to use incognito/private browsing mode to access the platform. The incident was resolved without requiring permanent changes to user login procedures.

Secureworks experienced an issue where playbook automations failed to run for some customers, affecting their automated security response workflows. The incident was classified as minor and lasted approximately 3.6 hours before being resolved. The service team investigated and restored normal automation functionality.

Secureworks experienced a 27.5-hour incident where Zendesk ticket creation from @secureworks comments was failing, causing delayed customer service responses to user inquiries. The issue also affected ticket assignment functionality through the "Assignee" field. The problem was resolved after implementing a fix and monitoring the results.