WERANA · BLOG
Security insights, technical deep-dives, and the latest cybersecurity trends
Kubernetes security is not complete with image scanning, RBAC, and pod security settings alone. After deployment, real behaviors occur inside running pods and containers, including process execution, file access, network traffic, privilege escalation attempts, and abnormal outbound connections. WERANA Veluna uses runtime context to help identify real threats and prioritize response.
Vulnerability management can no longer rely only on CVSS scores or CVE counts. Real risk depends on whether a vulnerable asset is running, externally reachable, and connected to privilege escalation or lateral movement paths. WERANA Veluna combines scan results with EPSS, KEV, exposure, and runtime usage context so security teams can focus on exploitable risks that require immediate action.
Scanning is the starting point for identifying vulnerabilities, misconfigurations, and external exposures. However, actual risk depends on whether the affected asset is running, whether an attacker can reach it, and whether it is showing signs of abnormal behavior. WERANA Veluna analyzes the execution context of Kubernetes, containers, and hosts through eBPF, helping teams prioritize the threats that matter most in real operating environments.
When microservices multiply, nobody really knows what's flowing between them. We used eBPF to watch K8s East-West traffic at the kernel level — no code changes, no sidecars. Here's what we found.
