Ensure AKS cluster uses managed identities
AKS should use managed identities instead of service principals.
Security Impact
Service principals require credential rotation and can be exposed.
How to Remediate
Create clusters with system-assigned managed identity. Migrate existing clusters.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your Azure environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Azure Kubernetes Service (AKS) resources across your Azure subscriptions every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for SOC 2, PCI-DSS, NIST 800-53 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- azure-aks-6
- Service
- Azure Kubernetes Service (AKS)
- Category
- Identity Management
- Severity
- HIGH
Automate This Check
TigerGate automatically scans your Azure environment for this and 160+ other security checks.
Start Free TrialRelated Azure Kubernetes Service (AKS) Checks
View all checksEnsure AKS cluster has Azure AD integration enabled
Ensure AKS cluster has Azure RBAC enabled
Ensure AKS cluster API server is not publicly accessible
Ensure AKS uses Azure Policy add-on
Ensure AKS cluster has network policy enabled