home.social

#system-hardening — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #system-hardening, aggregated by home.social.

fetched live
  1. I always remap my sshd daemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.

    And that's why my second line of defence is to disallow remote root login - and also make use of the AllowGroups feature in sshd_config. Users granted remote access must be member of a specific group. And root is also excluded from this group.

    That pays off these days. And this is a nice filter match for #fail2ban and similar tools

    termbin.com/0cf6

    I have 293 login attempts on "random users" since May 21. And 259 attempts as root.

    #infosec #ssh #sshd #systemhardening #kernel

  2. I always remap my sshd daemon to listen to a non-standard port, to reduce a lot of noise. Which has worked fine for years. But every now and then there are attempts. All the #Linux kernel flaws found lately has made remote login attempts more interesting for attackers. And they scan much more broadly now than just port 22.

    And that's why my second line of defence is to disallow remote root login - and also make use of the AllowGroups feature in sshd_config. Users granted remote access must be member of a specific group. And root is also excluded from this group.

    That pays off these days. And this is a nice filter match for #fail2ban and similar tools

    termbin.com/0cf6

    I have 293 login attempts on "random users" since May 21. And 259 attempts as root.

    #infosec #ssh #sshd #systemhardening #kernel

  3. Server Security Checklist — Essential Hardening Guide

    Securing your servers isn’t optional — it’s your first line of defense against data breaches, ransomware, insider threats, and lateral movement. Use this checklist as a baseline for Linux, Windows, cloud, hybrid, or on-prem servers.

    🔧 1. System & OS Hardening
    • Keep OS & packages updated (apply security patches frequently).
    • Remove / disable unused services & software.
    • Enforce secure boot + BIOS/UEFI passwords.
    • Disable auto-login and guest accounts.
    • Use minimal OS images only (reduce attack surface).

    🔐 2. Access Control
    • Enforce strong passwords & MFA everywhere.
    • Use RBAC & least privilege access.
    • Disable root/Administrator login over SSH/RDP.
    • Rotate credentials & keys regularly.
    • Implement just-in-time access for privileged users.

    🌐 3. Network Security
    • Restrict inbound/outbound traffic via firewalls.
    • Segment critical servers from general LANs/VLANs.
    • Disable unused ports & protocols.
    • Enable DoS/DDoS protection.
    • Apply zero-trust network principles.

    🔑 4. Secure Remote Access
    • Use SSH key-based authentication (disable password login).
    • Enforce VPN for admin access.
    • Log & monitor all remote access sessions.
    • Disable legacy protocols (Telnet, FTP, SMBv1).
    • Require bastion/jump host for critical access.

    📊 5. Logging & Monitoring
    • Enable centralized logging (syslog / SIEM).
    • Track failed login attempts & anomalies.
    • Configure alerts for privilege escalation or config changes.
    • Monitor log tampering.
    • Retain logs securely for audits & forensics.

    🔒 6. Data Protection
    • Encrypt data at rest (LUKS, BitLocker, etc.).
    • Encrypt data in transit (TLS 1.2+).
    • Strict database access policies.
    • Regular, offline, immutable backups.
    • Test restore procedures (don’t assume backups work).

    🔁 7. Application & Patch Management
    • Keep middleware, frameworks, and apps patched.
    • Delete default credentials & sample files.
    • Enable code signing for software packages.
    • Use secure coding practices (OWASP Top 10).
    • Implement dependency scanning (Snyk, Trivy, etc.).

    🛡️ 8. Malware & Intrusion Defense
    • Deploy EDR/AV on endpoints.
    • Enable IDS/IPS at network edge.
    • Automatic vulnerability scans (schedule weekly/monthly).
    • Monitor persistence techniques (cron, startup scripts).
    • Block known malicious IP ranges & TLDs.

    🏢 9. Physical & Cloud Security
    • Restrict physical access to server racks/rooms.
    • Enable provider security tools (AWS Security Groups, Azure NSG, IAM).
    • Harden cloud images (CIS benchmarks).
    • Review cloud logging & audit trails regularly.
    • Disable unused cloud API keys / roles.

    📜 10. Policy & Compliance
    • Use CIS / NIST / ISO-27001 benchmarks.
    • Track & document every access change.
    • Force annual access reviews & key rotation.
    • Perform regular security training for admins.
    • Maintain disaster recovery & incident plans.

    ➕ Additional 5 Critical Controls (Advanced Hardening)

    🧠 11. Privileged Access Management (PAM)
    • Use jump hosts & session recording.
    • Just-In-Time access for admins.
    • Store keys in secure vaults (HashiCorp Vault, CyberArk).

    🚨 12. Real-Time Threat Detection
    • Use behavioral analytics → UEBA/XDR.
    • AI-based anomaly detection recommended.
    • Block suspicious IPs automatically.

    🧪 13. Red Team & Pentesting
    • Run regular internal pentests.
    • Validate configuration weaknesses.
    • Simulate phishing + lateral movement scenarios.

    🧱 14. Container / VM Isolation
    • Use AppArmor, SELinux, Seccomp profiles.
    • Limit Docker socket access & root containers.
    • Scan images before deployment.

    📦 15. Automated Configuration Management
    • Use IaC (Terraform, Ansible, Puppet) for repeatable and secure builds.
    • Detect drift using compliance scanning.
    • Version control all infrastructure.

    🧠 Core Reminder

    A server is only as secure as the team who maintains it.
    Hardening isn’t one task — it’s an ongoing

    #ServerSecurity #SystemHardening #InfoSec #CyberSecurity #BlueTeam
    #DevSecOps #SysAdmin #ThreatDetection #AccessControl #NetworkSecurity
    #LinuxSecurity #SecureArchitecture #RiskMitigation #SecurityChecklist
    #CloudSecurity #InfrastructureSecurity #ZeroTrust #SecurityMonitoring

  4. I tried Lynis this time, and it gave me clearer suggestions which I was able to act upon, such as installing critical apt tools, and change file permissions to certain files.

    #Linux #cybersecurity #malware #systemhardening #tech