Is port 22 (SSH) safe to expose?
Secure Shell — remote login and file transfer on Linux and network devices. Exposing it to the internet is high risk.
Why exposing port 22 is risky
The most brute-forced port on the internet. Weak or reused passwords, and old OpenSSH CVEs, make an exposed SSH port a direct way in.
How to check if it's exposed
From outside your network, a quick nmap -p 22 <your-ip> (or an external port scanner) shows whether 22 answers. On the host, ss -tlnp | grep :22 shows what's listening and on which interface — it should be a private address, not 0.0.0.0.
How to secure it
- Use key-only authentication and disable password login and root login.
- Restrict the source to your office/VPN, or reach it through a bastion.
- Keep OpenSSH patched.
SkyShield watches what's really exposed
SkyShield follows your firewall rules through to the container and shows what the internet can actually reach. Free for one server, then from $49 per server a month. Start free.