In the last part of the article series on the 4C’s of cloud-native security, we will look at securing the cloud environment itself. Although actual steps to harden your cloud infrastructure differ based on the cloud vendor and the services used to architecture your cloud-native application, many concepts and methodologies are quite similar.
Archive: our articles
Category: Cloud Native
In this part of the article series on the 4C’s of cloud-native security, we will take a closer look at code security. We will briefly inspect why code security is essential, why it should be addressed from the beginning, and why trends such as shift-left security are important aspects of overall security considerations.
Securing the Kubernetes cluster (which may act as a runtime platform for several components of typical cloud-native applications) addresses one of the 4C’s in cloud-native security. If you haven’t heard about the 4C’s of cloud-native security yet or want a quick refresher, you should read my corresponding introduction article.
Securing the container images of your cloud-native application building blocks addresses one of the 4C’s in cloud-native security. If you haven’t heard about the 4C’s of cloud-native security yet or want a quick refresher, you should read my corresponding introduction post.
Containers and cloud-native design patterns gained popularity over the past years. More and more organizations use containers in production and adopt cloud-native practices and methodologies to get even more value from existing containerized applications and underlying technologies such as container orchestrators like Kubernetes.
Learn how to use the Azure Cognitive Search, prepare your application data to make it searchable, and improve performance and quality of your search results. In the last articles of this series, we created an index and filled it with data from the PokeApi. Now it is time to show you how you can search this index and integrate the search into your application.
In this article series, you learn how to use the Azure Cognitive Search, prepare your application data to make it searchable, and improve your search results’ performance and quality. In the first article, I introduced Azure Cognitive Search Services. In the second part, I demonstrated how to build an index that contains your searchable data. Now, you will see how to fill your index automatically from an Azure data source.
With this article series, you will learn how to use the Azure Cognitive Search, prepare your application data to make it searchable, and improve your search results’ performance and quality. This second article of the series will demonstrate how to create, modify, and configure your data’s index.
Internet-facing solutions of different kinds such as websites, single-page applications (SPAs), or web/REST APIs have a common requirement: they require proper transport encryption. Adding a proper SSL certificate to services is not optional. If we talk about HTTP, it is always HTTPS. You should treat it the same way. Dealing with certificates has been tedious and cumbersome in the past. We saw popular websites and cloud vendors being in trouble because their SSL certificates expired in production environments. With the rise of Let’s Encrypt in 2014, acquiring and rotating valid SSL certificates became fairly easy.
With this article series, you will learn what Azure Cognitive Search is, and how to use it. See the essential steps and make your application’s data searchable, improve search performance and the quality of search results. As this is the first article of the series, it provides you with an introduction to Azure Cognitive Search and demonstrates how to create your first search service.