Agent skill · security · jeremylongshore
castai-security-basics
Review CAST AI identity, Kubernetes RBAC, cloud IAM, Kvisor, network, and evidence boundaries against enabled features. Use when preparing onboarding, automation expansion, or security-agent changes. Trigger with: "secure CAST AI", "audit CAST AI permissions", "review Kvisor access".
Why this skill is useful
Provides specific commands and procedures for securing CAST AI API keys and RBAC configurations that the AI wouldn't reliably generate on its own.
What it needs
Requires helm, kubectl installed locally. Requires castai account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CAST AI Least-Privilege Review Overview Review permissions against the components actually enabled. Distinguish observation, optimization, operator lifecycle, Kvisor telemetry, optional cluster proxy, and cloud-provider access instead of labeling the entire installation read-only or full-access. Prerequisites Selected umbrella-chart mode and optional features Rendered Helm resources, service accounts, RBAC, cloud IAM, and secret references Organization roles, API-key inventory, network policy, and data-classification rules Instructions Step 1: Establish feature scope Use Read and Grep to map read-only, Workload Autoscaler, Node Autoscaler, full, Kvisor options, reliability metrics, GPU or storage telemetry, operator management, and cluster proxy. Flag enabled components that lack a named business owner. Step 2: Review identity boundaries Separate human castctl login from service API keys. Verify organization role bindings, region, enterprise child targeting, storage, rotation, and revocation. Reject keys in values, URLs, Terraform output, logs, or support artifacts. Step 3: Review Kubernetes permissions Use Bash(helm:) to render the pinned installation and Bash(kubectl:) for bounded RBAC inspection. Compare each service account to current documented permissions. Account for agent deployment patching, operator lifecycle permissions, Kvisor cluster reads, optional scan jobs, and feature-gated token or pod-resize permissions. Step 4: Review cloud permissions Map each AWS, GCP, Azure, or other permission to monitoring, onboarding, automation, discovery, commitments, or storage telemetry. Do not reuse an automation role for read-only monitoring when the provider supports narrower access. Step 5: Review network and data paths Document regional egress, private connectivity, webhook destinations, telemetry classes, retention, and support-transfer controls. Do not invent a static IP allowlist or a broad 0.0.0.0/0 policy under the label of least privilege. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/castai-security-basics--3808b6