Cloudanix home page
Search...
⌘K
Community
Login
Login
Search...
Navigation
Minimize Wildcard Use In Roles And Cluster Roles
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
Minimize Wildcard Use In Roles And Cluster Roles
More Info:
Kubernetes Roles and ClusterRoles provide access to resources based on sets of objects and actions that can be taken on those objects. It is possible to set either of these to be the wildcard ”*” which matches all items.
Risk Level
Medium
Address
Security
Compliance Standards
CISGKE
Assistant
Responses are generated using AI and may contain mistakes.