Terraform is the de facto tool if you work with infrastructure as code (IaC). Regardless of the resource provider, it allows your organization to work with all of them simultaneously. One unquestionable aspect is Terraform security, since any configuration error can affect the entire infrastructure. In this article we want to explain the benefits of using Terraform, and provide guidance for using Terraform in a secure way by reference to some security best practices. Let’s get started!

HTTPS is the standard method for internet communications that transmit sensitive data. The TLS protocol is the backbone of HTTPS, encrypting connections so transmitted information can’t be intercepted or modified. HTTPS should also be used with local web applications that transmit sensitive data. This includes NetApp servers, since external applications and users need to authenticate, authorize and transfer data with the NetApp ONTAP operating system.

I recently had the pleasure of participating in a great panel discussion at the San Diego Cyber Security Summit, entitled “Cloud Security — Leveraging Its Strengths and Overcoming Its Vulnerabilities,” alongside representatives from Palo Alto Networks, Gigamon, Sysdig, Lacework, Imperva, and Tufin.

Velero is an open source tool for backing up and restoring resources in a Kubernetes cluster, performing disaster recovery, and migrating resources and persistent volumes to another Kubernetes cluster. Velero backup helps many organizations protect data stored in persistent volumes and makes your entire Kubernetes cluster more resilient. Velero has been pulled over 50M times from DockerHub! It is the most popular data protection choice for the Kubernetes community.

A microservice application comprises small autonomous services that communicate with each other through application programming interfaces (APIs) — as standalone services or via a service mesh. These API calls or requests raise security and compliance concerns if not appropriately secured through authentication and authorization checks. Service-to-service authorization is the process of determining what actions an authenticated service is allowed to perform based on pre-defined policies.