In today’s interconnected software landscape, supply chain security has evolved from an afterthought to a mission-critical priority. High-profile incidents, such as the SolarWinds breach, have demonstrated how a single vulnerability can cascade through the entire software development pipeline—affecting everything from code commits to production environments. The consequences of these attacks can be devastating, not only for the businesses targeted but also for their customers and stakeholders, underscoring the urgent need for a proactive, defense-in-depth approach to securing every link in the chain.
Read articleIn today’s interconnected software landscape, supply chain security has evolved from an afterthought to a mission-critical priority. High-profile incidents, such as the SolarWinds breach, have demonstrated how a single vulnerability can cascade through the entire software development pipeline—affecting everything from code commits to production environments. The consequences of these attacks can be devastating, not only for the businesses targeted but also for their customers and stakeholders, underscoring the urgent need for a proactive, defense-in-depth approach to securing every link in the chain.
What is ModSecurity? ModSecurity is an open-source, cross-platform web application firewall (WAF) engine that provides a robust security layer for your web applications. Initially developed for Apache, ModSecurity now supports IIS and Nginx, offering flexible and powerful protection against various web-based attacks. It acts as an intrusion detection and prevention engine, analyzing HTTP traffic and blocking malicious requests before they reach your application. Originally developed and sponsored by Trustwave, it has been transfered to the OWASP foundation earlier this year.
Kubernetes has quickly become the industry standard for managing applications in the cloud. What was once seen as a complex technology is now part of the basics for companies looking to grow and scale their digital operations. These days, setting up a Kubernetes cluster is fairly straightforward, and many teams can get up and running in no time. However, just because it’s easy to set up doesn’t mean it’s always done right.
Automating DNS Management with External-DNS, FluxCD, and Cloudflare Managing DNS records can invole a lot of manual work. If you’ve ever had to manually copy and paste IP addresses to create DNS records, or tried to rely on wildcard entries that point to a single load balancer IP or CNAME, you know the pain. It often goes something like this: you run kubectl to grab the load balancer IP, then hop over to your Terraform DNS repo, make the necessary changes, create a Merge Request, wait for the review, and only after all that, you finally get the DNS record updated.
We are happy to bring you our latest Whitepaper: Implementing the 2+1 Backup Strategy for Kubernetes Environments!
In this whitepaper we talk about how you can utilize open-source tooling to implement a 2+1 back-up strategy, providing multiple layers of redundancy, significantly reducing the risk of total data loss and ensuring business continuity.
As software and DevOps engineers, spinning up new PostgreSQL deployments for various applications, clusters, and environments is a straightforward task. However, these deployments inevitably require updates over time. Not all PostgreSQL deployments are managed by an operator, and upgrading these instances can involve significant manual effort.
When you work on infrastructure, develop helm charts or simply want you run your tests in a more production like environment, running Kubernetes on your Gitlab CI may a good fit for you. Luckily, it’s only a little bit of configuration to set-up!