Cloudanix home page
Search...
⌘K
Community
Login
Login
Search...
Navigation
The Default Namespace Should Not Be 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
The Default Namespace Should Not Be Used
More Info:
Kubernetes provides a default namespace, where objects are placed if no namespace is specified for them. Placing objects in this namespace makes application of RBAC and other controls more difficult.
Risk Level
Low
Address
Security
Compliance Standards
CISEKS
Assistant
Responses are generated using AI and may contain mistakes.