Stratus Red Team
Ranked #10 of 12 for breach and attack simulation tools: Single binary that detonates cloud attack techniques to test detection rules.
Vendors can pay for more visibility on this site; the link to Stratus Red Team is marked like every other vendor link. How that works.
Visit Stratus Red Team See it in the breach and attack simulation tools ranking
Stratus Red Team at a glance
| Headquarters | Not stated by the vendor |
|---|---|
| API | Nothing recorded about an API |
| Deployment | Open source code, Cloud or hosted |
| Free plan | Yes |
| Pricing model | Free open source tool under the Apache licence |
| Best for | Cloud detection engineers validating rules on AWS, Azure, GCP or Kubernetes |
What is Stratus Red Team?
Stratus Red Team describes itself on its homepage as a self-contained binary to easily detonate offensive attack techniques against a live cloud environment. Its stated purpose is validating that threat detection rules work, and it is positioned as the cloud counterpart to Atomic Red Team. The site navigation lists about 103 technique pages: 46 for AWS, 25 for GCP, 15 for Azure, 8 for Kubernetes, 7 for Entra ID and 2 for EKS.
Techniques are mapped to MITRE ATT&CK, with coverage matrices on the site. The source repository is licensed under Apache-2.0 and sits in the Datadog GitHub organisation, where Christophe Tafani-Dereeper and Simon Marechal are named as core maintainers, and the site footer carries a Datadog copyright notice. The homepage makes no statement about pricing, a free plan or a hosted offering.
Stratus Red Team key features
- Single binary. The tool ships as one self-contained binary. That keeps installation light for an engineer who wants to run a technique against a test account without deploying a server or console.
- Cloud technique catalogue. About 103 technique pages are listed. AWS has 46, GCP 25, Azure 15, Kubernetes 8, Entra ID 7 and EKS 2, so coverage is deepest for AWS and thin for EKS.
- Command set for the technique lifecycle. Documentation pages cover list, status, show, warmup, detonate, revert and cleanup. Separating warmup from detonation and cleanup lets a team prepare infrastructure first and remove it afterwards.
- MITRE ATT&CK mapping. Attack techniques are mapped to MITRE ATT&CK, and coverage matrices are published on the site. Detection engineers can see which tactics are exercised before choosing what to detonate.
- Concurrent executions guide. A guide on concurrent executions is named in the documentation. The pages we read do not describe its contents, so check it before running several techniques at the same time.
- Detection rule validation. The stated purpose is to confirm that threat detection rules work. The tool generates the activity; judging whether an alert fired still happens in your own logging or SIEM.
- Open source under Apache-2.0. The repository datadog/stratus-red-team is licensed under Apache-2.0. Teams can read the code behind each technique, though the licence page does not describe support terms.
Who Stratus Red Team suits
- A cloud security engineer testing AWS detections. With 46 AWS techniques listed, an engineer can detonate one, check whether the expected alert fires and then revert. The pages do not state how long each technique takes.
- A detection engineering team on several clouds. Techniques exist for GCP, Azure and Entra ID as well as AWS. One binary and one command set means a team can reuse the same routine across providers.
- A Kubernetes platform team. Eight Kubernetes and two EKS techniques are listed. They give a starting point for testing cluster-level detections, though the catalogue is small compared with AWS.
Getting started with Stratus Red Team
The pages we read describe the command set rather than a step-by-step installation. Documentation names commands to list and show techniques, warm up the prerequisites, detonate, revert and clean up, which suggests a sequence: choose a technique, prepare it, run it, then undo it.
Because it runs against a live cloud environment, a dedicated test account is the sensible target. The homepage does not describe credentials, permissions or how to obtain the binary, so use the documentation and the GitHub repository for those details. A guide on concurrent executions is also listed, and should be read before running more than one technique at once.
The case for and against Stratus Red Team
- Stratus Red Team is a self-contained binary that detonates attack techniques against a live cloud environment to check detection rules, described as the cloud counterpart to Atomic Red Team.
- Marked in our records as cloud techniques.
- Single binary is among the traits we single out for it.
- Suits: Cloud detection engineers validating rules on AWS, Azure, GCP or Kubernetes.
- Apache-2.0 is among the traits we single out for it.
- Less suited to: Teams wanting endpoint, email or network coverage in one tool.
- Technique pages cover AWS, GCP, Azure, Kubernetes, Entra ID and EKS only, with no endpoint or network tests listed.
- Detonation happens in a real cloud account, which leaves risk planning with the team.
What we make of Stratus Red Team
Stratus Red Team is a self-contained binary that detonates attack techniques against a live cloud environment to check detection rules, described as the cloud counterpart to Atomic Red Team.
The site lists about 103 techniques: 46 for AWS, 25 for GCP, 15 for Azure, 8 for Kubernetes, 7 for Entra ID and 2 for EKS. Source is Apache-2.0 under the Datadog GitHub organisation, and the footer carries a Datadog copyright.
In our breach and attack simulation tools ranking Stratus Red Team stands at #10 of 12: Keysight Threat Simulator sits directly above it and Infection Monkey directly below. From place 4 the established names follow in their ranked order; we publish no numeric score.
The vendor states no country of establishment, so Stratus Red Team is left out of the regional count for this list.
Stratus Red Team pros and cons in practice
- Ships as one self-contained binary.
- About 103 techniques across AWS, GCP, Azure, Kubernetes, Entra ID and EKS.
- Warmup, detonate, revert and cleanup commands give a clear lifecycle.
- Apache-2.0 source is open to inspection.
- Techniques run against a live cloud environment, so a mistake in scope has real effects.
- EKS has only 2 techniques and Kubernetes 8, against 46 for AWS.
- The homepage states no pricing, hosted option or support tier.
- It generates activity only; checking whether detections fired is left to your own tooling.
Stratus Red Team pricing
In the catalogue: Free open source tool under the Apache licence.
The homepage makes no statement about pricing, a free plan or a hosted or SaaS offering. The source repository is licensed under Apache-2.0, which governs the use of the code, and the site footer carries the notice Copyright 2021-Present Datadog, Inc. Beyond that, the pages we read give no price list, no commercial support tier and no paid edition. Running the tool will still cost money indirectly, because techniques are detonated against a live cloud environment, so your own provider may bill for resources created during warmup. Check each technique page for what it creates before running it.
Source: the pricing material on stratus-red-team.cloud, as read for Best Breach and Attack Simulation Tools in 2026 and last reviewed on 15 November 2026.
Stratus Red Team in practice
Documented commands are list, status, show, warmup, detonate, revert and cleanup, with a guide to concurrent executions, so each technique can be prepared, run and undone.
Techniques are mapped to MITRE ATT&CK with coverage matrices on the site.
The repository names two core maintainers and carries a Datadog copyright notice on the site.
Stratus Red Team: data and security
Stratus Red Team detonates real techniques against a live cloud environment, so the main security question is where it runs. Use an isolated account or project, because the tool is built to create the conditions an attacker would use.
The pages we read describe no hosted service, so no customer data is sent to a vendor console by the tool itself. They state no certifications and no country of establishment, and the footer names Datadog, Inc. in its copyright line. Review the Apache-2.0 repository before approving it for internal use.
Stratus Red Team fact sheet
| Product | Stratus Red Team |
|---|---|
| Vendor website | stratus-red-team.cloud |
| Headquarters | Not stated by the vendor |
| Source code | Open source, per our records |
| Price visibility | Public on the vendor site |
| Alternatives page | No dedicated page |
| What we do not hold | company size and funding |
| Head-to-head pages | No comparison written |
| Catalogue tags | Cloud techniques, Apache-2.0, Single binary |
| Rank there | #10 of 12 |
| Primary guide | Best Breach and Attack Simulation Tools in 2026 |
What Stratus Red Team connects to
Integrations the vendor names (9):
- AWS
- Amazon EKS
- Google Cloud (GCP)
- Microsoft Azure
- Microsoft Entra ID
- Kubernetes
- MITRE ATT&CK
- Atomic Red Team (counterpart)
- GitHub repository
Close alternatives to Stratus Red Team
4 products in this guide come closest to Stratus Red Team on tags, pricing and region.
- Atomic Red Team (#3 of 12): Not for: buyers wanting dashboards, scheduling and vendor support included. Open source library of small ATT&CK-mapped tests for checking detections.
- Cymulate (#4 of 12): Aimed at: Security teams wanting scorecards and ATT&CK benchmarking across email, endpoint and cloud.
- Infection Monkey (#11 of 12): Open source network simulation tool using propagating agents and a central server. Watch out: the documentation names no product integrations, so no documented route exists into SIEM tooling.
- Mandiant Security Validation (#12 of 12): Director and agent validation drawing on frontline incident intelligence. Watch out: every deployment needs a director plus agents on the controls under test, and cost grows with the agent count.
Every guide that lists Stratus Red Team
| Guide | Position |
|---|---|
| Best Breach and Attack Simulation Tools in 2026 | #10 of 12 |
Stratus Red Team: questions
9 answersWhere is Stratus Red Team based?
The vendor pages we reviewed state no country of establishment for Stratus Red Team, so we do not give one.
Is Stratus Red Team free, or what does it charge?
The pricing entry for Stratus Red Team reads: Free open source tool under the Apache licence. On free access, something can be used at no cost.
What else should I look at besides Stratus Red Team?
The closest products in the same guide are Atomic Red Team, Cymulate, Infection Monkey and Mandiant Security Validation. Compare their entries before settling on Stratus Red Team.
How does Stratus Red Team rank for breach and attack simulation tools?
The breach and attack simulation tools ranking has Stratus Red Team at position 10 out of 12.
Who is Stratus Red Team best for?
Cloud detection engineers validating rules on AWS, Azure, GCP or Kubernetes. It is a weaker match for the following: teams wanting endpoint, email or network coverage in one tool.
What does Stratus Red Team do?
It detonates attack techniques against a live cloud environment so that you can check whether your detection rules notice them.
Which clouds are covered?
The navigation lists AWS, EKS, GCP, Azure, Entra ID and Kubernetes, with about 103 technique pages in total.
Who maintains it?
The GitHub repository names Christophe Tafani-Dereeper and Simon Marechal as core maintainers, and the footer carries a Datadog copyright.
How is it licensed?
The repository datadog/stratus-red-team shows the Apache-2.0 licence on its GitHub page.
Stratus Red Team: sources
Read from the vendor’s own pages on 14 November 2026.
- stratus-red-team.cloud: Binary description, purpose, counterpart to Atomic Red Team and the absence of pricing statements
- stratus-red-team.cloud: Technique counts by platform and ATT&CK coverage matrices
- stratus-red-team.cloud: Documentation commands and concurrent executions guide; footer copyright notice
- github.com/datadog/stratus-red-team: Apache-2.0 licence on the repository page
- github.com/datadog/stratus-red-team: Core maintainers named in the repository
How we rank
Feature lists tell little, so positions rest on setup effort, the true price, portability and fit. Stratus Red Team ends up at #10 among 12. How vendor facts are sourced, and how money can and cannot influence a page, is in the editorial process.