Infection Monkey vs Stratus Red Team

Infection Monkey is an open-source breach and attack simulation tool for checking data center resilience to perimeter breaches and internal server infection. Monkey Agent scans systems and simulates attack techniques, while Monkey Island Server provides a command-and-control web interface. The tool maps visible machines, accessible services, and possible routes through a network, then reports security issues the agents discover or exploit. It supports on-premises environments, containers, and public and private clouds. The documented AWS integration uses Systems Manager to run Infection Monkey on EC2 instances, and plugins can be installed, updated, removed, or uploaded through the Monkey Island interface. Internet access is not required; when available, it is used to check for updates and whether machines can reach the internet. The FAQ says sensitive data is encrypted in the Island database and sent to agents over HTTPS, and that first launch requires creating credentials for access to the server. It also says the tool avoids exploits or attacks that may affect target systems, including EternalBlue. The Free plan is free.

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.