# Linux, cloud e containers

> Hosts Linux e macOS, Docker e Kubernetes, AWS, Azure, GCP, IaC e CI/CD.

Auditoria de privilégios e capabilities, revisão de containers e SBOM, RBAC e network policy no Kubernetes, IAM e exposição na nuvem, Terraform, object storage e GitHub Actions.

abusing-shadow-credentials-for-privesc: Take over Active Directory accounts by writing attacker-controlled public keys to msDS-KeyCredentialLink (Shadow Credentials) with pyWhisker, Whisker, or Certipy, then authenticate via PKINIT to recover the target's NT hash without a password reset. Use when BloodHound shows GenericWrite/GenericAll/

analyzing-azure-activity-logs-for-threats: Queries Azure Monitor activity logs and sign-in logs via azure-monitor-query

analyzing-cloud-storage-access-patterns: Detect abnormal access in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics for after-hours bulk downloads, new-IP access, and API-call spikes (e.g. GetObject) via statistical baselines and time-series anomaly detection. Use when inv

analyzing-docker-container-forensics: Investigate compromised Docker containers by analyzing images, layers,

analyzing-linux-kernel-rootkits: Detect kernel-level rootkits in Linux memory dumps using Volatility3

analyzing-linux-system-artifacts: Examine Linux system artifacts (auth logs, cron/systemd persistence,

analyzing-malicious-iso-and-container-files: Analyzes malicious ISO, IMG, VHD, and similar container files used to smuggle payloads

analyzing-malicious-vbscript-and-wsf: Analyzes malicious VBScript, WSF, and HTA scripts: parsing WSF/HTA containers,

analyzing-persistence-mechanisms-in-linux: Scan Linux systems for persistence mechanisms including crontab/systemd entries, LD_PRELOAD injection, shell profile modifications (.bashrc, .profile), and SSH authorized_keys backdoors, then correlate findings with auditd logs into an installation timeline. Use during incident response or threat hu

auditing-aws-s3-bucket-permissions: Systematically audit AWS S3 bucket permissions to identify publicly

auditing-cloud-with-cis-benchmarks: Audit AWS, Azure, and GCP environments against the CIS Foundations Benchmarks by running automated scans with tools like Prowler and ScoutSuite, interpreting failed controls, and tracking remediation for continuous compliance. Use when conducting a cloud security audit, validating CIS benchmark comp

auditing-gcp-iam-permissions: Auditing Google Cloud Platform IAM permissions to identify overly permissive

aws-cli: Auth/lab ref: AWS CLI v2 for interacting with AWS services from the terminal.

aws-security-review: Audit AWS environments for IAM privilege escalation, exposed resources, logging gaps, and misconfigurations across accounts. Use for cloud security assessments and hardening reviews.

benchmarking-kubernetes-with-kube-bench: Installs and runs the kube-bench tool against a Kubernetes cluster as a Job, DaemonSet, or standalone binary, selecting the correct benchmark version and targets (control plane, etcd, kubelet, worker nodes) and emitting JSON or JUnit output for pipelines. Use when setting kube-bench up for the first

building-cloud-siem-with-sentinel: Deploy Microsoft Sentinel as a cloud-native SIEM/SOAR by configuring multi-cloud data connectors (AWS, Azure, GCP), writing KQL detection and hunting queries, and building automated Logic Apps response playbooks. Use when establishing a centralized SOC for multi-cloud environments, migrating from a

building-devsecops-pipeline-with-gitlab-ci: Configure a GitLab CI/CD pipeline that embeds SAST (Semgrep, SpotBugs, Gosec, Bandit, NodeJsScan), DAST, container scanning, dependency scanning, and secret detection via GitLab's managed security templates. Use when building a shift-left DevSecOps pipeline in GitLab, adding automated vulnerability

building-threat-feed-aggregation-with-misp: Deploy MISP via Docker and configure feeds from sources like abuse.ch, AlienVault OTX, and CIRCL to aggregate, correlate, and distribute threat intelligence, including automated feed synchronization and STIX/TAXII-based integration with Splunk, Elasticsearch, and SOAR platforms. Use when standing up

cicd-technique: CI/CD supply chain methodology: identifying poisoned pipelines, unsafe GitHub Actions, and extracting build secrets.

cloud-azure: Attack Azure / Entra ID — managed-identity token theft, Entra (Azure AD) role abuse, and app/ storage misconfig. Load when the target is on Azure, you hold Azure creds/a token, or see Entra/AAD/azurewebsites/blob.core.windows.net. Signals: 169.254.169.254 IMDS, Managed Identity, az cli, Entra roles,

cloud-container-escape: Break out of a container to the host. Load when you have a shell in a container/pod and want the node: privileged container, mounted docker.sock, dangerous capabilities, hostPath, or "escape the container". Signals: /.dockerenv, cgroup shows docker/k8s, CAP_SYS_ADMIN, mounted socket.

cloud-ctf: Lab/CTF: cloud security challenges; AWS/GCP/Azure creds, buckets, IAM, metadata, KMS/secrets, snapshots, object versions, identity chains.

cloud-docker-api-abuse: Turn an exposed container daemon or an over-privileged container into host compromise — a Docker API on 2375/2376, a mounted docker.sock, or a privileged/`-v /:/host` container. Load when you find an open Docker/containerd socket, port 2375/2376, a container you can run images in, or you landed insi

cloud-docker-registry: Find and loot exposed container registries — image pull/push, secrets baked in layers, and registry misconfig. Load on exposed Docker registry (port 5000, /v2/), a registry URL, harbor/ECR/ GCR/ACR references, or "container registry". Signals: /v2/_catalog, registry:2, unauth pull/push.

cloud-gcp: Attack Google Cloud Platform — metadata/SA token theft, IAM privilege escalation, and storage/ function misconfig. Load when the target runs on GCP, you hold a GCP SA key/token, or see gcp/gcloud/GCE/GKE/appspot. Signals: metadata.google.internal, service-account.json, storage.googleapis.com, cloudf

cloud-iam-privesc: Escalate privileges in cloud IAM (AWS/GCP/Azure) from a low-priv set of credentials. Load when you hold cloud creds/keys/a role and want higher privilege or new resources. Signals: leaked AWS keys, an assumed role, a service-account token, "escalate in AWS/GCP/Azure", enumerated permissions.

cloud-imds-ssrf: Escalate SSRF to cloud credential theft via the instance metadata service (IMDS). Load when SSRF is confirmed AND the target runs on AWS/GCP/Azure. Signals: 169.254.169.254 reachable, cloud-hosted app, SSRF that can set arbitrary Host/headers, "metadata".

cloud-k8s: Use for authorized cloud, container, and Kubernetes security assessment including metadata SSRF, IAM misconfig, container escape paths, and cluster RBAC review.

cloud-kubernetes: Attack exposed Kubernetes: API server, kubelet, etcd, dashboards, and RBAC. Load on k8s signals — ports 6443/10250/2379/8443, /api/v1, kube-dns, a pod foothold, or "kubernetes/k8s". Signals: kubectl, service-account tokens, exposed dashboard, container in a cluster.

cloud-s3-exposure: Find and prove misconfigured cloud object storage (S3/GCS/Azure Blob). Load when assets load from *.s3.amazonaws.com, storage.googleapis.com, *.blob.core.windows.net, bucket-looking hostnames, or "bucket". Signals: public-read/list, unauthenticated writes, predictable bucket names.

cloud-security-technique: Auth assessment: cloud security methodology; AWS/Azure/GCP IAM, storage, metadata, containers, serverless, workload identity, evidence routing.

code-review-iac: Security review of infrastructure-as-code — Terraform, CloudFormation, Ansible, Kubernetes/Helm manifests. Load when reviewing IaC in a repo/PR, on .tf/.yaml/.yml infra files, or "review our Terraform". Signals: *.tf, cloudformation/*.yaml, playbooks, k8s manifests, Helm charts, module registries.

competition-agent-cloud: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AI-agent, prompt-injection, MCP or toolchain, cloud, container, CI/CD, and supply-chain challenges. Use when the user asks to analyze prompt-to-tool flows, retrieval poisoning, mounted secrets, deployment drift, runtime

competition-cloud-metadata-path: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for cloud metadata services, instance identity, workload identity, link-local credential paths, role assumption, and metadata-to-privilege trust edges. Use when the user asks to inspect metadata-service access, instance cre

competition-container-runtime: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a m

competition-k8s-control-plane: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kubernetes API analysis, service-account trust, RBAC edges, admission and controller behavior, cluster secrets, workload mutation, and namespace-scoped drift. Use when the user asks to inspect kube API permissions, serv

competition-kernel-container-escape: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for kernel attack surface, namespace and cgroup boundaries, container isolation assumptions, syscall paths, and escape primitive verification. Use when the user asks to analyze container-to-host escape paths, kernel exploit

competition-linux-credential-pivot: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Linux credential artifacts, service tokens, SSH material, cloud and container secrets, socket-level trust, and host-to-host pivot chains. Use when the user asks to trace Linux auth artifacts, accepted token or key repla

conducting-cloud-incident-response: Respond to security incidents in AWS, Azure, and GCP via identity-based containment, cloud-native log analysis (CloudTrail, Azure Activity Logs, GCP Audit Logs), resource isolation, and forensic evidence acquisition adapted for ephemeral cloud infrastructure. Use when CSPM alerts or audit logs show

conducting-cloud-penetration-testing: This skill outlines methodologies for performing authorized penetration

configuring-aws-verified-access-for-ztna: Configure AWS Verified Access to provide VPN-less zero trust network

container-image-hardening: Harden Dockerfiles and container images — multi-stage builds, non-root users, minimal base images, and vulnerability gates. Use when building production containers or reviewing Dockerfiles.

container-technique: Container methodology: Identifying containerization limits, Docker/K8s misconfigurations, and executing escapes to the host node.

c-patterns: C language patterns and best practices for safe, maintainable C: ownership, API contracts, error handling, integer safety, portability, and concurrency boundaries. Use when writing or reviewing C code (C11+), designing module interfaces, refactoring legacy C, or hardening low-level code paths.

defense-cloud-detection: Detect and respond to attacks in cloud control planes — credential abuse, IMDS theft, persistence, and privilege escalation — from audit logs. Load for "detect cloud attacks", "CloudTrail/GuardDuty", "someone used our keys", AWS/Azure/GCP monitoring, or cloud IR. The defensive counterpart to the clo

defense-hardening-baseline: Turn offensive findings into concrete hardening — the fix side of each vuln class, plus config baselines. Load for blue-team/remediation tasks, "how do we fix/prevent", secure config review, or writing the remediation section of a report. Signals: "harden", "remediation", "secure baseline", "prevent

deploying-cloud-deception-with-decoy-resources: Deploy cloud-native deception across AWS, Azure, and GCP using decoy (honey) resources whose only purpose is to generate a high-fidelity alert the instant an attacker touches them: canary IAM access keys, permission-less decoy users/roles/service principals, honey object-storage buckets, and decoy s

detecting-aws-cloudtrail-anomalies: Detect unusual API call patterns in AWS CloudTrail logs using boto3,

detecting-aws-credential-exposure-with-trufflehog: Scan source code repositories, CI/CD pipelines, and configuration files

detecting-aws-guardduty-findings-automation: Build automated AWS GuardDuty finding response pipelines using EventBridge

detecting-aws-iam-privilege-escalation: Detect AWS IAM privilege escalation paths using boto3 and Cloudsplaining

detecting-azure-lateral-movement: Detect lateral movement in Azure AD/Entra ID environments using Microsoft

detecting-azure-service-principal-abuse: Detect Azure service principal abuse in Microsoft Entra ID using KQL detection

detecting-azure-storage-account-misconfigurations: Audit Azure Blob and ADLS storage accounts for public access exposure, weak

detecting-cloud-threats-with-guardduty: Deploy and operationalize Amazon GuardDuty, covering protection plans

detecting-compromised-cloud-credentials: Detect compromised cloud credentials across AWS, Azure, and GCP by analyzing

detecting-container-drift-at-runtime: Detects unauthorized runtime drift in containers by monitoring binary execution, filesystem changes, and configuration deviation from the original immutable image, using Falco and Microsoft Defender for Containers. Use when validating immutable-infrastructure controls, hunting for unexpected package

detecting-container-escape-attempts: Detects container escape at runtime across tooling - namespace manipulation, capability abuse, kernel exploits, sensitive host mounts, and anomalous syscalls - and explains which signals matter regardless of whether Falco, Sysdig, auditd, or an EDR is doing the collection. Use when deciding what bre

detecting-container-escape-with-falco-rules: Writes and tunes Falco rule syntax for container escape detection - conditions, macros, lists, priorities, and output fields - covering host filesystem mounts, sensitive host path access, kernel module loading, and privileged capability abuse, including how to drive down false positives. Use when au

detecting-container-runtime-threats-with-falco: Deploys and operates Falco with the modern eBPF driver in Kubernetes and Docker, covering driver selection, Helm installation, output channels, and the built-in ruleset that detects container escape, namespace abuse, privileged mounts, and anomalous syscalls. Use when standing Falco up on a cluster,

detecting-cryptomining-in-cloud: This skill teaches security teams how to detect and respond to unauthorized

detecting-misconfigured-azure-storage: Audit Azure Storage accounts for public blob containers, missing encryption, overly permissive SAS tokens, disabled logging, and network access violations using Azure CLI, PowerShell, and Microsoft Defender for Storage. Use for storage security audits across subscriptions, responding to Defender for

detecting-privilege-escalation-in-kubernetes-pods: Detects and prevents privilege escalation inside Kubernetes pods by combining admission control (OPA policies), runtime monitoring (Falco), and audit log analysis of security contexts, Linux capabilities, and syscall patterns. Use when investigating a pod running as root or privileged, hardening wor

detecting-s3-data-exfiltration-attempts: Detecting data exfiltration attempts from AWS S3 buckets by analyzing

detecting-shadow-it-cloud-usage: Detect unauthorized SaaS and cloud service usage (shadow IT) by parsing

detecting-supply-chain-attacks-in-ci-cd: Scans GitHub Actions workflows and CI/CD pipeline configurations for

devcontainer-setup: Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes. Use when adding devcontainer support to a project, setting up isolated development environments, or configuring sandboxed Claude Code workspaces.

emulating-cloud-attacks-with-stratus-red-team: Install and run Stratus Red Team to detonate granular, MITRE ATT&CK-mapped

escaping-containers-to-host: Exploits privileged pods, host mounts, runC CVEs, and exposed Docker sockets to break out of a container and reach the underlying host during an authorized container-security assessment. Use when executing an approved breakout test, demonstrating the real impact of a privileged or hostPath workload,

exploiting-aws-with-pacu: Runs the Pacu AWS exploitation framework end-to-end — session and credential setup, IAM enumeration, automated privilege-escalation scanning via iam__privesc_scan, and persistence/backdooring modules like iam__backdoor_users_keys. Use for authorized AWS penetration tests or red-team engagements, ass

gcloud-cli: Auth/lab ref: Google Cloud CLI for authenticating, configuring projects, and enumerating GCP resources from the terminal.

hardening-docker-containers-for-production: Hardens Dockerfiles, images, and per-container runtime settings against the CIS Docker Benchmark v1.8.0: non-root users, dropped capabilities, read-only root filesystem, seccomp and AppArmor profiles, and minimal multi-stage builds, validated with docker-bench-security, Hadolint, and Dockle. Use whe

hardening-docker-daemon-configuration: Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc, no-new-privileges, and live-restore. Use when securing a Docker host's daemon to prevent privilege escalation

hardening-linux-endpoint-with-cis-benchmark: Hardens Linux endpoints using CIS Benchmark recommendations for Ubuntu,

hunting-for-living-off-the-cloud-techniques: Hunts for adversary abuse of legitimate cloud services (Azure, AWS, GCP,

hunting-persistence-on-linux: Hunts for Linux persistence by inspecting cron, systemd units, shell rc files, SSH

implementing-aqua-security-for-container-scanning: Deploy Aqua Security's Trivy scanner to detect vulnerabilities, misconfigurations,

implementing-aws-config-rules-for-compliance: Implements AWS Config managed and custom rules for continuous compliance

implementing-aws-iam-permission-boundaries: Configures AWS IAM permission boundaries that cap the maximum permissions

implementing-aws-macie-for-data-classification: Enable and configure Amazon Macie via AWS CLI/Terraform to discover, classify, and protect sensitive data (PII, financial data, credentials) in S3 using ML and pattern matching, including discovery jobs, custom data identifiers, allow lists, and EventBridge-based remediation. Use when setting up S3

implementing-aws-nitro-enclave-security: Build AWS Nitro Enclave confidential computing environments using nitro-cli

implementing-aws-security-hub: Deploy AWS Security Hub as a centralized CSPM platform, backed by AWS

implementing-aws-security-hub-compliance: Deploy AWS Security Hub, backed by AWS Config, to aggregate findings

implementing-azure-defender-for-cloud: Enable Microsoft Defender for Cloud (CSPM + CWPP) across VMs, containers,

implementing-beyondcorp-zero-trust-access-model: Implement Google''s BeyondCorp zero trust access model using Cloud

implementing-cloud-dlp-for-data-protection: Implement cloud DLP using Amazon Macie, Google Cloud DLP API, Microsoft

implementing-cloud-security-posture-management: Continuously monitor multi-cloud environments (AWS, Azure, GCP) for

implementing-cloud-trail-log-analysis: Implementing AWS CloudTrail log analysis for security monitoring, threat

implementing-cloud-vulnerability-posture-management: Implement multi-cloud CSPM to detect cloud-native misconfigurations

implementing-cloud-waf-rules: Deploys and tunes Web Application Firewall rules on AWS WAF, Azure WAF,

implementing-cloud-workload-protection: Implements cloud workload protection using boto3 and google-cloud APIs

implementing-container-image-minimal-base-with-distroless: Reduces container attack surface by building application images on Google distroless base images that ship only the application runtime - no shell, package manager, or OS utilities - using multi-stage build patterns plus debugging and scanning techniques adapted to distroless. Use when hardening con

implementing-devsecops-security-scanning: Integrates SAST, DAST, and SCA into CI/CD pipelines using Semgrep for

implementing-envelope-encryption-with-aws-kms: Implements envelope encryption with AWS KMS, encrypting data locally with a data encryption key (DEK) and protecting that DEK with a KMS-managed key (KEK), covering the encrypt/decrypt flow, KMS key types, and security validation criteria. Use when designing key management for encrypting large or nu

implementing-file-integrity-monitoring-with-aide: Configures AIDE (Advanced Intrusion Detection Environment) for file integrity monitoring on Linux, covering baseline database creation, scheduled integrity checks via cron, change detection, and alerting on unauthorized modifications. Use when setting up host-based file integrity monitoring, detecti

implementing-gcp-binary-authorization: Implements GCP Binary Authorization end to end, including creating KMS-backed attestors, Container Analysis notes, deploy-time policies, and signing image attestations, so that only trusted, verified images deploy to GKE and Cloud Run. Use when enforcing container supply-chain integrity or deploy-ti

implementing-gcp-organization-policy-constraints: Implements GCP Organization Policy constraints via gcloud and Terraform, such as restricting external IPs, resource locations, default service accounts, and service account keys, plus dry-run testing of policy impact before enforcement. Use when enforcing security guardrails across an org's resource

implementing-honeytokens-for-breach-detection: Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries,

implementing-image-provenance-verification-with-cosign: Signs and verifies container image provenance with Sigstore Cosign, covering key-based and keyless OIDC signing (Fulcio, Rekor transparency log), SLSA attestations, and enforcing signature verification through Kubernetes admission control. Use when signing images for supply chain security, setting u

implementing-kubernetes-network-policy-with-calico: Installs Calico as the cluster CNI and writes standard Kubernetes NetworkPolicy under it, covering default-deny baselines, policy ordering and precedence, service-account-based selectors, and verifying that policy is genuinely being enforced. Use when adopting Calico as the enforcement CNI, establis

implementing-kubernetes-pod-security-standards: Chooses and applies the correct Kubernetes Pod Security Standard (Privileged, Baseline, Restricted) for a workload: what each profile forbids, how to map existing workloads to a profile, which securityContext fields must change, and how to plan a PodSecurityPolicy-to-PSS migration without breaking r

implementing-opa-gatekeeper-for-policy-enforcement: Deploys OPA Gatekeeper via Helm as a Kubernetes admission controller and writes ConstraintTemplates with Rego plus instantiated Constraints to validate, mutate, or deny resource requests at admission time. Use when enforcing custom policy-as-code at admission on Kubernetes v1.24+, blocking non-compl

implementing-rbac-hardening-for-kubernetes: Hardens Kubernetes RBAC by designing least-privilege Roles and ClusterRoles, auditing RoleBindings, eliminating cluster-admin sprawl, separating service accounts, and integrating an external OIDC identity provider. Use when tightening cluster access control, removing excessive ClusterRoleBindings, o

implementing-runtime-security-with-tetragon: Implements eBPF-based runtime observability and in-kernel enforcement in Kubernetes with Cilium Tetragon, monitoring process execution, file access, network connections, and syscalls, and blocking dangerous calls at the kernel level. Use when deploying Tetragon to detect or block syscalls such as pt

implementing-secrets-scanning-in-ci-cd: Integrate gitleaks and trufflehog into CI/CD pipelines to detect leaked

implementing-security-monitoring-with-datadog: Implements security monitoring using Datadog Cloud SIEM, Cloud Security

implementing-supply-chain-security-with-in-toto: Implements supply chain integrity verification for container builds with the in-toto framework: generating signing keys, defining a supply chain layout, recording pipeline steps as signed link metadata, verifying before deployment, enforcing at Kubernetes admission, and integrating with SLSA. Use wh

implementing-taxii-server-with-opentaxii: Deploy and configure a TAXII 2.1 server (Medallion) with Docker, publish

implementing-zero-standing-privilege-with-cyberark: Deploy CyberArk Secure Cloud Access (SCA) to eliminate standing privileges in AWS, Azure, and GCP by provisioning ephemeral, scoped roles on a just-in-time basis governed by the TEA framework (Time, Entitlements, Approvals). Use when designing or implementing zero standing privilege / just-in-time p

implementing-zero-trust-in-cloud: Guides zero trust implementation across AWS, Azure, and GCP per NIST SP 800-207 and BeyondCorp principles, covering identity-centric access, micro-segmentation, continuous verification, device trust assessment, and Identity-Aware Proxy deployment. Use when migrating from perimeter security to identi

kubernetes-security-audit: Audit Kubernetes clusters for RBAC excesses, pod security gaps, network policy holes, and supply-chain risks. Use when reviewing cluster configuration or hardening deployments.

linpeas: Auth/lab ref: LinPEAS Linux privilege review; weak permissions, services, env/config exposure, kernel hints, report triage.

linux-exploit-suggester: Auth/lab ref: Suggest Linux privilege escalation exploits based on kernel version and OS.

linux-internals-dev: Auth/lab dev: Linux internals; ELF loading and program startup, procfs, namespaces/caps, eBPF verifier/maps, LSM hooks for tooling/telemetry design.

linux-persistence: Auth/lab ref: Linux durability-risk audit; cron/systemd/SSH/PAM/LD_PRELOAD indicators, validation, cleanup and remediation notes.

managing-cloud-identity-with-okta: Implement Okta as a centralized cloud identity provider: configure SSO with AWS, Azure, and GCP, deploy phishing-resistant MFA with Okta FastPass, automate user provisioning/deprovisioning, and enforce adaptive access policies on device posture and risk signals. Use when standing up Okta SSO, rollin

mimipenguin: Auth/lab ref: Linux secret-exposure audit; process/memory artifact review for authorized recovery and defensive validation.

offensive-cicd-secrets: Comprehensive secrets extraction methodology targeting CI/CD environments across all major platforms. Covers environment variable extraction from build contexts, exploitation of vault and secrets-manager misconfigurations (HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, GCP Secret Manager), r

offensive-cloud: Cloud security attack methodology covering AWS, Azure, and GCP. Includes credential harvesting (IMDS, ~/.aws, env vars, leaked CI secrets, instance roles), enumeration with cloud-specific tools (pacu, ScoutSuite, Prowler, ROADtools, gcp_enum), privilege escalation paths (IAM PassRole, AssumeRole cha

offensive-container-escape: Container escape and breakout techniques targeting Docker, containerd, and Podman runtimes. Covers privileged container breakout via host filesystem mount and nsenter, Docker socket abuse through /var/run/docker.sock, Linux capability exploitation including CAP_SYS_ADMIN, CAP_SYS_PTRACE, and CAP_NET

offensive-data-exfiltration: Dense methodology covering DNS exfiltration (dnscat2, iodine, dns2tcp), HTTPS tunneling (domain fronting, CDN abuse, legitimate service channels), ICMP tunneling (icmpsh, ptunnel-ng), cloud storage dead drops (S3 presigned URLs, Azure Blob SAS tokens, GCS signed URLs), email-based exfil (SMTP, EWS,

offensive-k8s-attacks: Kubernetes cluster attack techniques covering the full attack lifecycle from initial foothold in a pod to cluster-wide compromise. Covers service account token theft and impersonation, RBAC misconfiguration exploitation including wildcard permissions and privilege escalation via role binding, direct

offensive-linux-privesc: Comprehensive Linux privilege escalation methodology for offensive security engagements. Covers the full attack surface from a low-privilege shell to root: SUID/SGID binary abuse via GTFOBins, Linux capabilities exploitation (cap_setuid, cap_dac_override, cap_dac_read_search), sudo misconfigurations

offensive-windows-privesc: Comprehensive Windows privilege escalation methodology for offensive security engagements. Covers the full attack surface from a standard user shell to NT AUTHORITY\\SYSTEM: token impersonation via SeImpersonate and SeAssignPrimaryToken privileges using JuicyPotato, PrintSpoofer, GodPotato, SweetPot

osv-scanner: Scan dependency manifests, lockfiles, SBOMs, and container images with OSV-Scanner; interpret package findings and call-analysis coverage.

performing-aws-account-enumeration-with-scout-suite: Run the agentless, open-source ScoutSuite tool (via pip install and the `scout` CLI)

performing-aws-privilege-escalation-assessment: Performing authorized privilege escalation assessments in AWS environments

performing-cloud-asset-inventory-with-cartography: Run Cartography to sync AWS, GCP, or Azure resources into a Neo4j graph database,

performing-cloud-forensics-investigation: Collect and analyze cloud forensic evidence using AWS CLI, Azure CLI, or gcloud

performing-cloud-forensics-with-aws-cloudtrail: Investigate AWS account compromise by querying CloudTrail with boto3's LookupEvents

performing-cloud-incident-containment-procedures: Execute cloud-native incident containment across AWS, Azure, and GCP using platform

performing-cloud-native-forensics-with-falco: Uses Falco YAML rules for runtime threat detection in containers and

performing-cloud-native-threat-hunting-with-aws-detective: Investigate AWS security incidents using Amazon Detective's behavior graphs,

performing-cloud-penetration-testing-with-pacu: Run authorized AWS penetration tests with Pacu, the open-source AWS exploitation

performing-cloud-storage-forensic-acquisition: Perform forensic acquisition of cloud storage services including Google

performing-container-escape-detection: Audits container and pod configuration for escape-enabling misconfiguration using the Kubernetes Python client - privileged flags, dangerous capability grants, host path mounts, shared namespaces, and CVE-2022-0492 style cgroup abuse. Use when sweeping a cluster for workloads that could break out, p

performing-container-image-hardening: Harden container images by minimizing attack surface, stripping unnecessary

performing-container-security-scanning-with-trivy: Runs Trivy across every target type it supports - container images, filesystems, Git repositories, and Kubernetes clusters - for OS and dependency vulnerabilities, IaC misconfiguration, exposed secrets, and licences, generating CycloneDX or SPDX SBOMs. Use when integrating Trivy into CI/CD, deployin

performing-docker-bench-security-assessment: Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across host configuration, daemon settings, images, and runtime configuration, then interprets pass/fail/warn output and remediates the common failures. Use when auditing Docker hosts for CIS compliance, scheduling re

performing-gcp-penetration-testing-with-gcpbucketbrute: Performs authorized GCP security testing using GCPBucketBrute to enumerate

performing-gcp-security-assessment-with-forseti: Performing comprehensive security assessments of Google Cloud Platform

performing-kubernetes-cis-benchmark-with-kube-bench: Turns kube-bench output into a finished CIS Kubernetes Benchmark audit: interpreting PASS/FAIL/WARN per control, judging which failures are genuine on a managed cluster, writing remediation, and packaging evidence for SOC 2 or PCI DSS. Use when conducting a scheduled compliance audit, triaging kube-

performing-kubernetes-etcd-security-assessment: Assesses the security posture of the etcd cluster backing Kubernetes: encryption at rest, TLS peer and client transport, access control, backup encryption, and network isolation. Use when auditing or hardening a control plane, reviewing whether Secrets are encrypted at rest, or protecting etcd backu

performing-kubernetes-penetration-testing: Evaluates Kubernetes cluster security by actively simulating attacker techniques against the API server, kubelet, etcd, pods, RBAC, network policy, and secrets, using kube-hunter, Kubescape, peirates, and manual kubectl exploitation to find paths to cluster compromise. Use for an authorized penetrat

performing-privilege-escalation-on-linux: Guides manual enumeration and automated tooling to escalate from a low-privilege

performing-serverless-function-security-review: Performing security reviews of serverless functions across AWS Lambda,

performing-vlan-hopping-attack: Simulates VLAN hopping attacks using switch spoofing and 802.1Q double tagging techniques in authorized lab environments to test VLAN segmentation effectiveness and switch port security. Use during an authorized penetration test to validate trunk port hardening, confirm DTP is disabled on access por

privesc-arsenal: One line: Linux + Windows local privilege-escalation tool arsenal for authorized engagements. Trigger signals: "privesc", "got a shell", "escalate", "root", "SYSTEM", initial access gained but not root. Authorized, in-scope targets only.

privesc-enumeration: Systematic post-foothold host enumeration and credential/loot hunting on Linux and Windows — build situational awareness and find the lead that escalates or moves laterally. Load the moment you land a shell and think "now what?". Signals: fresh foothold, low-priv user, "enumerate the box", "situatio

privesc-linux-gtfobins: Linux privilege escalation via sudo rules, SUID/SGID binaries, and capabilities using GTFOBins techniques. Load with a Linux shell needing root, on `sudo -l` output, SUID/`getcap` findings, or "escalate on Linux". Signals: allowed sudo commands, SUID binaries, file capabilities, cron/PATH abuse.

pspy: Observe short-lived Linux processes and filesystem activity without root. Use to correlate scheduled jobs, process arguments, and timestamps.

pwncat: Auth/lab ref: pwncat-cs Linux session management; listener/connect modes, shell stabilization, module enum, tunnel and cleanup workflow.

recon-cloud-assets: Discover an organization's cloud footprint — buckets, blobs, apps, IP ranges, and services across AWS/GCP/Azure. Load during recon on a company target, on "cloud recon", finding storage/assets, or before cloud testing. Signals: an org name/domain in scope, assets on cloud CDNs, wildcard program.

remediating-s3-bucket-misconfiguration: Provides step-by-step procedures for remediating Amazon S3 bucket

scanning-container-images-with-grype: Scans container images, filesystems, and SBOMs for known CVEs with Anchore Grype, matching Syft-generated SBOM packages against NVD, GitHub Advisories, and OS-specific feeds with configurable severity thresholds and failure gates. Use when Grype or Syft is the chosen toolchain, when scanning an exis

scanning-containers-with-trivy-in-cicd: Integrates Aqua Security''s Trivy scanner into CI/CD pipelines to detect

scanning-docker-images-with-trivy: Scans a Docker image with Trivy for vulnerabilities in OS packages and language dependencies, misconfiguration, exposed secrets, and licence violations, emitting SARIF, CycloneDX, or SPDX output. Use when scanning or gating a specific image, wiring an image scan into CI/CD, or checking an image duri

scanning-iac-and-images-with-trivy: Scans container images, Infrastructure-as-Code (Terraform, CloudFormation,

scanning-kubernetes-manifests-with-kubesec: Scores Kubernetes resource manifests with Kubesec to flag misconfiguration and privilege-escalation risk before deployment, mapping each finding back to the securityContext change that fixes it. Use when gating manifests in CI, reviewing YAML or a rendered chart before it reaches a cluster, or expla

securing-api-gateway-with-aws-waf: Secures AWS API Gateway endpoints with AWS WAF by configuring managed

securing-aws-iam-permissions: Hardens AWS IAM configurations to enforce least-privilege access, covering

securing-aws-lambda-execution-roles: Hardens AWS Lambda execution roles by writing least-privilege IAM policies,

securing-azure-with-microsoft-defender: Deploys and configures Microsoft Defender for Cloud as a CNAPP for

securing-container-registry-images: Secures container registry images (ECR, ACR, GCR, Docker Hub) by scanning

securing-container-registry-with-harbor: Configures the security features of the Harbor open-source container registry - integrated Trivy scanning, Cosign and Notary content trust policies, project-level RBAC, immutable tag and retention rules, and OIDC authentication - to enforce provenance and block deployment of vulnerable images. Use w

securing-helm-chart-deployments: Secures Helm chart deployments by verifying chart signatures and provenance, rendering and linting templates for misconfiguration, enforcing pod security contexts through values.yaml, moving secrets into an external store instead of Helm values, and scoping RBAC for Helm operations in CI/CD. Use whe

securing-kubernetes-on-cloud: Hardens managed Kubernetes clusters on EKS, AKS, and GKE by implementing

securing-serverless-functions: Hardens serverless compute platforms (AWS Lambda, Azure Functions, Google

supply-chain-security: Use for software supply-chain security assessment covering SBOM, SCA, CI/CD pipelines, container images, build integrity, dependency provenance, and vulnerability reachability.

trivy: Auth/lab ref: broad vulnerability scanner for containers, filesystems, repos, IaC, and SBOMs.

trufflehog: Auth/lab ref: TruffleHog secret scanning; verified secret types, git/cloud/CI sources, validation evidence, remediation workflow.

Canonical: https://notholy.com/pt-br/skills/category/cloud-containers
