From the desk of KSOC's security research team:The Kubernetes development team received reports that the Kubernetes API may have a Server Side Request Forgery vulnerability when using aggregated API servers. The team promptly patched multiple versions of Kubernetes in order to help remediate the issue, leaving it to Kubernetes

Individual engineering teams care about security, but typically for the platform or application architecture they’re working on. CISOs on the other hand must care about all security that’s happening inside of an organization. From infrastructure teams to application teams, the CISO is ultimately responsible. When it comes to

Most security breaches start with a faulty service account, password breach, or overlook of permissions given to a user or a service account. It could be any type of security breach from a fishing scam to a brute force attack. This occurs because there’s a major oversight to how

Thinking about when to implement security for Kubernetes is much like any other field of technology. If you’re a Systems Administrator or Infrastructure Engineer, you must understand certain platforms and systems prior to securing them. For example, if you’re running workloads in ESXi, you must first understand ESXi

Standard best practices for software development ask you to follow a ton of testing standards. From unit tests to mock tests to security tests with tools like Sonarqube and Veracode from a security static analysis perspective. When Infrastructure-as-Code and configuration languages started coming out, those same standards weren’t followed,

A recent article showed that over 900,000 Kubernetes endpoints (API servers) are sitting publicly on the internet. If you think that’s bad, remember that a Kubernetes API server being public is only about 5-10% of the security concerns that happen in many production environments when it comes to

By Brooke Motta, CEO It’s my privilege to announce that — KSOC has raised $6 million in seed funding! I am thrilled to work alongside an incredible team of investors, advisors, customers, colleagues and thought leaders.   It’s an exciting time. Many organizations have adopted cloud-native architectures, and according to