maxtac-cloud-runtime-boundary

You can analyze cloud runtime boundaries for SSRF, HTTP request influence, container control, pod control, and metadata services using this skill to evaluate security configurations across AWS, Azure, GCP, and managed Kubernetes environments.

A cloud runtime boundary defines the security perimeter around compute, serverless, and container workloads. You need to check it when evaluating runtime-to-cloud privilege paths, network perimeters, and workload identity configurations to prevent unauthorized access.

You can check AWS IMDS, Azure managed identities, and GCP firewall rules by applying provider-specific configurations and security checks to identify vulnerabilities in metadata services and network perimeters.

Yes, you can validate managed Kubernetes configurations, service accounts, and workload identity setups to ensure runtime boundary security and prevent unauthorized container or pod control.

Yes, cloud provider-specific configurations and security checks must already be in place for the analysis to evaluate HTTP request influence, SSRF, container control, pod control, and metadata service risks accurately.

You can use the proof hygiene checks in this skill to ensure that sensitive data like credentials and tokens are not stored or transmitted insecurely across your cloud runtime boundaries.