I’m excited to share that we’ve raised $30M in Series B funding led by Sapphire Ventures. This is a significant milestone for Uptycs. Jai Das from Sapphire Ventures led the round with participation from existing investors Comcast Ventures and ForgePoint Capital. It was an oversubscribed round with no room for additional investors. This serves as a testament to our strong customer relationships, our current success as a venture, and the excitement around the space of SQL-powered security analytics.
Network traffic encryption is increasing. This increase is driven by demand for privacy protection and the availability of great services for deploying certificates for free. According to Google’s Transparency Report, 88% of web traffic performed on Chrome for Windows is encrypted, and that number is higher for macOS, Android, and ChromeOS. The encryption trend is even clearer when you look at the percentage of HTTPS browsing time in the Transparency Report. At the same time, malware is also following this trend, as the increased security allows attackers to evade some detection mechanisms.
Kubernetes nodes – the machines responsible for running your container workloads – can come in a number of shapes, sizes, and configurations. One common deployment pattern, however, is a lack of in-transit encryption between them.
Another common deployment pattern? Lack of TLS support on the container workloads themselves. After all, who wants to set up and manage a PKI (Public-Key Infrastructure) and a private CA (Certificate Authority) for tens or hundreds of microservices, and get the certificates to be trusted by all workloads? I don’t know about you, but that doesn’t sound like a lot of fun to me.
For many security-conscious businesses looking for a SaaS provider, SOC 2 compliance is a minimal requirement. Unfortunately, many providers aren't sure how to implement SOC 2 compliance requirements, as they are inherently vague.