6 ms·

I did mention two other security layers, so I take issue with you counting only one. Especially since the SSH access would obviously be on a dedicated jumpgate

I did mention two other security layers, so I take issue with you counting only one. Especially since the SSH access would obviously be on a dedicated jumpgate, so that IS two just right there. Maybe running a different OS and architecture just lower risk of one zero-day piercing both. Also huproxy, or squid, or anything else that provides network-level access. But I also think that if you consider network-level access as fundamentally different from other access then that's kinda missing the point of BeyondCorp.

johnmaguire2013 9y ago
> But I also think that if you consider network-level access as fundamentally different from other access then that's kinda missing the point of BeyondCorp. I understand what you're saying here. I think to me, the point is, don't trust LAN access more than WAN access. But that doesn't mean that restricting LAN access is a bad idea. One of the benefits to BeyondCorp is that you don't (generally) require LAN access in order to access resources. But if your BeyondCorp server goes down, then what? How will you access it? I probably still wouldn't want to expose my mission critical services over WAN (though I understand your point that VPN is a service exposed over WAN -- and why not SSH then?) Maybe that's wrong of me (I likely haven't given this as much thought as you), especially if you're using TCP-MD5 (which I actually haven't heard of until now, sorry for missing that), or filtering source IP addresses. This is an interesting discussion, and I really appreciate your thoughtfulness. I'd love to hear more about huproxy and how it's working for you, if you'd care to discuss it more. My email is jmaguire@duo.com.