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
GCP Introduction
Authenticating your GCP account
GCP Pricing
GCP Services which determine your cost
GCP Threats
Getting Started with gcp Realtime Events
GCP Misconfigurations
Getting Started with GCP Audit
CloudSql Audit
Cloud Tasks Monitoring
Dataflow Monitoring
Function Monitoring
Monitoring Compliance
PubSubLite Monitoring
Spanner Monitoring
NoSQL Monitoring
Compute Audit
IAM Audit
BigQuery Monitoring
CDN Monitoring
DNS Monitoring
KMS Monitoring
Kubernetes Audit
Load Balancer Monitoring
Log Monitoring
Storage Audit
Pub/Sub Monitoring
VPC Audit
IAM Deep Dive
Resources
GCP Services which determine your cost
GCP Threats
Getting Started with gcp Realtime Events
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
CISGKE
Assistant
Responses are generated using AI and may contain mistakes.