News for hackers. Stuff that matters.
Re:250M Microsoft customer service and support records expos... by monksy on Wednesday January 22, 2020 @02:06PM (#22120838)
We don't have sysadmins anymore "because of the cloud"
Re:250M Microsoft customer service and support records expos... by bcrosby95 on Wednesday January 22, 2020 @03:31PM (#22121685)
Equally important, we don't have network admins. It would be physically impossible to expose our search database like this to the open internet. Extra layers of protection are great.

It reminds me of companies I've worked with before that accidentally had a production site pointed to a dev database. Why the hell is that even physically possible with your network setup?

Re:250M Microsoft customer service and support records expos... by mdavidn on Wednesday January 22, 2020 @04:44PM (#22122381)
Amazon does provide a mechanism to define private networks disconnected from the internet.

https://aws.amazon.com/vpc/

Re:250M Microsoft customer service and support records expos... by mschuster91 on Wednesday January 22, 2020 @04:15PM (#22122118)
Welcome to the wonderful world of Kubernetes (or, for that matter, any Docker orchestration solution, such as DC/OS).

Anything can reach anything, provided you know the naming schema... and there's no easy way to fix it on anything that is not AWS/Azure/GCP, not without losing all the benefits of a self hosted k8s cluster in the first place.

Openstack at least provides ways to isolate machines, but that's VM-level only and truly an ultimate PITA to set up.

Re:250M Microsoft customer service and support records expos... by arpa on Wednesday January 22, 2020 @04:19PM (#22122165)
Not entirely true, there are network security policies (on select few CNI providers) and other means of segregation using good old iptables (although probably need to update alternatives for iptables to point to iptables-legacy for them to work).
Re:250M Microsoft customer service and support records expos... by mschuster91 on Wednesday January 22, 2020 @04:21PM (#22122183)
Ew. iptables (or any other way of messing around with the black magic that Docker and the orchestrators do to provide intra-container networking) is one thing only and that is a nice way to shoot yourself in the head while aiming at your legs.
Re:250M Microsoft customer service and support records expos... by arpa on Wednesday January 22, 2020 @04:34PM (#22122293)
To be entirely honest, if you know what you're doing and how lets say kube-proxy works in essence, things get pretty easy and simple. If you start every configuration of firewall with iptables -F, you're gonna have an interesting time. However, if you spend some time around these beasts, they are pretty well and logically built and it is trivial to coexist and modify your chains without touching those managed by docker/k8s. There is no black magic/and or wrong with the way they manage the rules. I'm much more angry at proper iptables being moved to iptables-legacy and systemd messing around with my resolv.conf :)
Re:250M Microsoft customer service and support records expos... by mbreedlove on Wednesday January 22, 2020 @02:47PM (#22121256)
"Sysadmins? No, we just have devops now!"
Re:250M Microsoft customer service and support records expos... by dvfjsdhgfv on Wednesday January 22, 2020 @02:59PM (#22121379)
Many managers use "devops" as an excuse to put a lot of burden on a small team, then this team is doing their best to automate managing a large number of machines but it's physically impossible to delve deeper into details and polish things, hence mishaps are bound to happen. And don't get me started on on what is happening inside containers.
Re:250M Microsoft customer service and support records expos... by tylfin on Wednesday January 22, 2020 @04:07PM (#22122048)
Sorry but I'd like to get you started on what is happening inside containers ;P

Specifically can you go into more details about what worries you with containers. Is it insecure images with out of date software, or risky applications inside the containers? Something else?

Re:250M Microsoft customer service and support records expos... by mschuster91 on Wednesday January 22, 2020 @04:17PM (#22122143)
Let's imagine your JIRA is insecure, someone owns it and obtains RCE, then does a privilege escalation on the host, whoops suddenly all services are accessible whereas that would have required more steps and owning in the old one-vm/bare metal-server-per-service model.
Re:250M Microsoft customer service and support records expos... by arpa on Wednesday January 22, 2020 @04:25PM (#22122226)
Escaping properly namespaced/pivot_root'ed environment and owning a host is non-trivial too.