You might have spotted this tweet from backend engineer @jack-monzo this weekend:
The Security team has been working on network isolation for these 1,500 services – Jack breaks down how they’ve done it in this post
You might have spotted this tweet from backend engineer @jack-monzo this weekend:
The Security team has been working on network isolation for these 1,500 services – Jack breaks down how they’ve done it in this post
Well done Jack and the rest of the team, this is a massive accomplishment.
I’m interested in the tools/ways you implement the automated check on new code, are you using something like Danger?
Great write up and progress too.
We write our own CI check scripts and tools and run them in CircleCI
Great article! I can imagine how excited is to develop this feature and rolling it out to production.
That’s a nice network security design. Let’s say a rogue actor gains access to kube API server, outside your normal CD process. They deploy a workload using a pod spec containing the known labels necessary to call some service. Will the system prevent/detect this type of intrusion?