Back to catalog
Static reviewDevelopment

Skill dossier

performing-cloud-incident-containment-procedures

Source declaration

Execute cloud-native incident containment across AWS, Azure, and GCP using platform CLIs to revoke or disable compromised IAM credentials, isolate resources with security groups and network ACLs, and preserve forensic evidence via snapshots. Use when responding to a cloud security incident that requires stopping lateral movement while keeping evidence intact for later investigation.

The author's original description, preserved in English. It describes intent, not verified performance.

Execute cloud-native incident containment across AWS, Azure, and GCP using platform CLIs to revoke or disable compromised IAM credentials, isolate resources with security groups and network ACLs, and preserve forensic evidence via snapshots. Use when responding to a cloud security incident that requires stopping lateral movement while keeping evidence intact for later investigation.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Execute cloud-native incident containment across AWS, Azure, and GCP using platform CLIs to revoke or disable compromised IAM credentials, isolate resources with security groups and network ACLs, and preserve forensic evidence via snapshots. Use when responding to a cloud security incident that requires stopping lateral movement while keeping evidence intact for later investigation. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Performing Cloud Incident Containment Procedures [Source statement; provisional, not tested. Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L41]
  • AWS Containment Procedures [Source statement; provisional, not tested. Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L62]
  • Azure Containment Procedures [Source statement; provisional, not tested. Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L182]
  • GCP Containment Procedures [Source statement; provisional, not tested. Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L250]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L1-L39]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
57.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-cloud-incident-containment-procedures/assets/template.mdReference1.4 KB
skills/performing-cloud-incident-containment-procedures/LICENSEOther11 KB
skills/performing-cloud-incident-containment-procedures/references/api-reference.mdReference5.3 KB
skills/performing-cloud-incident-containment-procedures/references/standards.mdReference1.1 KB
skills/performing-cloud-incident-containment-procedures/references/workflows.mdReference2.5 KB
skills/performing-cloud-incident-containment-procedures/scripts/agent.pyScript12.4 KB
skills/performing-cloud-incident-containment-procedures/scripts/process.pyScript12.5 KB
skills/performing-cloud-incident-containment-procedures/SKILL.mdInstruction10.9 KB

SKILL.md frontmatter

{
  "name": "performing-cloud-incident-containment-procedures",
  "description": "Execute cloud-native incident containment across AWS, Azure, and GCP using platform CLIs to revoke or disable compromised IAM credentials, isolate resources with security groups and network ACLs, and preserve forensic evidence via snapshots. Use when responding to a cloud security incident that requires stopping lateral movement while keeping evidence intact for later investigation.",
  "domain": "cybersecurity",
  "subdomain": "incident-response",
  "tags": [
    "cloud-security",
    "incident-containment",
    "aws",
    "azure",
    "gcp",
    "cloud-forensics",
    "credential-revocation",
    "network-isolation"
  ],
  "mitre_attack": [
    "T1486",
    "T1490",
    "T1070",
    "T1078",
    "T1021"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "d3fend_techniques": [
    "Restore Access",
    "Password Authentication",
    "Biometric Authentication",
    "Strong Password Policy",
    "Restore User Account Access"
  ],
  "nist_csf": [
    "RS.MA-01",
    "RS.MA-02",
    "RS.AN-03",
    "RC.RP-01"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Performing Cloud Incident Containment Procedures

    Source-described action candidate under “Performing Cloud Incident Containment Procedures”; not verified execution.

  2. 02
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  3. 03
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  4. 04
    Action

    AWS Containment Procedures

    Source-described action candidate under “AWS Containment Procedures”; not verified execution.

  5. 05
    Action

    Azure Containment Procedures

    Source-described action candidate under “Azure Containment Procedures”; not verified execution.

  6. 06
    Action

    GCP Containment Procedures

    Source-described action candidate under “GCP Containment Procedures”; not verified execution.

Inspect all extracted workflow candidates (14 candidate steps)
  1. 07
    Action

    Evidence Preservation Best Practices

    Source-described action candidate under “Evidence Preservation Best Practices”; not verified execution.

  2. 08
    Action

    Always snapshot before containment - Create disk/volume snapshots before network isolation

    Source-described action candidate under “Evidence Preservation Best Practices”; not verified execution.

  3. 09
    Output

    Preserve CloudTrail/Activity Logs - Copy logs to write-protected storage

    Source-described output candidate under “Evidence Preservation Best Practices”; not verified execution.

  4. 10
    Action

    Document all actions - Timestamp every containment step taken

    Source-described action candidate under “Evidence Preservation Best Practices”; not verified execution.

  5. 11
    Action

    Use break-glass procedures - Pre-establish emergency access for IR team

    Source-described action candidate under “Evidence Preservation Best Practices”; not verified execution.

  6. 12
    Action

    Maintain forensic chain of custody - Hash all evidence artifacts

    Source-described action candidate under “Evidence Preservation Best Practices”; not verified execution.

  7. 13
    Action

    MITRE ATT&CK Cloud Techniques

    Source-described action candidate under “MITRE ATT&CK Cloud Techniques”; not verified execution.

  8. 14
    Action

    References

    Source-described action candidate under “References”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

19 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Medium

Network access is mentioned

10 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 10 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

2 occurrences

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

7 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/performing-cloud-incident-containment-procedures/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/performing-cloud-incident-containment-procedures/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/performing-cloud-incident-containment-procedures
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.