Someone: “… the new php vulnerability”
Me: “wait what, another one?”
S: “Yes”
I had exposed services for years, never a problem. I don’t have time to be on top of all of this. Im going random high port wireguard access only.
Someone: “… the new php vulnerability”
Me: “wait what, another one?”
S: “Yes”
I had exposed services for years, never a problem. I don’t have time to be on top of all of this. Im going random high port wireguard access only.
Every solution has its pros and cons. If you rely on something that requires public access (like randomly sharing access with others) than this is not a solution for you. With that said, you can go hybrid, anything high risk that you will never share with others (or only with a few predefined set of people that you can share a VPN config with) can go behind a VPN, anything you intend to share with others stays public but goes into a VM on a separate VLAN with restricted access to stuff to minimize the blast radius should sh*t go down. Personally this is what I’m trying to do, most things have been moved behind VPNs, only a few things remain public and I’m slowly moving them to separate VMs in a restricted network.