This content originally appeared on DEV Community and was authored by Faruk
Member-only story
Why I Always Disable Unused Services on Linux Servers
--
Share
When I take over a new Linux server, one of the first things I do is check which services are running . Why? Because every service left running is another potential door for attackers .
Here’s why disabling unused services is one of the fastest wins in hardening — and how I do it step by step.
🚨 The Risks of Leaving Services Running
- Increased Attack Surface An open port means someone can knock on it. Even if the service isn’t vulnerable today, it could be tomorrow.
- Privilege Escalation Paths Services running as root can become a direct route to full system compromise.
root- Resource Drain Unused daemons eat CPU, memory, and bandwidth for no reason. - Compliance Failures CIS Benchmarks, PCI-DSS, and HIPAA all require minimizing unnecessary services.
🔍 Step 1: Identify What’s Running
Check active services:
systemctl list-unit-files --type=service --state=enabled
Check open ports:
ss -tulnp
➡️ Any service listening externally that you don’t need is a candidate for shutdown.
👉 Read Full Blog on Medium Here
This content originally appeared on DEV Community and was authored by Faruk
Faruk | Sciencx (2025-09-24T18:27:00+00:00) Why I Always Disable Unused Services on Linux Servers | by Faruk Ahmed | Sep, 2025. Retrieved from https://www.scien.cx/2025/09/24/why-i-always-disable-unused-services-on-linux-servers-by-faruk-ahmed-sep-2025/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.