https://mecanik.dev/en/tags/server-security/Recent content in Server Security on [ MECANIK DEV ]Hugo -- gohugo.ioenCopyright © 2020-{year} by [ MECANIK DEV ]. All Rights Reserved.Tue, 07 Jul 2026 07:00:00 +0100https://mecanik.dev/en/posts/linux-server-hardening-guide-2026/Tue, 07 Jul 2026 07:00:00 +0100https://mecanik.dev/en/posts/linux-server-hardening-guide-2026/A default Linux install is convenient, not secure. Hardening is the process of reducing a server’s attack surface and tightening its configuration so that the inevitable probing from the internet finds nothing easy to exploit. This guide covers the hardening steps that matter most in 2026, in a sensible order of priority. TL;DR SSH is your biggest exposed surface: use key-based authentication, disable root login and passwords, and rate-limit connections Run a default-deny firewall and shut down every service and port you do not need Keep the system patched automatically, and apply kernel and account hardening Use SELinux or AppArmor, enable audit logging, and measure yourself against the CIS Benchmark for your distribution 1.https://mecanik.dev/en/posts/wordpress-security-hardening-checklist-2026/Mon, 06 Jul 2026 19:00:00 +0100https://mecanik.dev/en/posts/wordpress-security-hardening-checklist-2026/WordPress powers a huge share of the web, which makes it a constant target. The good news is that the overwhelming majority of WordPress compromises exploit a small, predictable set of weaknesses, and almost all of them are preventable. This WordPress security hardening checklist walks through the steps that actually move the needle in 2026, roughly in priority order. TL;DR Vulnerable and outdated plugins and themes are the single biggest WordPress attack vector; disciplined updates and removing unused code matter more than anything else Strong authentication (unique admin usernames, strong passwords, two-factor, login rate limiting) closes the second most common door Harden wp-config.