---
title: "Discussion on \"Hardening a 3-tier app before Kubernetes: 6 things that were quietly broken\" | Hashnode"
description: "Discussion on \"Hardening a 3-tier app before Kubernetes: 6 things that were quietly broken\". Before moving Deal Aggregator to Kubernetes I audited it the way an attacker would. Public delete endpoints, a ReDoS hole, an unauthenticated database and internal tools on the open internet. Here is what I found and how I fixed each one."
url: "https://hashnode.com/posts/hardening-a-3-tier-app-before-kubernetes/6ad0d42179583e25958b8a97"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Hardening a 3-tier app before Kubernetes: 6 things that were quietly broken](https://devseccloud.hashnode.dev/hardening-a-3-tier-app-before-kubernetes?utm_source=hashnode&utm_medium=feed)

Before moving Deal Aggregator to Kubernetes I audited it the way an attacker would. Public delete endpoints, a ReDoS hole, an unauthenticated database and internal tools on the open internet. Here is what I found and how I fixed each one.

Oct 15 · 5 min read · devseccloud.hashnode.dev  
Read the article

-   [#devsecops](https://hashnode.com/tag/devsecops)
-   [#docker](https://hashnode.com/tag/docker)
-   [#node-js](https://hashnode.com/tag/node-js)
-   [#nginx](https://hashnode.com/tag/nginx)

## Written by

[Sulakshana Karunarathne](https://hashnode.com/@sulaa29)

@sulaa29 · Colombo

  
[View profile](https://hashnode.com/@sulaa29)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.