Skip to content

Proposal: Add “Security & Hardening” section to Monad Ops Track #293

Description

@Asplana92

🛡️ Proposal: Security & Hardening Track for Monad Ops

While operating a public Monad RPC node, I noticed thousands of unauthorized SSH attempts and automated scans every week.
This shows that public infrastructure needs not only monitoring — but also proactive protection.

🔍 Observations

  • 7,000+ failed SSH attempts detected in one week (fail2ban-client status sshd)
  • Repeated scan activity from multiple regions (IPs auto-banned)
  • Unauthorized HTTP/RPC probes targeting public endpoints

🔐 Suggested Content for Security Track

Add a short “Security & Hardening” section to the Ops track covering:

  • UFW firewall configuration — only allow 80/443
  • Fail2Ban setup — auto-ban repeated SSH login attempts
  • Health timers — auto-restart RPC if unresponsive
  • Unattended-upgrades — automatic security patches
  • Basic monitoring metrics for banned IPs and intrusion attempts

🧰 Example setup

  • Ubuntu 24.04 (Hetzner VPS)
  • Fail2Ban + UFW + systemd timers
  • Public RPC endpoint: monad.skandicescape.online
  • Monitoring stack: Prometheus + Grafana + Nginx Exporter

📊 Example log output

sudo fail2ban-client status sshd
|- Currently banned: 55
|- Total failed: 7028
`- Total banned: 563

🌐 Author

asplana92 | Web3 Infra Builder

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions