7 Linux Security Mistakes I Made (So You Don’t Have To) | by Faruk Ahmed | Apr, 2025
Faruk

Faruk @cyberwebpen

About: InfoSec Analyst | 10+ yrs in DLP, CrowdStrike, QRadar, Qualys, Linux Admin, WebLogic Admin | Python & Bash Enthusiast | Passionate about cybersecurity, automation, and continuous learning.

Joined:
Apr 27, 2025

7 Linux Security Mistakes I Made (So You Don’t Have To) | by Faruk Ahmed | Apr, 2025

Publish Date: Apr 28
0 0

Member-only story

7 Linux Security Mistakes I Made (So You Don’t Have To)

--

Share

Intro:

When I started managing Linux servers, I focused on speed over safety. I just wanted things to work — and I didn’t always stop to think about security. Over time (and a few close calls), I learned the hard way that small oversights can become big vulnerabilities. Here are 7 Linux security mistakes I made so you don’t have to.

1. Leaving SSH on the Default Port (22)

I left SSH open on port 22, thinking “everyone uses it.” Turns out, bots scan that port constantly.

✅ Fix:

sudo nano /etc/ssh/sshd_config  # Change:Port 22 → Port 2210
Enter fullscreen mode Exit fullscreen mode

Then restart:

sudo systemctl restart sshd
Enter fullscreen mode Exit fullscreen mode

2. Allowing Root Login via SSH

I thought root login would save time. Instead, I was handing attackers a shortcut.

✅ Fix:

# In /etc/ssh/sshd_config:PermitRootLogin no
Enter fullscreen mode Exit fullscreen mode

3. Ignoring Open Ports

I never checked what was listening — bad idea. One service left exposed nearly cost me.

✅ Fix (Ubuntu & Red Hat):

ss -tuln
Enter fullscreen mode Exit fullscreen mode

4. Forgetting to Set…


👉 Read Full Blog on Medium Here

Comments 0 total

    Add comment