Unsurprisingly, a lot of people say they don’t like working with security teams. Security teams often have ridiculous requirements, and it can be painful for everyone when releases get delayed. I’ve been guilty of thinking the same thing, so when I was approached at my job at Doximity to build a security team (without prior experience doing so), I knew I wanted to take a different approach.

Modern application development requires more work to ensure the development path and the data it produces are fully in sync, secure, optimized, and error-free. This responsibility has increasingly fallen upon application developers. They’re being asked to double as database administrators to maintain fluidity in the process and support an agency’s rapid release cycle.

We have unveiled several exciting announcements recently, from the launch of Ivanti Neurons to all of our strategic partnerships and integrations (see the details on Intel and Qualys). In fact, we have had so much content to announce that we've needed to create a whole new blog category! But this train is not slowing down any time soon.

Bring your own device (BYOD) policies are more important than ever since smartphones became pervasive. I’d argue that even if you don’t want to allow personal user devices to access corporate data or applications, you still need a BYOD policy if only to acknowledge the fact that users are already bringing their personal devices into your place of business.

With one of the largest threats to a company’s security and privacy being its own employees, having employees work remotely only adds to the risk. While this year’s Verizon Data Breach Investigations Report chalks it up to internal errors rather than intentional malice, the threat remains. Many corporations have sent employees to work from the confines of their homes, creating a greater need for protection against data and security breaches.

The HAProxy Kubernetes Ingress Controller integrates with cert-manager to provide Let’s Encrypt TLS certificates. When it comes to TLS in Kubernetes, the first thing to appreciate when you use the HAProxy Ingress Controller is that all traffic for all services travelling to your Kubernetes cluster passes through HAProxy. Requests are then routed towards the appropriate backend services depending on metadata in the request, such as the Host header.