@bmeeks:
@jpvonhemel:
Hi Bill,
I do have SSH enabled with keys and passwords disabled. I thought this was secure and my port is not the typical 22. I understand that a port scan would reveal my open ports and figured it was secure using the key pair. I will take your advise and consider closing this port and accessing ssh via openVPN. That goes for the web admin too.
I don't block anything with snort, just log and review. I do see a snort alert on WAN when I ssh in. What was odd about my AWS/Twitter IP addresses was my public IP and port 10022 were the source and I didn't know how to make sense of it. Source ports are usually random, or at least I thought they were. It was odd that my public ip/10022 was sending to AWS/Twitter at port 443
Anyway, I have disabled the WAN interface for Snort and will just watch out for LAN alerts.
I appreciate your help.
Jerold
Using SSH with keys is much better than a password. A key can be OK, but you will see a constant stream of attempts if the bots find the open port. Without the key they should be kept out. If all you ever want is SSH, I guess for a home network key-driven logins are OK. Personally I use the OpenVPN server on pfSense and a client to access my network remotely. I then open select things from the VPN into my LAN.
Bill
Bill,
Great information! first time I am trying to setup snort.
I do agree that having OpenVpn open is the best way and access everything else behind it, but is OpenVPN protected against brute force attacks in snort by default or you have to set that up?