infra-rbac-audit

Auditing Kubernetes RBAC involves parsing role bindings to detect cluster-admin assignments, wildcard permissions, and over-permissive service accounts. This Skill identifies these misconfigurations to enforce least privilege and outputs a prioritized checklist of violations with remediation guidance.

Yes, you can check AWS IAM and GCP IAM policies for admin-equivalent roles. The audit reviews external access findings, flags overly broad owner/editor bindings, validates role last-used behavior, and identifies service account key usage to prevent over-privileged cloud access.

The best way to find excessive database and Airflow permissions is to audit PostgreSQL and Trino grants for dangerous roles like superuser or CREATEDB, and review Airflow RBAC to highlight users with administrative roles, ensuring least-privilege access across the data platform.

Yes, this RBAC audit supports compliance readiness for SOC2, GDPR, and PCI-DSS. It continuously verifies least-privilege access across data platform components, identifying misconfigured access control before it causes compliance incidents during pre-compliance reviews or quarterly access audits.

To run least-privilege verification across multiple data platforms, ask your agent to audit Kubernetes, AWS IAM, GCP IAM, PostgreSQL/Trino grants, and Airflow roles. The Skill validates principle-of-least-privilege patterns and returns a prioritized checklist of violations with concrete remediation guidance.

You need an RBAC audit for insider-threat investigation when you suspect excessive or misconfigured access control across your data platform components. It identifies orphaned or excessive service accounts and admin-equivalent policies, providing prioritized findings to remediate risky configurations before incidents occur.