Why I don't change SSH from port 22
Dreams of Code
Sep 29, 2024 15:00
Create an account to hide videos, mark them watched, or save them to Don't Miss.
Create an account to hide videos, mark them watched, or save them to Don't Miss.
Create an account to hide videos, mark them watched, or save them to Don't Miss.
Chapters
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:
https://www.youtube.com/channel/UCWQaM7SpSECp9FELz-cHzuQ/join
Join Discord: https://discord.com/invite/eMjRTvscyt
Join Twitter: https://twitter.com/dreamsofcode_io
Video Links:
- Okta STO: https://www.okta.com/identity-101/security-through-obscurity/
- Privileged ports: https://www.w3.org/Daemon/User/Installation/PrivilegedPorts.html
- Elastic Rule: https://www.elastic.co/guide/en/security/current/potential-non-standard-port-ssh-connection.html
- Fail2ban: https://github.com/fail2ban/fail2ban
- DIgital Ocean Harden SSH: https://www.digitalocean.com/community/tutorials/how-to-harden-openssh-on-ubuntu-20-04
- Shodan: https://www.shodan.io/
- GreyNoise SSH Bruteforcer: https://viz.greynoise.io/tags/ssh-bruteforcer-attempt?days=30
Entertainment