4 ms·
The problem is that you think it’s private but it isn’t. If an attacker wants access they’ll get access. At that point the false sense of security is a hindranc
by nindalf 2y ago
The problem is that you think it’s private but it isn’t. If an attacker wants access they’ll get access. At that point the false sense of security is a hindrance, because systems might not have been secured like they would have been on the public Internet.
- usrnm 2y ago> might not have been secured like they would have been on the public Internet Yes, because we all know how secure the tings on the public Internet are. /s Nobody's saying that a private network doesn't have to be properly secured, you're fighting a strawman argument
- krab 2y agoMaybe knowing there are many institutions on the network is a good motivation to keep services secure. It's apparent any hospital or vendor may be breached. So if you overcome the false sense of security, the separate network will give you another layer of defense.
- jaapz 2y agoWho says they're not securing anything apart from being air-gapped from the internet?
- clan 2y agoSecure is not a binary term. If sjunet is managed as a number of interconnected airgapped networks then I for sure find that more secure than a Internet connected network. The attacker surely still have vectors in but whole classes of common attacks are mitigated. Even if it is just "one big intranet" it is still better than one big intranet with one really good ((zero) trust me bro!) firewall to the Internet. Various levels of zero trust principles can easily be applied within sjunet. That makes it better in my eyes. For critical infrastructure I find this an important step. In the end security relies on us stupid humans. And it is easier to manage an airgap. It is the number of things we do afterwards to bypass it which is the problem. The idea of an Intranet is still sound. But private does not mean secure. It is just a security layer. The next layer is if you run it fully open. Are the rooms locked? Do you require 802.11X certificates for connectivity? Are all ports open for all clients/hosts. Do you have a sensible policy for you host configuration? Have you segmented the network even further? Etc. Etc. So your point is still valid for sure! You should secure it like on the public Internet aka a hostile environment. That is the important takeaway. My point is that is should no be used as an argument against a private network. For large critical infrastructure such as hospitals it makes good sense. It is an added layer for the attacker to overcome - it is not security theater. For some the hassle might not be worth the while but that is then the trade off as with all forms of security. It ain't binary but discussion often end up like that. Done right it can be additive. Done wrong it just adds pain and agony. We all dread the security theatre. I boldly claim this aint't it.
- actionfromafar 2y agoIt's not only about security but also availability. If the regular Internet goes down for some reason, the private network (is meant to) keep operating.
- msla 2y agoSo they actually have multiple physical sets of cables?
- actionfromafar 2y agoYes, I think so. There's not much public information, perhaps on purpose.