Why I don't change SSH from port 22

To try everything Brilliant has to offer—free—for a full 30 days, visit https://brilliant.org/DreamsofCode . You’ll also get 20% off an annual premium subscription.

This video was sponsored by Brilliant.

If you're running a server with SSH on it, then hardening ssh is an important step to improving your system security. One approach to hardening SSH that many users perform is to change ssh off of the standard port of 22 onto something else.

In my case however, I tend not to do this, as I feel it's security through obscurity and ineffective. Not only does it not work, but, it can also cause other issues...

Become a better developer in 4 minutes: https://bit.ly/45C7a29 👈

Join this channel to get access to perks:
   / @dreamsofcode  

Join Discord:   / discord  
Join Twitter:   / dreamsofcode_io  

Video Links:
Okta STO: https://www.okta.com/identity-101/sec...
Privileged ports: https://www.w3.org/Daemon/User/Instal...
Elastic Rule: https://www.elastic.co/guide/en/secur...
Fail2ban: https://github.com/fail2ban/fail2ban
DIgital Ocean Harden SSH: https://www.digitalocean.com/communit...
Shodan: https://www.shodan.io/
GreyNoise SSH Bruteforcer: https://viz.greynoise.io/tags/ssh-bru...

00:00:00 - Intro
00:00:54 - Sponsor
00:02:17 - Security through obscurity
00:03:42 - It's only a matter of time
00:05:30 - Not all ports are the same
00:07:56 - Complexity is the enemy of security
00:08:25 - Obscurity as an indentifier
00:09:05 - Port Privilege
00:09:43 - More security issues
00:10:58 - Why I don't change the ssh port
00:11:27 - Other approaches to reduce log spam