DailySecu
CloudNetworks presents next-generation Kubernetes security strategy with integrated access control and secret management
| Distributed authorisation management and secret exposure issues addressed with QueryPie KAC and HashiCorp Vault■ New challenges for Kubernetes security in the AI and cloud-native eraAs AI and cloud-native technologies become standard in enterprise infrastructure, Kubernetes is enabling innovative productivity through service deployment automation and multi-cloud support. However, this convenience comes with increased complexity in security operations. Kubernetes is inherently a multi-tenant environment where multiple teams and users access cluster resources simultaneously. Namespaces and resources operated by each team are intermingled, and different roles such as development, operations, security, and data analysis require different permissions. This process can lead to fragmented permission management and inconsistent security policies.In real-world scenarios, RBAC (Role-Based Access Control) policies are often managed separately for each cluster, and since permissions are granted at the role level, it is challenging to enforce granular control at the resource name level. With the widespread use of CLI tools (kubectl, Lens, K9s, etc.) for direct access, there is a risk of unauthorised access without recording user session commands or going through approval processes.In this situation, as DevOps and CI/CD pipelines rapidly evolve, cases of hardcoding or exposing sensitive secrets in code or deployment pipelines are increasing. Ultimately, this can lead to a critical risk of a single cluster breach spreading to all cloud resources.■ QueryPie KAC Solves Real-World Kubernetes Access Control IssuesTo address these complex Kubernetes security management issues, CloudNetworks proposes QueryPie Kubernetes Access Controller (KAC), which provides centralised access control and auditing when developers, DevOps, and system engineers access the cluster using access tools such as kubectl, Lens, and K9s.Currently, most companies share Kubeconfig files with administrator privileges among multiple users or manage them individually for each cluster, making it difficult to apply consistent security policies. Additionally, it is challenging to track what actions users actually performed, limiting the ability to analyse the root cause of security incidents.QueryPie KAC provides user K8S access control, integrated audit logging, and an integrated management environment for assets in other systems to build an efficient infrastructure environment and manage application security through K8S Container Orchestration.Session recording and real-time monitoringWhen a user accesses a container, session recording is automatically performed to monitor actions within the container. All approved Kubernetes API requests are logged for monitoring and response, and the history of user actions after accessing the container can be replayed as a video for intuitive management.Detailed access control and permission managementK8S Resource name (regular expression) based access control rules can be applied to users, which is not supported by existing K8S RBAC. You can design detailed policies that allow access only to specific namespaces or resources with specific naming rules. Additionally, you can enhance security with user attribute-based access control (ABAC), which allows you to dynamically grant permissions based on various attributes such as the user's team, role, time zone, and IP address, overcoming the limitations of traditional role-based access control.■ Innovation in Kubernetes secret management with HashiCorp VaultThe second most important security challenge in a Kubernetes environment is secret management. AWS's EKS provides convenient K8S services, and sensitive information used in K8S is stored and used through the secret feature. However, such sensitive information is difficult to manage separately and poses a risk of leakage.Automating Secret Management with HashiCorp Vault VSOHashiCorp Vault provides a centralised secret management platform to address these structural issues. By deploying the Vault Secrets Operator (VSO), Kubernetes is integrated with Vault.In K8S, sensitive information used by service Pods is managed using the secret feature. By leveraging Vault VSO, such secret content can be centrally stored in the Vault key-value store. This enables more precise access control and continuous change management compared to the existing Kubernetes environment.Operational Efficiency and AutomationThis allows you to integrate and manage secrets used by Pods in K8S using Vault VSO, increasing the efficiency of sensitive information management. Additionally, you can modify K8S secrets and configure sensitive information changes and deployments through the application CI/CD pipeline.Vault sets a TTL (Time To Live) to automatically revoke credentials when they are no longer in use, and prevents secrets with expired lifetimes from being reused. All access and issuance events are recorded in audit logs, enabling consistent security governance across DevOps, CI/CD, and GitOps deployment pipelines.■ Kubernetes security implemented with QueryPie KAC and HashiCorp Vault integration workflowCloudNetworks' strategy goes beyond simply adopting QueryPie KAC and HashiCorp Vault as separate solutions; it aims to build an organic and integrated security workflow tailored to Kubernetes operations.When a user requests access to a Kubernetes cluster, QueryPie KAC determines whether to grant access based on policies. If access is granted, Vault dynamically issues secrets that match the user's or application's request purpose and permission level.When a Pod starts, VSO securely injects the latest secrets from Vault and automatically discards them according to the TTL settings when they are no longer needed. Operations teams can design systems that allow authorised users and applications to safely use the necessary permissions and automatically recover them without manually managing credentials. All approval requests, session recordings, and secret issuance/disposal histories are integrated into a central audit log, enabling compliance with regulatory and security audit requirements. The operations team and security team can visualise the entire cluster security status in real time, detect abnormal behaviour, and analyse incidents in detail when they occur from a unified dashboard.■ CloudNetworks' Kubernetes integration security support planCloudNetworks is an official partner of HashiCorp and QueryPie and has experience in building access control and secret management solutions in various industries. We support a phased approach tailored to each company's cluster size, regulatory environment, and security maturity. Depending on the company's requirements, we can provide centralised access control through QueryPie KAC, secret management through HashiCorp Vault, or a combination of both solutions. In addition, we provide a cloud-native security environment tailored to the security journey of each company, including integration with CI/CD pipelines, Secrets Operator deployment, and DevSecOps policy design. Jeong Heung-kyun, CEO of CloudNetworks, said, ‘Our goal is to help companies achieve consistent security governance and compliance they can trust without compromising the innovative automation and flexibility provided by Kubernetes.’
July 03, 2025