Timeline for Is HTTPS required for local network server to server communication
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2021 at 8:26 | comment | added | Chibueze Opata | The title of this answer is misleading, 'A network that has not been explicitly secured is not secure' is a better phrase. A network being internal has nothing to do with its security so you make the same error by using the opposite statement. Internal networks should be secure and if they're not or they can't be, that's a whole different ball game. If you have to use https in your secure internal network, you have way bigger problems. | |
| Mar 9, 2020 at 21:03 | comment | added | Mike Robinson | Also: remember that you can use technologies like certificate-based VPNs on internal networks as well as outward-facing ones, and the benefits are the same. You can wall-off portions of your internal network so that they cannot be accessed except by those internal systems which possess one-of-a-kind crypto credentials that only your company can issue. The nice thing about VPNs is that they secure everything ... and yet they do it transparently to the clients that are employing them. It adds one more strong layer of accountability, easily and manageably. | |
| Mar 9, 2020 at 13:35 | history | answered | Peteris | CC BY-SA 4.0 |