I don't use anything cloud based and much of my shit isn't even allowed out to the internet.
It's a drop in the ocean, for too many say "But it's sooooo convenient and I've got nothing to hide" and open up all they got. Share camera's with amazon, email address book with facebook etc. not realizing nor caring I make an appearance in their instances too and I DO mind.
There are variouse alternatives to see what ports are open. Usually they autyo scan just the ip you come from, to avoid being used to scan a potential target.
If you want more, just use Greenbone. Run it twice. Once from another IP just to know how the world sees you. One time internal network and add accounts to greenbone allowing it to login and check further.
If you run linux, then Lynis is awesome to verify your config
Then don't go to the cloud! (or use encrypted storage if you really have to)
My view: Unless I can access the hardware 24/7/365 the data isn't mine for 'they' can deny me access to my data anytime while they keep full access. (hence store it decryped)
If source is whitelisted, Accept (avoid being locked out myself)
So all IP's are allowed to begin with, but some ("my" IP's like at home, my office etc) are on a whitelist ahead of everything else. They can't become blacklisted to avoid myself becoming locked out. Then it's the drop all on the blacklisted, followed by portscan detection. Only after that the 'normal' rules (allow https, smtp etc) begin.
And there is no increase on delay's or jitter compared to what i'm already facing on the WAN itself.
It keep's 6000+ hosts with possible harmful intend away from the ports I need/want open to the world. Actually, the router -while still being bored- offloads the services behind it. I really can't see a reason not to keep doing it. But, sure, it's a personal choice.
I only use their WiFi because I got some in- and outdoor ap's for free. The Wifi manager is selfhosted and has no internet access. For upgradesi downoad the deb file, trasnsfer and install.
It's not the best out there, but works for me and i'm still happy with it.
I'm using RouterOS. In the firewall rules you can create a rule that if an IP touches a port, it get added to a address list (optional with a time-out). So my FW rules begin like this:
If source is whitelisted, Accept (avoid being locked out myself)
If source IP is in the blacklist, drop all
if source IP tries to connect to port 21,22,25,137-139, 113 (and a bunch of others) add it to the blacklist
....
....
So using a portscanner will touch ports I'm not running any service on (like telnet) and you'll be blocked. A time-out of one week on the blacklist usually gives me an blacklist of 6500+ addresses.
This too has endless possibilities. t.ex. like port knocking. ('touch' one or more ports in a specified sequence in a specified time to be allowed to access the actual service port)
It does not. It does not uses ports at all. Fail2ban monitors your logfiles and activates the firewall to block IP's that matched your rules.
t.ex. You can block an IP that tried to access https://
<url>
/admin. You can block an IP that used wrong credentials x times to login on an ssh port. Or block one that tried to relay via your mailserver. The duration is configurable and alternative duration can be configured for recidivists.
And yes, you can whitelist IP's to avoid locking yourself out. The possibilities are endless.
Recent tv's became thin client's. Turn it on and it first need to download the app('s)