4 ms·
> And this is were I fundamentally disagree with the author. Nothing you've listed requires access to the internet - it requires access to a network. Ok - now
by horsawlarway 2y ago
> And this is were I fundamentally disagree with the author. Nothing you've listed requires access to the internet - it requires access to a network.
Ok - now what? I don't understand the disagreement you seem to think you have.
That network inevitably requires a connection to the outside world or those exact same features I listed above stop working. So you're just shifting blame without an answer...
So continue with your path - now I have an X-Ray machine that's connected to a network. The router on that network still has to connect to the internet to facilitate functional use of the machine, so let's assume crowdstrike is running there - tell me how your advice of "Don't connect it to the internet" is meaningful here?
I have an expert radiologist who I want to confer with on my patients x-ray, he's in a different state - what is your advice? How is my problem solved with a banal "Just don't connect it!"?
- flumpcakes 2y agoMany countries have dedicated network for medical services. If you don't you could use dark fibre, MPLS, etc. Connecting to an network should not automatically get you routable access to the internet. A lot of headaches from cyber attacks would go away with this was the principle. But for a lot of people connecting to the "network" means unfettered "Internet" connectivity. I've worked at places that have used dark fibre and MPLS and had no security problems, as that's not an easy attack vector. Moving to 'SDN WAN' means now sites are connected to the _Internet_ and a simple DDOS can take your branch down. This may or may not be important to you, but the general advice of keeping off the Internet as much as possible unless you need it is good advice (and a vendor not offering central deployment of updates is a pretty poor excuse).