SCYTHE vs Stratus Red Team

SCYTHE is a continuous Adversarial Exposure Validation platform for enterprise security teams. It runs MITRE ATT&CK-mapped adversary campaigns, including multi-stage campaigns based on named threat actors, to check whether controls detect, alert, block and respond. Results map to ATT&CK coverage and identified gaps. AI can generate campaigns from plain-language threat descriptions, but execution requires human approval. Deployment options include cloud SaaS, on-premises, hybrid and air-gapped environments. Listed integrations include CrowdStrike Falcon, Microsoft Defender, SentinelOne, Cortex XDR, Splunk, Microsoft Sentinel, IBM QRadar, Google Chronicle, Elastic SIEM, ServiceNow and Jira. SCYTHE says it connects bidirectionally with SIEM, SOAR, EDR, ticketing systems and security controls. Its tests are described as controlled, configurable, logged and auditable; destructive capabilities require explicit authorization. Included attack surfaces are Windows, macOS, Linux, cloud and OT/ICS. The company identifies itself as SOC 2 Type II certified and describes an annual independent security audit. Pricing is custom-quoted based on environment scope, and there is no free plan, though a free trial is available. Managed validation is also offered.

Stratus Red Team is a free, open-source Go binary for running specific offensive attack techniques against a live cloud environment and checking detections. Its techniques map to MITRE ATT&CK, with coverage for AWS, Azure, GCP, Kubernetes, Amazon EKS, and Entra ID. For each technique, it can prepare prerequisites, detonate the activity, reverse side effects, and remove prerequisites. Terraform creates and removes required infrastructure, and Stratus downloads its own Terraform binary. Installation options include Go, Homebrew, pre-built Linux, Windows, and macOS binaries, and Docker. The tool can also operate as a Go library for automation and custom techniques. It supports Linux, macOS, Windows, API use, and self-hosting. Documentation recommends an administrator role in a sandbox account or test cluster, not production infrastructure. Kubernetes clusters must already exist, AWS customer-provided detonation infrastructure is unsupported, and Azure resources are fixed to West US.