VPS security auditing and hardening
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Security auditing and automated hardening for remote servers.
/harden audit <host>Run security audit against a server. Checks:
/harden fix <host>Apply safe fixes that won't lock you out:
/harden emergency <host>Quick 10-minute hardening for new servers:
/harden report <host>Generate markdown security report.
| Option | Description |
|---|---|
--user=NAME | SSH user (default: root) |
--dry-run | Preview changes without applying |
/harden audit 192.168.1.100
/harden fix myserver.com --user=admin
/harden emergency vps.example.com --dry-run
/harden report server.io > security-report.md| Check | Pass Criteria |
|---|---|
| System Updates | 0 pending updates |
| Auto Updates | unattended-upgrades installed |
| Root Login | PermitRootLogin no |
| Password Auth | PasswordAuthentication no |
| Firewall | UFW active or iptables configured |
| Fail2ban | Service running |
| Uptime | < 90 days |
| Services | < 10 listening ports |
| Sudo Users | At least one non-root sudo user |
| MaxAuthTries | Set to 3 or less |
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.