Cloudanix home page
Search...
⌘K
Community
Login
Login
Search...
Navigation
Ensure Default Service Accounts Not Actively Used.
Overview
AWS
Azure
GCP
GitHub
On-Demand Scan
Kubernetes
Integrations
AWS Introduction
Security of your AWS Account
AWS Pricing
AWS Services which determine your cost
AWS Threats
Getting Started with AWS Realtime Events
AWS Misconfigurations
Getting Started with AWS Audit
Permissions required for Misconfigurations Detection
API Gateway Audit
Cloudformation Audit
CloudFront Audit
CloudTrail Audit
Cloudwatch Audit
DynamoDB Audit
EC2 Audit
Elastic Search Audit
ELB Audit
IAM Audit
KMS Audit
Kubernetes Audit
Lambda Audit
RDS Audit
Redshift Audit
Route53 Audit
S3 Audit
Security Groups Audit
SES Audit
SNS Audit
IAM Deep Dive
App Sync Audit
Code Build Audit
Open Search Audit
Shield Audit
SQS Audit
On this page
More Info:
Risk Level
Address
Compliance Standards
Additional Reading:
Ensure Default Service Accounts Not Actively Used.
More Info:
The default service account should not be used to ensure that rights granted to applications can be more easily audited and reviewed.
Risk Level
Medium
Address
Security
Compliance Standards
CISEKS
Additional Reading:
https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/
Assistant
Responses are generated using AI and may contain mistakes.