3 ms·
Perhaps, but at the same time, you shouldn't be using IP addresses as a security mechanism. Assume the connection between your hosts is compromised, and code a
by JoshTriplett 11y ago
Perhaps, but at the same time, you shouldn't be using IP addresses as a security mechanism. Assume the connection between your hosts is compromised, and code accordingly, with encrypted/authenticated connections between hosts.
- tptacek 11y agoNot that I want to wade into the "don't use D.O." part of this argument, but, in practice, nobody does this. Virtually every deployment environment I've ever seen with more than 4 hosts in it would be fatally compromised by an attacker who could reach any IP address in that environment.
- JoshTriplett 11y agoTrue. I haven't heard folks other than Google explicitly talking about this as a best practice.
- jsmthrowaway 11y agoA VPC is analogous to a physical network, not a subnet. Nobody uses them that way because it's not easy to grok, but you can treat a VPC as a physical network complete with your own numbering and ACL policies. If you're doing that defense in depth on a physical network, I'm impressed by your dedication but would avoid your work for wasting resources.
- beachstartup 11y agoit's analogous to a vlan, and it's not that much work to maintain ACLs if the vlans aren't supposed to talk to each other, which they're not, that's the whole point.
- deleted 11y ago[deleted]