kubernetes-security-audit

Audit Kubernetes manifests for security vulnerabilities and misconfigurations.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill kubernetes-security-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubernetes-security-audit
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/kubernetes/security-audit
Command: npx skills add https://github.com/infraspecdev/tesseract --skill kubernetes-security-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds security misconfigurations in Kubernetes manifests that general-purpose review often misses, helping prevent privilege escalation, data exposure, and unsafe workload settings before deployment.

Core Features & Use Cases

  • RBAC Analysis: Reviews Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings for wildcard permissions, dangerous verbs, and overbroad access.
  • Pod and Workload Security: Checks Deployments, StatefulSets, DaemonSets, Jobs, CronJobs, and Pods for root execution, privilege escalation, host namespace access, and missing hardening settings.
  • Network, Secrets, and Image Review: Validates NetworkPolicies, secret handling, image pinning, service accounts, and Pod Security Standards, with EKS-specific checks when AWS-managed Kubernetes is present.
  • Use Case: A platform engineer can run this Skill against a Helm chart or manifest bundle to catch insecure RBAC, missing network isolation, and weak container security before merge.

Quick Start

Ask the Kubernetes security audit skill to review the attached manifests for RBAC, pod security, network policy, secret handling, and image risks.

Frequently Asked Questions about kubernetes-security-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Kubernetes manifests for security vulnerabilities before deployment?

To audit Kubernetes manifests for security vulnerabilities, you review Deployments, StatefulSets, and Pods for root execution, privilege escalation, and missing security context hardening before applying them to your cluster.

What RBAC misconfigurations should I look for in Kubernetes Roles and ClusterRoles?

When checking Kubernetes RBAC scope, you should look for wildcard permissions, dangerous verbs, and overbroad access in Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings to prevent privilege escalation.

Can I scan Helm charts and Kustomize overlays for pod security context issues?

Yes, you can scan Helm charts and Kustomize overlays to validate pod security context, verify service accounts, check image pinning, and ensure workloads meet Pod Security Standards before merge.

Does this security audit check EKS-specific identity and aws-auth settings?

Yes, when EKS-linked configurations are present in your Kubernetes manifests, the security audit performs EKS-specific checks for identity mappings and aws-auth settings to validate AWS-managed cluster permissions.

How do I validate NetworkPolicies and secret handling in k8s manifests?

To validate NetworkPolicies and secret handling in k8s manifests, you review network restrictions to ensure proper isolation and verify that secrets are managed safely without exposure across Deployments, StatefulSets, and DaemonSets.

What are the limitations of general-purpose review for Kubernetes security?

General-purpose review often misses Kubernetes security misconfigurations like unsafe workload settings, weak container security, and overbroad RBAC, which can lead to privilege escalation and data exposure if not audited specifically.