It’s hard to argue that that all web services and applications should not be secured using HTTPS. However, securely obtaining and deploying the certificates needed for securing web services is a challenge, especially for developers.
Simply put, there is no easy way for developers to request certificates that comply with corporate policy. First, they need to know where the internal CA is, then they must be granted access to it and possess the proper credential to authenticate. Once they pass those hurdles, they need to know how to request a certificate with the proper characteristics, including who’s using it, what it will be used for and how long it should be valid. All of these delays will tempt developers to sidestep security to meet their SLAs.
Here are five DevOps shortcuts that should make the hair on the back of your neck stand on end:
- Not using TLS/SSL to secure connections
When much of the DevOps process is automated, manual certificate processes will disrupt the workflow—something developers would rather avoid. In fact, many developers find it easier to ignore certificates than to allow security to delay the release. Deploying web services without securing them with HTTPS leaves end users vulnerable.
- Spinning up their own certificate authorities
Even if they do use certificates, developers often look for shortcuts to simplify typically arduous security processes. They need look no further than to their DevOps platforms, which provide a script or instructions that allow developers to spin up their own internal certificate authority (CA). This allows developers to issue as many certificates as they need as fast as they need them. The challenge is that these “test” certificates are not always replaced by corporate-compliant certificates when the application moves to production. If that happens, your organization will be exposed to a veritable avalanche of certificates that you can’t see or that you may not even know about.
- Introducing self-signed certificates
You should also be wary of how your in-house developers are using self-signed certificates. Rather than purchasing CA certificates, developers can download an open source implementation of SSL and TLS called OpenSSL. They can then create the certificates they need in order to develop and test software. When used in production versions of applications, these self-signed certificates can make you vulnerable to unforeseen attacks. If not properly monitored, self-signed certificates can allow cyber-criminals to conduct man-in-the-middle attacks that impersonate banking, e-commerce, and social media websites.
- Creating certificates with weak signature algorithms
Dismissing or implementing keys and certificates poorly not only exposes your organization to unnecessary security vulnerabilities, but it can also lead to chaos by inserting inconsistent, manual steps into an increasingly automated environment. If you don’t maintain control over the security of your certificates, you may inadvertently enable attackers to use a compromised, stolen, or forged certificate to impersonate, eavesdrop, and monitor your infrastructure and decrypt communications you thought were private.
- Sidestepping or completely ignoring security policies
Finally, developers are typically not security experts and most do not aim to be. They are less likely to consider anything but the most basic security measures to meet their objectives, especially given past struggles with the error-prone manual nature of certificate provisioning. The result is that security policies are either ignored completely or minimized to maintain the velocity of DevOps. This oversight can create blind spots in your security posture that allow cyber criminals to hide in your encrypted tunnels.
The speed of DevOps does not have to come at the expense of security. There are ways that you can centralize, standardize, and automate the process of procuring keys and certificates as part of your end-to-end DevOps environment. Automating certificate acquisition will enable your DevOps teams to deliver applications and IT services more effectively and more securely. But to do this, your DevOps practitioners need to understand that they share important responsibilities for security; it isn’t just someone else’s job.