📐ISO/IEC 42001 42001-8.2Rule: ISO42001-8-001high

AI workload least-privilege RBAC

Description

Clause 8.2 — Operational controls applied to AI processes; access controls enforced.

⚠️ Risk Impact

AI workloads with excessive privilege become breach amplifiers — compromise of an AI workload becomes compromise of cluster-wide resources.

🔍 How EchelonGraph Detects This

ISO42001-8-001Automated scanner rule

EchelonGraph's Tier 1 Cloud Scanner automatically checks for this condition across all connected cloud accounts. Violations are flagged as high-severity findings with remediation guidance.

🖥️ Manual Verification

terminal
kubectl auth can-i --list --as=system:serviceaccount:ai:default | grep -E 'cluster|nodes|secrets'

🔧 Remediation

Apply namespace-scoped RBAC to every AI workload. Revoke cluster-admin from AI service accounts. Use ServiceAccount projection for short-lived tokens.

💀 Real-World Attack Scenario

A Kubeflow pipeline service account was granted cluster-admin during a debugging session 'temporarily'. The temporary grant persisted for 8 months. When the pipeline was compromised via a malicious notebook upload, the attacker had cluster-admin within minutes.

💰 Cost of Non-Compliance

Over-privileged AI workloads: avg 4.6× breach impact (IBM 2024 X-Force Threat Intelligence Index).

📋 Audit Questions

  • 1.What RBAC does your top AI workload have?
  • 2.Is any AI workload granted cluster-admin?
  • 3.How often is AI-namespace RBAC reviewed?
  • 4.Show me a recent RBAC review finding.

🎯 MITRE ATT&CK Mapping

T1098.001 — Additional Cloud Credentials

🏗️ Infrastructure as Code Fix

main.tf
resource "kubernetes_role_binding_v1" "ai_namespace_only" {
  metadata { name = "ai-ns-only"; namespace = "ai" }
  role_ref { api_group = "rbac.authorization.k8s.io"; kind = "Role"; name = "ai-pipeline-role" }
  subject {
    kind = "ServiceAccount"; name = "ai-pipeline"; namespace = "ai"
  }
}

⚡ Common Pitfalls

  • ⛔Temporary cluster-admin that becomes permanent
  • ⛔Auto-generated default SA tokens auto-mounted
  • ⛔Wildcard verbs in RoleBindings

📈 Business Value

Least-privilege RBAC contains the blast radius of AI-workload compromise — converting potential cluster-wide breach to namespace-scoped incident.

⏱️ Effort Estimate

Manual

2-3 weeks for cluster-wide AI RBAC audit + tightening

With EchelonGraph

EchelonGraph audits AI-namespace RBAC continuously; flags over-privileged service accounts

🔗 Cross-Framework References

EUAIA-ART16-RBACCIS-K8S-5.1.1

Automate ISO/IEC 42001 42001-8.2 compliance

EchelonGraph continuously monitors this control across all your cloud accounts.

Start Free →