[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B6BJ6DVXF87Y87AV27ES36":3,"skill-same:01M7B6BJ6DVXF87Y87AV27ES36":80},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":13,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":59},"01M7B6BJ6DVXF87Y87AV27ES36","emulating-cloud-attacks-with-stratus-red-team",null,"Install and run Stratus Red Team to detonate granular, MITRE ATT&CK-mapped AWS, Azure, GCP, and Kubernetes attack techniques through their warmup-detonate-revert-cleanup lifecycle, then verify the telemetry they generate. Use to validate that cloud detections (CloudTrail, GuardDuty, Microsoft Sentinel, GCP SCC, Falco) actually fire, or to run a repeatable purple-team exercise generating realistic attacker telemetry.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: emulating-cloud-attacks-with-stratus-red-team\ndescription: Install and run Stratus Red Team to detonate granular, MITRE ATT&CK-mapped\n  AWS, Azure, GCP, and Kubernetes attack techniques through their warmup-detonate-revert-cleanup\n  lifecycle, then verify the telemetry they generate. Use to validate that cloud detections\n  (CloudTrail, GuardDuty, Microsoft Sentinel, GCP SCC, Falco) actually fire, or to run a\n  repeatable purple-team exercise generating realistic attacker telemetry.\ndomain: cybersecurity\nsubdomain: cloud-security\ntags:\n- stratus-red-team\n- adversary-emulation\n- cloud-security\n- detection-validation\n- purple-team\n- aws\n- mitre-attack\n- threat-detection\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- DE.CM-01\nmitre_attack:\n- T1078\n---\n# Emulating Cloud Attacks with Stratus Red Team\n\n> **Legal Notice:** This skill is for authorized security testing and detection-validation purposes only. Stratus Red Team spins up and modifies real cloud infrastructure in the account whose credentials you supply. Only run it in accounts you own or are explicitly authorized to test. Always `cleanup` afterwards to avoid orphaned, billable, or insecure resources. Unauthorized use against systems you do not control is illegal.\n\n## Overview\n\nStratus Red Team is an open-source \"Atomic Red Team for the cloud,\" maintained by Datadog. It is a self-contained Go binary that programmatically *detonates* granular, well-documented offensive techniques against AWS, Azure, GCP, and Kubernetes, then lets you cleanly revert and remove everything it created. Unlike a full exploitation framework, Stratus is purpose-built for **detection engineering and purple teaming**: each technique maps to a MITRE ATT&CK tactic and ships with a precise description of the cloud API calls it generates, so a blue team can confirm whether their CloudTrail\u002FGuardDuty\u002FSentinel\u002FFalco detections actually fire.\n\nEvery technique has a deterministic lifecycle. Stratus first provisions any prerequisite infrastructure with embedded Terraform (the **warmup** phase), then performs the malicious actions (**detonate**), optionally **revert**s the side effects so you can detonate again, and finally **cleanup**s the prerequisite infrastructure. Because the prerequisites and the attack are decoupled, you can iterate on a detection by detonating the same technique repeatedly without re-provisioning. The tool uses your standard cloud SDK credential chain (AWS profiles\u002Fenv vars, `az login`, GCP ADC, kubeconfig), so it operates with exactly the permissions of the identity you authenticate as.\n\nThis skill covers installing Stratus, listing and filtering the technique catalog, running the full warmup-detonate-revert-cleanup lifecycle, mapping detonations to the telemetry they produce, and wiring the results into a detection-validation workflow. Source: github.com\u002FDataDog\u002Fstratus-red-team and stratus-red-team.cloud official documentation.\n\n## When to Use\n\n- Validating that a new or existing cloud detection rule (CloudTrail, GuardDuty, Microsoft Sentinel, GCP SCC, Falco) actually triggers on real attacker activity\n- Building a repeatable purple-team exercise for cloud TTPs without writing bespoke attack scripts\n- Generating realistic, MITRE-mapped telemetry to test SIEM ingestion and alert routing\n- Measuring detection coverage of a cloud environment against a known catalog of techniques\n- Onboarding analysts with safe, reversible hands-on cloud attack simulations\n\n## Prerequisites\n\n- Stratus Red Team binary (Go 1.23+ to build from source, or Homebrew\u002FDocker):\n  ```bash\n  # Go install\n  go install -v github.com\u002Fdatadog\u002Fstratus-red-team\u002Fv2\u002Fcmd\u002Fstratus@latest\n\n  # Homebrew\n  brew tap datadog\u002Fstratus-red-team https:\u002F\u002Fgithub.com\u002FDataDog\u002Fstratus-red-team\n  brew install datadog\u002Fstratus-red-team\u002Fstratus-red-team\n\n  # Docker\n  docker run --rm -v $HOME\u002F.stratus-red-team\u002F:\u002Froot\u002F.stratus-red-team\u002F \\\n    -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN \\\n    ghcr.io\u002Fdatadog\u002Fstratus-red-team list\n  ```\n- Authenticated cloud credentials for the target provider:\n  ```bash\n  # AWS — verify identity before detonating\n  export AWS_PROFILE=stratus-lab\n  aws sts get-caller-identity\n\n  # Azure\n  az login\n\n  # GCP\n  gcloud auth application-default login\n\n  # Kubernetes\n  kubectl config current-context\n  ```\n- A dedicated, non-production lab account or subscription (techniques create real resources)\n- Terraform is embedded; no separate install is required, but outbound HTTPS to download provider plugins on first warmup is needed\n\n## Objectives\n\n- Install Stratus Red Team and confirm the target cloud identity\n- Enumerate and filter techniques by platform and MITRE ATT&CK tactic\n- Execute the warmup -> detonate -> revert -> cleanup lifecycle safely\n- Map each detonation to the cloud API calls and log sources it generates\n- Validate detection rules against the produced telemetry and track coverage\n- Guarantee no residual infrastructure remains after testing\n\n## MITRE ATT&CK Mapping\n\n| ID | Name | Use in this skill |\n|----|------|-------------------|\n| T1078 | Valid Accounts | Emulation runs as a valid cloud identity; many techniques abuse legitimate credentials\u002FAPI access |\n| T1078.004 | Valid Accounts: Cloud Accounts | e.g. `aws.credential-access.ec2-steal-instance-credentials` produces cloud-account abuse telemetry |\n| T1580 | Cloud Infrastructure Discovery | Discovery-tactic techniques such as `aws.discovery.*` |\n| T1530 | Data from Cloud Storage | Exfiltration techniques such as `aws.exfiltration.ec2-share-ebs-snapshot` |\n| T1098 | Account Manipulation | Persistence techniques such as `aws.persistence.iam-create-admin-user` |\n\n## Workflow\n\n### 1. Confirm identity and list the technique catalog\nAlways confirm which account you are about to attack, then browse the catalog.\n```bash\naws sts get-caller-identity\nstratus list\n# Filter to a single platform\nstratus list --platform aws\n# Filter by MITRE ATT&CK tactic\nstratus list --mitre-attack-tactic credential-access\n```\n\n### 2. Inspect a specific technique before running it\nRead exactly what a technique will do and which detonation\u002Ftelemetry it produces.\n```bash\nstratus show aws.credential-access.ec2-steal-instance-credentials\n```\n\n### 3. Warm up prerequisite infrastructure\nProvision the prerequisites with embedded Terraform without performing the attack yet.\n```bash\nstratus warmup aws.credential-access.ec2-steal-instance-credentials\nstratus status\n```\n\n### 4. Detonate the technique\nExecute the malicious actions; this is what your detections must catch. Warmup is implicit if not already done.\n```bash\nstratus detonate aws.credential-access.ec2-steal-instance-credentials\n# Detonate and force a re-warmup in one step\nstratus detonate aws.persistence.iam-create-admin-user --force\n```\n\n### 5. Inspect status and the telemetry generated\nCheck lifecycle state, then pull the corresponding control-plane logs to confirm the attack landed.\n```bash\nstratus status\n# Pull recent CloudTrail events to verify the detonation\naws cloudtrail lookup-events \\\n  --lookup-attributes AttributeKey=EventName,AttributeValue=CreateAccessKey \\\n  --max-results 10\n```\n\n### 6. Validate the detection\nConfirm your SIEM\u002Fdetection fired. Example: query Athena\u002FCloudTrail or check GuardDuty findings.\n```bash\naws guardduty list-findings --detector-id \"$DETECTOR_ID\" \\\n  --finding-criteria '{\"Criterion\":{\"updatedAt\":{\"GreaterThanOrEqual\":'\"$(date -d '-1 hour' +%s)\"'000}}}'\n```\n\n### 7. Revert side effects to re-detonate\nUndo the detonation while keeping prerequisites so you can iterate on a detection.\n```bash\nstratus revert aws.credential-access.ec2-steal-instance-credentials\nstratus detonate aws.credential-access.ec2-steal-instance-credentials   # run again\n```\n\n### 8. Clean up all infrastructure\nTear down everything a technique created. Always finish here.\n```bash\nstratus cleanup aws.credential-access.ec2-steal-instance-credentials\n# Nuke everything Stratus ever provisioned in this account\nstratus cleanup --all\nstratus status   # confirm COLD state for all techniques\n```\n\n### 9. Drive it programmatically for coverage runs\nLoop over a tactic to measure detection coverage, then clean up. See `scripts\u002Fagent.py`.\n```bash\npython scripts\u002Fagent.py --platform aws --tactic credential-access --detonate --cleanup\n```\n\n## Tools and Resources\n\n| Resource | Purpose | Link |\n|----------|---------|------|\n| Stratus Red Team GitHub | Source, releases, technique source | https:\u002F\u002Fgithub.com\u002FDataDog\u002Fstratus-red-team |\n| Stratus Red Team docs | Technique catalog and lifecycle reference | https:\u002F\u002Fstratus-red-team.cloud |\n| Attack technique list | Full per-platform technique IDs | https:\u002F\u002Fstratus-red-team.cloud\u002Fattack-techniques\u002Flist\u002F |\n| MITRE ATT&CK Cloud | Tactic\u002Ftechnique reference for mapping | https:\u002F\u002Fattack.mitre.org\u002Fmatrices\u002Fenterprise\u002Fcloud\u002F |\n| Atomic Red Team | Complementary endpoint emulation | https:\u002F\u002Fgithub.com\u002Fredcanaryco\u002Fatomic-red-team |\n\n## Detection-Validation Mapping\n\nFor purple-team value, pair each detonation with the telemetry and detection it should trigger:\n\n| Technique | Expected telemetry | Detection to validate |\n|-----------|--------------------|-----------------------|\n| `aws.credential-access.ec2-steal-instance-credentials` | CloudTrail use of role creds from a non-EC2 IP | GuardDuty `UnauthorizedAccess:IAMUser\u002FInstanceCredentialExfiltration` |\n| `aws.persistence.iam-create-admin-user` | `CreateUser` + `AttachUserPolicy` (AdministratorAccess) | CloudTrail\u002FSentinel rule on admin-policy attach |\n| `aws.exfiltration.ec2-share-ebs-snapshot` | `ModifySnapshotAttribute` sharing to external account | GuardDuty `Exfiltration:EC2\u002F...` \u002F custom rule |\n| `aws.discovery.ec2-enumerate-from-instance` | Burst of `Describe*` from instance role | Enumeration-burst detection |\n\nAfter detonation, confirm the alert fired end-to-end (source -> SIEM -> ticket). If it\ndid not, you have found a coverage gap; document it before cleaning up.\n\n## Cost and Safety Notes\n\n- Some techniques provision billable resources (EC2 instances, EBS snapshots). Always\n  run `stratus cleanup --all` and verify `stratus status` returns COLD.\n- Never run Stratus with production credentials; use a dedicated lab account\u002Fsubscription.\n- The state directory `~\u002F.stratus-red-team\u002F` holds Terraform state — preserve it until\n  cleanup completes, or you may strand resources.\n\n## Lifecycle State Reference\n\n| State | Meaning |\n|-------|---------|\n| COLD | No prerequisites provisioned; nothing to clean up |\n| WARM | Prerequisites provisioned but not yet detonated |\n| DETONATED | Attack actions performed; side effects present |\n\n## Validation Criteria\n\n- [ ] Stratus installed and `stratus list` returns the technique catalog\n- [ ] Target cloud identity confirmed via `sts get-caller-identity` \u002F equivalent\n- [ ] Technique inspected with `stratus show` before detonation\n- [ ] Warmup completed and status shows WARM\n- [ ] Detonation completed and status shows DETONATED\n- [ ] Generated telemetry located in CloudTrail\u002FGuardDuty\u002FSIEM\n- [ ] Detection rule confirmed to fire (or coverage gap documented)\n- [ ] Technique reverted and re-detonated to confirm repeatability\n- [ ] `stratus cleanup --all` run and status returns COLD for every technique\n- [ ] No orphaned billable resources remain in the account\n","# Emulating Cloud Attacks with Stratus Red Team\n\n> **Legal Notice:** This skill is for authorized security testing and detection-validation purposes only. Stratus Red Team spins up and modifies real cloud infrastructure in the account whose credentials you supply. Only run it in accounts you own or are explicitly authorized to test. Always `cleanup` afterwards to avoid orphaned, billable, or insecure resources. Unauthorized use against systems you do not control is illegal.\n\n## Overview\n\nStratus Red Team is an open-source \"Atomic Red Team for the cloud,\" maintained by Datadog. It is a self-contained Go binary that programmatically *detonates* granular, well-documented offensive techniques against AWS, Azure, GCP, and Kubernetes, then lets you cleanly revert and remove everything it created. Unlike a full exploitation framework, Stratus is purpose-built for **detection engineering and purple teaming**: each technique maps to a MITRE ATT&CK tactic and ships with a precise description of the cloud API calls it generates, so a blue team can confirm whether their CloudTrail\u002FGuardDuty\u002FSentinel\u002FFalco detections actually fire.\n\nEvery technique has a deterministic lifecycle. Stratus first provisions any prerequisite infrastructure with embedded Terraform (the **warmup** phase), then performs the malicious actions (**detonate**), optionally **revert**s the side effects so you can detonate again, and finally **cleanup**s the prerequisite infrastructure. Because the prerequisites and the attack are decoupled, you can iterate on a detection by detonating the same technique repeatedly without re-provisioning. The tool uses your standard cloud SDK credential chain (AWS profiles\u002Fenv vars, `az login`, GCP ADC, kubeconfig), so it operates with exactly the permissions of the identity you authenticate as.\n\nThis skill covers installing Stratus, listing and filtering the technique catalog, running the full warmup-detonate-revert-cleanup lifecycle, mapping detonations to the telemetry they produce, and wiring the results into a detection-validation workflow. Source: github.com\u002FDataDog\u002Fstratus-red-team and stratus-red-team.cloud official documentation.\n\n## When to Use\n\n- Validating that a new or existing cloud detection rule (CloudTrail, GuardDuty, Microsoft Sentinel, GCP SCC, Falco) actually triggers on real attacker activity\n- Building a repeatable purple-team exercise for cloud TTPs without writing bespoke attack scripts\n- Generating realistic, MITRE-mapped telemetry to test SIEM ingestion and alert routing\n- Measuring detection coverage of a cloud environment against a known catalog of techniques\n- Onboarding analysts with safe, reversible hands-on cloud attack simulations\n\n## Prerequisites\n\n- Stratus Red Team binary (Go 1.23+ to build from source, or Homebrew\u002FDocker):\n  ```bash\n  # Go install\n  go install -v github.com\u002Fdatadog\u002Fstratus-red-team\u002Fv2\u002Fcmd\u002Fstratus@latest\n\n  # Homebrew\n  brew tap datadog\u002Fstratus-red-team https:\u002F\u002Fgithub.com\u002FDataDog\u002Fstratus-red-team\n  brew install datadog\u002Fstratus-red-team\u002Fstratus-red-team\n\n  # Docker\n  docker run --rm -v $HOME\u002F.stratus-red-team\u002F:\u002Froot\u002F.stratus-red-team\u002F \\\n    -e AWS_ACCESS_KEY_ID -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN \\\n    ghcr.io\u002Fdatadog\u002Fstratus-red-team list\n  ```\n- Authenticated cloud credentials for the target provider:\n  ```bash\n  # AWS — verify identity before detonating\n  export AWS_PROFILE=stratus-lab\n  aws sts get-caller-identity\n\n  # Azure\n  az login\n\n  # GCP\n  gcloud auth application-default login\n\n  # Kubernetes\n  kubectl config current-context\n  ```\n- A dedicated, non-production lab account or subscription (techniques create real resources)\n- Terraform is embedded; no separate install is required, but outbound HTTPS to download provider plugins on first warmup is needed\n\n## Objectives\n\n- Install Stratus Red Team and confirm the target cloud identity\n- Enumerate and filter techniques by platform and MITRE ATT&CK tactic\n- Execute the warmup -> detonate -> revert -> cleanup lifecycle safely\n- Map each detonation to the cloud API calls and log sources it generates\n- Validate detection rules against the produced telemetry and track coverage\n- Guarantee no residual infrastructure remains after testing\n\n## MITRE ATT&CK Mapping\n\n| ID | Name | Use in this skill |\n|----|------|-------------------|\n| T1078 | Valid Accounts | Emulation runs as a valid cloud identity; many techniques abuse legitimate credentials\u002FAPI access |\n| T1078.004 | Valid Accounts: Cloud Accounts | e.g. `aws.credential-access.ec2-steal-instance-credentials` produces cloud-account abuse telemetry |\n| T1580 | Cloud Infrastructure Discovery | Discovery-tactic techniques such as `aws.discovery.*` |\n| T1530 | Data from Cloud Storage | Exfiltration techniques such as `aws.exfiltration.ec2-share-ebs-snapshot` |\n| T1098 | Account Manipulation | Persistence techniques such as `aws.persistence.iam-create-admin-user` |\n\n## Workflow\n\n### 1. Confirm identity and list the technique catalog\nAlways confirm which account you are about to attack, then browse the catalog.\n```bash\naws sts get-caller-identity\nstratus list\n# Filter to a single platform\nstratus list --platform aws\n# Filter by MITRE ATT&CK tactic\nstratus list --mitre-attack-tactic credential-access\n```\n\n### 2. Inspect a specific technique before running it\nRead exactly what a technique will do and which detonation\u002Ftelemetry it produces.\n```bash\nstratus show aws.credential-access.ec2-steal-instance-credentials\n```\n\n### 3. Warm up prerequisite infrastructure\nProvision the prerequisites with embedded Terraform without performing the attack yet.\n```bash\nstratus warmup aws.credential-access.ec2-steal-instance-credentials\nstratus status\n```\n\n### 4. Detonate the technique\nExecute the malicious actions; this is what your detections must catch. Warmup is implicit if not already done.\n```bash\nstratus detonate aws.credential-access.ec2-steal-instance-credentials\n# Detonate and force a re-warmup in one step\nstratus detonate aws.persistence.iam-create-admin-user --force\n```\n\n### 5. Inspect status and the telemetry generated\nCheck lifecycle state, then pull the corresponding control-plane logs to confirm the attack landed.\n```bash\nstratus status\n# Pull recent CloudTrail events to verify the detonation\naws cloudtrail lookup-events \\\n  --lookup-attributes AttributeKey=EventName,AttributeValue=CreateAccessKey \\\n  --max-results 10\n```\n\n### 6. Validate the detection\nConfirm your SIEM\u002Fdetection fired. Example: query Athena\u002FCloudTrail or check GuardDuty findings.\n```bash\naws guardduty list-findings --detector-id \"$DETECTOR_ID\" \\\n  --finding-criteria '{\"Criterion\":{\"updatedAt\":{\"GreaterThanOrEqual\":'\"$(date -d '-1 hour' +%s)\"'000}}}'\n```\n\n### 7. Revert side effects to re-detonate\nUndo the detonation while keeping prerequisites so you can iterate on a detection.\n```bash\nstratus revert aws.credential-access.ec2-steal-instance-credentials\nstratus detonate aws.credential-access.ec2-steal-instance-credentials   # run again\n```\n\n### 8. Clean up all infrastructure\nTear down everything a technique created. Always finish here.\n```bash\nstratus cleanup aws.credential-access.ec2-steal-instance-credentials\n# Nuke everything Stratus ever provisioned in this account\nstratus cleanup --all\nstratus status   # confirm COLD state for all techniques\n```\n\n### 9. Drive it programmatically for coverage runs\nLoop over a tactic to measure detection coverage, then clean up. See `scripts\u002Fagent.py`.\n```bash\npython scripts\u002Fagent.py --platform aws --tactic credential-access --detonate --cleanup\n```\n\n## Tools and Resources\n\n| Resource | Purpose | Link |\n|----------|---------|------|\n| Stratus Red Team GitHub | Source, releases, technique source | https:\u002F\u002Fgithub.com\u002FDataDog\u002Fstratus-red-team |\n| Stratus Red Team docs | Technique catalog and lifecycle reference | https:\u002F\u002Fstratus-red-team.cloud |\n| Attack technique list | Full per-platform technique IDs | https:\u002F\u002Fstratus-red-team.cloud\u002Fattack-techniques\u002Flist\u002F |\n| MITRE ATT&CK Cloud | Tactic\u002Ftechnique reference for mapping | https:\u002F\u002Fattack.mitre.org\u002Fmatrices\u002Fenterprise\u002Fcloud\u002F |\n| Atomic Red Team | Complementary endpoint emulation | https:\u002F\u002Fgithub.com\u002Fredcanaryco\u002Fatomic-red-team |\n\n## Detection-Validation Mapping\n\nFor purple-team value, pair each detonation with the telemetry and detection it should trigger:\n\n| Technique | Expected telemetry | Detection to validate |\n|-----------|--------------------|-----------------------|\n| `aws.credential-access.ec2-steal-instance-credentials` | CloudTrail use of role creds from a non-EC2 IP | GuardDuty `UnauthorizedAccess:IAMUser\u002FInstanceCredentialExfiltration` |\n| `aws.persistence.iam-create-admin-user` | `CreateUser` + `AttachUserPolicy` (AdministratorAccess) | CloudTrail\u002FSentinel rule on admin-policy attach |\n| `aws.exfiltration.ec2-share-ebs-snapshot` | `ModifySnapshotAttribute` sharing to external account | GuardDuty `Exfiltration:EC2\u002F...` \u002F custom rule |\n| `aws.discovery.ec2-enumerate-from-instance` | Burst of `Describe*` from instance role | Enumeration-burst detection |\n\nAfter detonation, confirm the alert fired end-to-end (source -> SIEM -> ticket). If it\ndid not, you have found a coverage gap; document it before cleaning up.\n\n## Cost and Safety Notes\n\n- Some techniques provision billable resources (EC2 instances, EBS snapshots). Always\n  run `stratus cleanup --all` and verify `stratus status` returns COLD.\n- Never run Stratus with production credentials; use a dedicated lab account\u002Fsubscription.\n- The state directory `~\u002F.stratus-red-team\u002F` holds Terraform state — preserve it until\n  cleanup completes, or you may strand resources.\n\n## Lifecycle State Reference\n\n| State | Meaning |\n|-------|---------|\n| COLD | No prerequisites provisioned; nothing to clean up |\n| WARM | Prerequisites provisioned but not yet detonated |\n| DETONATED | Attack actions performed; side effects present |\n\n## Validation Criteria\n\n- [ ] Stratus installed and `stratus list` returns the technique catalog\n- [ ] Target cloud identity confirmed via `sts get-caller-identity` \u002F equivalent\n- [ ] Technique inspected with `stratus show` before detonation\n- [ ] Warmup completed and status shows WARM\n- [ ] Detonation completed and status shows DETONATED\n- [ ] Generated telemetry located in CloudTrail\u002FGuardDuty\u002FSIEM\n- [ ] Detection rule confirmed to fire (or coverage gap documented)\n- [ ] Technique reverted and re-detonated to confirm repeatability\n- [ ] `stratus cleanup --all` run and status returns COLD for every technique\n- [ ] No orphaned billable resources remain in the account\n",{"name":5,"tags":24,"author":33,"domain":34,"license":14,"version":35,"nist_csf":36,"subdomain":27,"description":7,"mitre_attack":38},[25,26,27,28,29,30,31,32],"stratus-red-team","adversary-emulation","cloud-security","detection-validation","purple-team","aws","mitre-attack","threat-detection","mahipal","cybersecurity","1.0",[37],"DE.CM-01",[39],"T1078","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":58},[48,51,54],{"tool":49,"command":50},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill emulating-cloud-attacks-with-stratus-red-team",{"tool":52,"command":53},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill emulating-cloud-attacks-with-stratus-red-team",{"tool":55,"command":56},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill emulating-cloud-attacks-with-stratus-red-team","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002FSKILL.md",true,[60,64,70,74],{"path":61,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fapi-reference.md","REFERENCE","参考文档",2429,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002Freferences\u002Fapi-reference.md",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fstandards.md",1252,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002Freferences\u002Fstandards.md",{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"scripts\u002Fagent.py","SCRIPT","脚本",5196,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Femulating-cloud-attacks-with-stratus-red-team\u002Fscripts\u002Fagent.py",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]