3 years ago

Category: Security, Infrastructure, Architecture, automation

I was leading a DevOps project for a client and requirements and designs were changing almost daily. At the time, it was a greenfield Cloud deployment with 30+ security and infrastructure services being deployed to create a secure cloud hosting platform. This platform was completely integrated and consisted of components like boundary services — jump servers, proxies, reverse proxies and file transfer services, as well as 2FA, certificate services, intrusion prevention, anti-virus, logging, monitoring and alerting to name just a few! All these services needed to talk to one another and each component stack needed ingress and egress rules that enabled traffic to route on the right protocols and ports to other services.

The first was that it reduced the amount of effort the Devs used to re-factor rules, and secondly it provided us with a central place to define all rules.