3 ms·
I've used outbound firewalls and it's painful. Your provider for some API changes IPs for whatever reason and now you need to change your firewall, etc. If you
by toast0 5y ago
I've used outbound firewalls and it's painful. Your provider for some API changes IPs for whatever reason and now you need to change your firewall, etc.
If you use an outbound http/socks proxy, it's a bit more tenable. You can set rules based on hostnames, but you're also on the hook for running a production proxy cluster. Hopefully you don't need outbound UDP.
- samwillis 5y agoThe majority of backend web apps only talk to a limited few services; db’s, internal queues, external apis. My main app talks to two internal db’s, and maybe 4 external apis. It should be possibles to specify the host names of these services and block everything else, certainly on a PAAS such a Heroku (they even know what internal services you are using), but that functionality isn’t there… I simply don’t understand why not. It should be possible to build this sort of firewall based on hostnames not IP addresses? Maybe with a custom DNS server? And to be honest I would take the configuration complexity if it made my apps more secure. There will be apps that talk to more, and as you said use UDP etc. but these will be the minority.
- ev1 5y agoit needs to be significantly more than just hostname / IP / DNS. a common attack i see for exfil behind FW is to sign up for a free account on heroku, fastly, cloudflare, etc so that your outbound destination is to a "good" IP. you can resolve api.legitimatecompany.example and then send the actual request to that IP (which is a CDN), with an encrypted Host: header of your own endpoint, for example.