The section your link pointed to isn't on Stratus Red Team's page any more, so we've brought you to the top.
Stratus Red Team is a self-contained binary that detonates granular, offensive attack techniques against live cloud environments, mapped to MITRE ATT&CKMITRE ATT&CKA publicly maintained knowledge base of adversary tactics and techniques observed in real attacks, maintained by MITRE. Cyber tools use it as a common taxonomy to classify, map, and communicate threat behavior..
Stratus Red Team is an open-source command-line tool, free to use, that detonates granular, self-contained attack techniques against a live cloud environment so defenders can check whether their detections actually fire. Its documentation describes it as "Atomic Red Team for the cloud," and it works the same way: pick a technique, such as stopping a CloudTrailCloudTrailAWS service that records API calls and account activity across an AWS environment, giving cyber tools an audit log to detect anomalous or malicious actions. trail or running GCS ransomware via client-side encryption, and run it with a single stratus detonate command, with techniques mapped to MITREMITREA US federally funded research and development center that maintains public frameworks—ATT&CK, CVE, D3FEND—that cyber tools use to classify threats, vulnerabilities, and defensive techniques in a common language.ATT&CKATT&CKA publicly maintained knowledge base by MITRE cataloguing adversary tactics, techniques, and procedures observed in real attacks, giving cyber tools a common taxonomy for classifying and correlating threat behavior.. It ships as a self-contained Go binary, installable via Homebrew, Docker, or prebuilt releases, and is aimed at detection engineers and cloud red teams validating alerting rather than at those building the cloud infrastructure itself. First committed in 2022, it has drawn 55 contributors and 210 commits in the past year, with a release only 21 days ago, putting it well ahead of most projects in adversary emulation.
Stratus Red Team is a self-contained binary that detonates granular, offensive attack techniques against live cloud environments, mapped to MITRE ATT&CK.
Will our detections actually fire when a real attacker technique happens in our cloud account?
runs a single self-contained technique that performs the real API calls of that technique against the live environment, so defenders can check whether an alert was generated rather than guessing from theory
Which MITRE ATT&CK techniques does our alerting pipeline actually cover?
each attack is mapped to a MITRE ATT&CK tactic and technique ID, so running the catalog against an environment shows which tactics produce an alert and which pass silently
Would we catch someone tampering with our cloud audit logging before doing damage?
includes prebuilt techniques for disabling audit logs, log sinks, VPC flow logs, and CloudTrail trails, letting defenders detonate the exact tampering step and see if it surfaces in their SIEM
Would we notice ransomware-style destruction of our storage before it spreads?
ships techniques that simulate ransomware through client-side encryption, key deletion, or file-by-file deletion against cloud storage, so teams can validate object-level and key-management alerting against the real sequence of calls
Would we catch an attacker planting a hidden identity or credential to keep access?
includes persistence techniques that backdoor a managed identity or application with a rogue federated credential, letting defenders confirm their identity-governance alerts trigger on that exact change
Can we tell which simulated run in our cluster or logs corresponds to which attack?
lets the detonation ID be injected into resource labels or pod annotations so activity from a specific run can be correlated against cluster and log activity afterward
14 capabilities
· 1 backed by code, an API document or a real run
Built from Stratus Red Team's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
+AWS attack techniquesshippedProvides ready-to-use AWS-specific attack techniques covering scenarios such as credential access, persistence, exfiltration, and defense evasion.28 releases · 11 other sources · first seen Jan 2022▸
release
28 total
New attack technique aws.impact.ec2-deregister-ami: deregisters an Amazon EC2 AMI to simulate disruption.
v2.36.0 · Aug 2026
· source
· release history
New attack technique aws.impact.ec2-deregister-ami: deregisters an Amazon EC2 AMI to simulate disruption.
v2.36.0 · Aug 2026
· source
· release history
New attack technique: execute commands on an AWS SageMaker Notebook Instance via Lifecycle Configuration (aws.execution.sagemaker-update-lifecycle-config).
v2.24.0 · Feb 2026
· source
· release history
New attack technique: simulate lateral movement via EC2 Serial Console by pushing an SSH public key to multiple instances using SendSerialConsoleSSHPublicKey.
v2.20.0 · Dec 2024
· source
· release history
New attack technique: simulate persistence by generating temporary AWS credentials with GetFederationToken via STS federation.
v2.20.0 · Dec 2024
· source
· release history
New attack technique aws.impact.bedrock-invoke-model simulates adversarial invocation of AWS Bedrock models.
v2.18.0 · Oct 2024
· source
· release history
docs
Deregister an Amazon EC2 AMI
docs update · Aug 2026
· source
Deregister an Amazon EC2 AMI
docs update · Aug 2026
· source
aws # Default configuration applied to all AWS techniques # Prepended to the names of Terraform-managed prerequisites prefix security-testing- tags Environment test Owner StratusCorrelationID aws.persistence.lambda-backdoor-function tags Purpose lambda-detection-validation For AWS techniques, it allows you to:…
docs update · Aug 2026
· source
example
8 total
Detonate the EBS cross-account sharing technique to generate CloudTrail events for ram:AssociateResourceShare and validate your detection coverage for this exfiltration path.$ stratus detonate aws.exfiltration.ec2-share-ebs-volume
v2.37.2 · Oct 2026
· source
Validate detection of adversary command execution on SageMaker by abusing Lifecycle Configurations to run code on a notebook instance.$ stratus detonate aws.execution.sagemaker-update-lifecycle-config
v2.24.0 · Feb 2026
· source
Detonate the EC2 serial console SSH key injection technique to test lateral movement detections in your AWS environment.$ stratus detonate aws.lateral-movement.ec2-serial-console-send-ssh-public-key
v2.20.0 · Dec 2024
· source
Detonate the new AWS IAM login profile update technique to simulate an attacker gaining console access by overwriting a victim user's password.$ stratus detonate aws.credential-access.update-iam-user-login-profile
v2.17.0 · Sep 2024
· source
Run the new SES enumeration technique against your AWS environment$ stratus red aws.discovery.ses-enumerate
v2.15.0 · Apr 2024
· source
Deploy a backdoored IAM role for persistence testing.$ stratus execute aws.persistence.iam-create-backdoor-role
v2.14.0 · Feb 2024
· source
+Attack technique detonation and revertverifiedExecutes and reverts cloud attack techniques via the Stratus CLI, allowing users to simulate and clean up adversary actions in a controlled way.11 releases · 21 other sources · first seen Jan 2022▸
Also counts toward: Command-line interface
release
11 total
Improves the aws.impact.s3-ransomware-client-side-encryption technique to allow SSE-C on target buckets before detonation by calling PutBucketEncryption with BlockedEncryptionTypes set to NONE, enabling CopyObject with customer-provided keys to succeed on new buckets that block SSE-C by default.
v2.37.0 · Sep 2026
· source
· release history
Adds aws.persistence.ec2-create-suspicious-keypair technique, simulating attacker persistence via ec2:CreateKeyPair with a short generic name (xg1), preceded by an ec2:DescribeInstances recon call filtered by key name; mapped to MITRE ATT&CK T1098.001 (Account Manipulation: Additional Cloud Credentials) with…
v2.37.0 · Sep 2026
· source
· release history
Supports SSE-C (server-side encryption with customer-provided keys) before S3 ransomware client-side encryption detonation.
v2.37.0 · Sep 2026
· source
· release history
Improves error messaging when an AWS region is not configured
v2.15.0 · Apr 2024
· source
· release history
Dynamic CLI autocomplete is now available for all attack techniques
v2.1.0 · Jun 2022
· source
· release history
Parallelizes command execution when running stratus warmup, stratus detonate, or stratus cleanup on multiple attack techniques simultaneously.
v1.4.0 · Feb 2022
· source
· release history
docs
Create an EC2 Key Pair with a Suspicious Name
docs update · Oct 2026
· source
Concurrent Executions By default, Stratus Red Team keeps the state of an attack technique in a single directory per technique, $HOME/.stratus-red-team/<technique-id> .
docs update · Aug 2026
· source
# Open a shell in which Grimoire collects the cloud audit logs Then, inside that shell, run the whole lifecycle with Grimoire's detonation ID as the correlation ID: export STRATUS_RED_TEAM_CORRELATION_ID = $GRIMOIRE_DETONATION_ID detonate exit # Grimoire then looks for the events your commands generated Warning Export…
seen Aug 2026
· source
Cloud-focused adversary emulation tool that provides granular, self-contained attack technique simulations mapped to MITRE ATT&CK.
command line
revert — Revert the detonation of an attack technique
v2.10.1 · Nov 2023
· command-line history
Emulate an attacker planting a persistence EC2 key pair with a suspicious name to validate detection of ec2:CreateKeyPair with generic key names.$ stratus detonate aws.persistence.ec2-create-suspicious-keypair
v2.37.0 · Sep 2026
· source
Emulate client-side S3 ransomware encryption against a fresh bucket (where SSE-C was previously blocked by default) to validate detection of PutBucketEncryption and abnormal object overwrite patterns.$ stratus detonate aws.impact.s3-ransomware-client-side-encryption
v2.37.0 · Sep 2026
· source
Run two parallel red-team sessions in the same AWS environment without state collisions by assigning each a unique correlation ID.$ STRATUS_RED_TEAM_CORRELATION_ID=session-alpha stratus detonate aws.impact.ec2-deregister-ami
v2.36.0 · Aug 2026
· source
Detonate the CMK vault deletion ransomware technique to validate alerting when an attacker destroys the Key Vault protecting Blob Storage.$ stratus detonate azure.impact.blob-ransomware-service-storage-cmk
v2.33.0 · Jun 2026
· source
Detonate the CPEK ransomware technique to test detection of encryption key substitution attacks against Azure Blob Storage.$ stratus detonate azure.impact.blob-ransomware-cpek
v2.33.0 · Jun 2026
· source
Detonate the Azure Blob Storage ransomware technique in a lab environment to validate detections for client-managed key abuse.$ stratus detonate azure.impact.blob-ransomware-client-encryption-scope
v2.26.0 · Feb 2026
· source
+GCP attack techniquesshippedProvides ready-to-use GCP-specific attack techniques covering scenarios such as credential access, persistence, and exfiltration.21 releases · 6 other sources · first seen Apr 2022▸
release
21 total
New GCP technique: GCS Ransomware through client-side encryption (gcp.impact.gcs-ransomware-client-side-encryption).
v2.32.0 · May 2026
· source
· release history
New GCP technique: Inject a Malicious Startup Script into a Vertex AI Workbench Instance (gcp.execution.modify-vertex-notebook-startup).
v2.32.0 · May 2026
· source
· release history
New GCP technique: GCS Ransomware through individual file deletion (gcp.impact.gcs-ransomware-individual-deletion).
v2.32.0 · May 2026
· source
· release history
Adds GCP discovery technique: Read GCE Instance Metadata via the Compute API.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Disable Data Access Audit Logs for a GCP Service.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Reduce Log Retention Period on a Cloud Logging Sink Bucket.
v2.31.0 · Apr 2026
· source
· release history
example
Simulate a GCP attacker disabling audit logs to blind your SIEM — useful for testing detection coverage of log-tampering TTPs.$ stratus detonate gcp.defense-evasion.disable-audit-logs
v2.31.0 · Apr 2026
· source
Detonate the multi-zone GCE instance creation technique to test detection of compute resource abuse at scale across regions.$ stratus detonate gcp.impact.create-instances-in-multiple-zones
v2.27.0 · Feb 2026
· source
Emulate post-compromise service account permission enumeration to test discovery-phase alerting in GCP.$ stratus detonate gcp.discovery.enumerate-permissions
v2.27.0 · Feb 2026
· source
Simulate an attacker using a stolen GCE default service account token from outside GCP to validate credential-theft detections.$ stratus detonate gcp.initial-access.use-compute-sa-outside-gcp
v2.27.0 · Feb 2026
· source
Simulate an attacker registering an SSH key to GCP instance metadata to test lateral movement detections.$ stratus detonate gcp.lateral-movement.add-sshkey-instance-metadata
v2.26.0 · Feb 2026
· source
Detonate the new GCP Secret Manager bulk-retrieval technique to test whether your detection engineering catches mass secret access.$ stratus detonate gcp.credential-access.secretmanager-retrieve-secrets
v2.23.0 · Feb 2025
· source
+Azure attack techniquesshippedProvides ready-to-use Azure-specific attack techniques covering credential access and persistence scenarios, such as retrieving App Service publishing credentials and exfiltrating Azure AI Foundry API keys.17 releases · 8 other sources · first seen Jun 2022▸
release
17 total
New Azure technique azure.persistence.exfiltrate-foundry-key: re-enables local (key-based) authentication on an Azure AI Foundry (Cognitive Services) account and retrieves API keys via ListKeys, emulating a Persistence/Credential Access attack path.
v2.35.0 · Jul 2026
· source
· release history
Adds azure.persistence.exfiltrate-foundry-key attack technique to exfiltrate API keys from Azure AI Foundry
v2.35.0 · Jul 2026
· source
· release history
New Azure attack technique: Retrieve App Service Publishing Credentials, enabling simulation of credential theft from Azure App Service.
v2.34.0 · Jul 2026
· source
· release history
New Azure attack technique: Retrieve App Service Publishing Credentials (azure.credential-access.app-service-publishing-credentials).
v2.34.0 · Jul 2026
· source
· release history
New attack technique: simulate Azure Blob Storage ransomware via Customer-Managed Key Vault key and vault deletion.
v2.33.0 · Jun 2026
· source
· release history
New attack technique: simulate Azure Blob Storage ransomware via Customer-Provided Encryption Keys (CPEK).
v2.33.0 · Jun 2026
· source
· release history
docs
Enable Local Authentication and Exfiltrate Azure AI Foundry API Keys Enable Local Authentication and Exfiltrate Azure AI Foundry API Keys
docs update · Aug 2026
· source
Enable Local Authentication and Exfiltrate Azure AI Foundry API Keys Persistence, Credential Access
docs update · Aug 2026
· source
example
Emulate an attacker re-enabling local auth on an Azure AI Foundry account and exfiltrating its API keys — useful for validating detections on Azure Cognitive Services key-listing activity.$ stratus detonate azure.persistence.exfiltrate-foundry-key
v2.35.0 · Jul 2026
· source
Execute the new Azure persistence technique in a CLI lab environment.$ stratus red azure.persistence.exfiltrate-foundry-key execute
v2.35.0 · Jul 2026
· source
Test your Entra ID application-layer detection by adding a rogue Federated Identity Credential to a service principal.$ stratus detonate entra-id.persistence.backdoor-application-fic
v2.31.0 · Apr 2026
· source
Test whether your Azure identity governance controls catch a backdoored Managed Identity being granted an external Federated Identity Credential.$ stratus detonate azure.persistence.backdoor-managed-identity-fic
v2.31.0 · Apr 2026
· source
Test your Azure blob storage ransomware detection by simulating individual file deletions across a Storage Account.$ stratus detonate azure.impact.blob-ransomware-individual-file-deletion
v2.24.0 · Feb 2026
· source
Detonate the STS federation token technique to validate persistence detections for temporary credential generation.$ stratus detonate aws.persistence.sts-federation-token
v2.20.0 · Dec 2024
· source
+Kubernetes cluster supportshippedProvides attack techniques and capabilities specific to Kubernetes environments, including privilege escalation and credential access.10 releases · 3 other sources · first seen Feb 2022▸
release
10 total
Support KUBECONFIG with multiple colon-separated paths for Kubernetes clusters
v2.36.1 · Sep 2026
· source
· release history
Kubernetes configuration now supports pod annotations.
v2.32.0 · May 2026
· source
· release history
Enables detonation ID templating in the Stratus Red Team configuration file, e.g. for injecting the ID into Kubernetes pod labels.
v2.32.1 · May 2026
· source
· release history
Kubernetes resources are now labeled with datadoghq.com/stratus-red-team-stage=warmup|detonation to distinguish warmup from detonation resources.
v2.32.0 · May 2026
· source
· release history
Adds initial support for EKS attack techniques, enabling adversary simulation against Amazon Elastic Kubernetes Service environments.
v2.16.0 · Aug 2024
· source
· release history
Use separate kubeconfig contexts for production and development clusters in a single run.$ export KUBECONFIG='/path/to/kubeconfig-prod:/path/to/kubeconfig-dev' stratus-red-team detonate azure.kubernetes-list-clusters
v2.36.1 · Sep 2026
· source
Inject the detonation ID into a Kubernetes pod label via the config file to correlate attack simulation runs with cluster activity.$ # Example stratus config snippet using detonation ID templating detonation_id: "{{ .DetonationID }}" pod_labels: stratus-detonation: "{{ .DetonationID }}"
v2.32.1 · May 2026
· source
Execute the new technique to dump all secrets within a Kubernetes cluster.$ stratus execute k8s.credential-access.dump-secrets
v1.5.0 · Feb 2022
· source
+Concurrent attack execution supportshippedSupports isolated concurrent executions of multiple attack techniques in the same environment via correlation IDs.6 releases · 4 other sources · first seen Aug 2026▸
release
Enables concurrent detonation across all providers (AWS, Azure, GCP, Entra ID, Kubernetes, EKS) by embedding a short correlation ID (var.correlation.short) in Terraform-managed resource names, preventing resource collisions when multiple users share an environment.
v2.36.1 · Sep 2026
· source
· release history
Adds opt-out of the Terraform cache to prevent concurrency issues during parallel detonations.
v2.36.1 · Sep 2026
· source
· release history
Propagates Azure correlation IDs via clientRequestID (migrated from user-agent) so detonation activity is traceable across Azure API calls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
v2.36.1 · Sep 2026
· source
· release history
Propagate Azure correlation IDs across cloud operations via new correlation id propagation logic
v2.36.1 · Sep 2026
· source
· release history
Supports isolated concurrent executions via the STRATUS_RED_TEAM_CORRELATION_ID environment variable, preventing errors or duplicates when multiple attack techniques run in the same environment simultaneously.
v2.36.0 · Aug 2026
· source
· release history
Adds STRATUS_RED_TEAM_CORRELATION_ID environment variable to isolate concurrent attack-technique executions in the same environment, preventing errors and duplicate state.
v2.36.0 · Aug 2026
· source
· release history
docs
file. All resource names must embed var.correlation.short so concurrent executions don't collide — see the create-attack-technique skill for details.
seen Sep 2026
· source
Concurrent Executions By default, Stratus Red Team keeps the state of an attack technique in a single directory per technique, $HOME/.stratus-red-team/<technique-id> .
docs update · Aug 2026
· source
, under one directory per attack technique. If you set a correlation ID, the state of that execution is stored one level deeper, in $HOME/.stratus-red-team/<technique-id>/<correlation-id> , so that concurrent executions of the same attack technique do not share a Terraform state. See Concurrent executions
seen Aug 2026
· source
If you isolate executions with runner.WithCorrelationID , only reports on that execution when the same correlation ID is set in its environment - see Concurrent executions .
seen Aug 2026
· source
+Library embedding with configurable loggingshippedExposes a controllable logger package so that Stratus can be embedded in larger cyber tooling with log output routed through any slog-compatible handler such as zap or logrus.4 releases · 1 other source · first seen May 2023▸
release
Adds controllable logger support via pkg/stratus/log, allowing library users to plug in their own logger.
v2.34.0 · Jul 2026
· source
· release history
New pkg/stratus/log package exposes a controllable logger, letting library embedders route Stratus log output through any slog.Handler (e.g., zap, logrus).
v2.34.0 · Jul 2026
· source
· release history
Allows specifying a context when instantiating Stratus Red Team runners, propagating it down to Terraform for more flexible programmatic use.
v2.16.0 · Aug 2024
· source
· release history
Adds automatic installation of shell completions for bash, zsh, and fish when installing Stratus Red Team via Homebrew
v2.5.4 · May 2023
· source
· release history
example
Route all Stratus library log output through your own zap logger instead of the default stdout handler — useful when embedding Stratus in a larger tool.$ import ( "log/slog" stratuslog "github.com/datadog/stratus-red-team/v2/pkg/stratus/log" "go.uber.org/zap" "go.uber.org/zap/exp/zapslog" ) func init() { zapLogger, _ := zap.NewProduction() handler :=…
v2.34.0 · Jul 2026
· source
+GCP defense evasion techniquesshippedProvides specific GCP attack techniques for disabling logging and flow logs to evade detection.5 releases · first seen Apr 2026▸
release
Adds GCP defense-evasion technique: Disable Data Access Audit Logs for a GCP Service.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Reduce Log Retention Period on a Cloud Logging Sink Bucket.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Delete a Cloud DNS Logging Policy.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Disable VPC Flow Logs on a Subnet.
v2.31.0 · Apr 2026
· source
· release history
Adds GCP defense-evasion technique: Attempt to Remove a GCP Project from its Organization.
v2.31.0 · Apr 2026
· source
· release history
+Programmatic integration controlsshippedAllows Stratus to be embedded in larger cyber tooling with configurable state management, Terraform binaries, credentials, and cloud storage backends.4 releases · first seen Apr 2026▸
release
Programmatic usage now supports supplying an existing Terraform binary instead of downloading its own.
v2.31.0 · Apr 2026
· source
· release history
Programmatic usage now supports custom StateManager, TerraformManager, ProviderFactory, Config, and CorrelationID when launching the runner.
v2.31.0 · Apr 2026
· source
· release history
Programmatic usage now supports configurable cloud credentials rather than relying on environment variables.
v2.31.0 · Apr 2026
· source
· release history
Programmatic usage now supports an S3 bucket for internal and Terraform state storage.
v2.31.0 · Apr 2026
· source
· release history
+AWS exfiltration techniquesshippedProvides specific AWS techniques for data exfiltration, such as exporting disks or RDS snapshots.3 releases · first seen Jan 2022▸
release
Adds attack technique aws.exfiltration.ec2-share-ebs-volume to emulate EBS volume exfiltration by sharing a volume with an external AWS account via AWS Resource Access Manager (RAM) using the AWSRAMPermissionEBSVolumeCopyAccess managed permission, mapped to MITRE ATT&CK tactic Exfiltration and technique…
v2.37.2 · Oct 2026
· source
· release history
Adds Exfiltrate an RDS snapshot attack technique
v0.0.20 · Jan 2022
· source
· release history
Adds new attack technique: Exfiltrate an AMI by Making it Public (shares with external account)
v0.0.14 · Jan 2022
· source
· release history
+YAML technique inventory generationshippedProvides CLI and Makefile commands to export a YAML inventory of all available attack techniques.1 release · 1 other source · first seen Nov 2022▸
release
make docs now generates a YAML file with all available attack techniques
v2.4.9 · Nov 2022
· source
· release history
example
Generate a YAML inventory of all available Stratus Red Team attack techniques.$ make docs
v2.4.9 · Nov 2022
· source
+Terraform provider configuration for Azure techniquesshippedManages infrastructure prerequisites for Azure attack techniques through Terraform provider integration, requiring specific environment variables such as ARM_SUBSCRIPTION_ID.1 release · first seen Jul 2026▸
Also counts toward: Terraform provider
release
The azure.persistence.exfiltrate-foundry-key technique requires the ARM_SUBSCRIPTION_ID environment variable (not AZURE_SUBSCRIPTION_ID) due to an upgrade to the azurerm Terraform provider 4.80.0.
v2.35.0 · Jul 2026
· source
· release history
+Threat-intelligence coverage mappingshippedFetches a threat-intelligence report, extracts cloud TTPs, classifies them against existing Stratus Red Team coverage, and drafts GitHub issues for any identified gaps.1 release · first seen Jul 2026▸
release
New map-threat-intel-coverage agent skill fetches a threat-intelligence report, extracts cloud TTPs, classifies each against existing Stratus Red Team coverage, and drafts GitHub issues for gaps.
v2.34.0 · Jul 2026
· source
· release history
+AWS S3 object encryption simulationshippedProvides specific AWS techniques for simulating the client-side encryption of S3 objects as part of an attack scenario.1 other source · first seen Aug 2023▸
example
Simulate an attacker encrypting S3 objects using client-side encryption logic$ stratus red aws.impact.s3-ransomware-client-side-encryption detonate
v2.9.0 · Aug 2023
· source
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for Stratus Red Team, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Stratus Red Team puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
59 readings of Datadog's pricing page since Sep 2021, with 27 relaunches of its plan lineup and 21 changes to what its plans include — each one dated, compared with the reading before it, and explained for someone buying the tool.
Pricing and packaging history is included with Researcher and Business. See how every vendor we track sells, and how that has changed over time, using data we don't publish anywhere else.
Each offering on the pricing page links to its own page of plans, read at its latest capture.
Plan relaunches
Plans, prices and descriptions are quoted from the vendor's own pricing page as we read it on each date.
A plan missing from a later reading is shown as no longer listed on the page — a statement about the page, not the product.
Readings that failed to show any plans are left out rather than read as a change.
Website history
datadoghq.com, every change
Datadog's home page and 40 more pages as they looked each month from August 2021 to October 2026: 52 renders, 7 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
Nothing first seen in this window. That doesn't mean Stratus Red Team shipped nothing, only that we found no record of it.
Changes per month New Updated Retired
2026-10
2
How we count
Read from 4 of 55 release notes and docs updates we hold for Stratus Red Team. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through Stratus Red Team's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
Show
Coverage in all entries
55 entries
No entries match these filters.
October 20264
September 20262
August 20268
July 20262
June 20261
May 20262
April 20261
March 20262
February 20264
February 20251
December 20241
October 20242
September 20241
August 20241
April 20241
February 20241
January 20241
November 20232
August 20231
June 20232
May 20231
November 20221
August 20221
July 20221
June 20222
April 20221
February 20223
January 20225
Project health
Issue, contributor and maintainer activity in datadog/stratus-red-team, 2023-10 – 2026-09,
as of 2026-09-25. Twelve-month figures first; the trend lines run
the whole window.
Contributors18+8 vs prior 12 months
Maintainers3+2 joined · −0 left, last 12 months
Bus factor2committers behind half the commits
Community-filed92%of issues opened, last 12 months
Median time to close645 daysfirst maintainer reply 62 days
Open backlog40of 211 issues ever filed
Issues opened / month0 · 0communitymaintainers
Open backlog40
Contributors / month2
Commits / month6
Stars2,401
Issue themes, last 12 months
bugs 9%
features 8%
docs 8%
other 75%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Threat coverage
Content for the last year of exploited CVEs and attack reports.
Stratus Red Team has content for 1 of the 982 threats tracked in the last year, 0 of them exact.
exact0names the CVE
related1names the technique or product
tracked982threats in the last year
See the threats, and how similar tools compare threat by threat, with Researcher and Business.