openskills.info
← All skills

Skill map

Cloud security

Applies identity, least privilege, workload protection, and policy controls. As Cloud Engineer needs it.

HOWTOs

Concrete operational procedures from the courses on this page.

  • How to contain a leaked cloud access key or compromised cloud identity

    not executable: Needs a live cloud account (AWS, Microsoft Entra, or Google Cloud) where the leaked key or compromised identity still exists, with pre-incident audit logs and a break-glass responder principal that can disable credentials and revoke sessions. No runner in the fleet holds a tenant under an active credential incident, and a local emulator cannot prove real disable, session revoke, or persistence cleanup against a provider control plane, so nothing here is executed.

    Disabling the credential, revoking the temporary sessions it already started, and scoping the principals, identity providers, and resources an attacker may have created for persistence, across AWS, Microsoft Entra, and Google Cloud.

    Cloud Security

  • How to scope and contain a compromised cloud compute instance

    not executable: Needs a live cloud account with a running compute instance under investigation (EC2, Azure VM, or Compute Engine), same-region forensics capacity for memory and disk capture, and authority to isolate the instance and revoke its cloud credentials without destroying evidence. No runner in the fleet hosts that incident context, and a local VM cannot prove provider network isolation or instance-role session revoke, so nothing here is executed.

    Isolating one compromised virtual machine without destroying evidence: the order of memory capture, disk snapshots, network isolation, and revoking the instance's own cloud credentials, then rebuilding from a known-good image rather than cleaning in place.

    Cloud Security