During the process of turning data into insights, the most compelling data often comes with an added responsibility—the need to protect the people whose lives are caught up in that data. Plenty of data sets include sensitive information, and it’s the duty of every organization, down to each individual, to ensure that sensitive information is handled appropriately.
For the DevOps-averse developer, lambdas are heaven. They can focus on writing self-contained and modularized pieces of code, deploying these functions for on-demand execution without being concerned about resource management or infrastructure. Lambda execution , however, can be tricky. Serverless security with the AWS API Gateway can feel daunting, especially when all you want to do is call a simple function as an API endpoint. For this, there’s the ease of Kong Gateway .
In the previous article we discussed how to enable a server initiated encrypted connection to a Microsoft SQL Server. But what if we have a scenario where we do not want to incur the overhead of encryption for every application? In that scenario instead of configuring the server to force encryption we will instead need the client to initiate the encrypted connection.
We’re proud to announce that we’ve received our first SOC2 Type II report, meaning that a rigorous audit validated our compliance with the highest industry standards, confirming our commitment to the security of your data.
