Skip to content

Latest commit

 

History

History
149 lines (101 loc) · 2.85 KB

File metadata and controls

149 lines (101 loc) · 2.85 KB

VPS Security Audit Report

Instructions: Copy this file to private/servers/<hostname>/AUDIT_REPORT.md and fill in the details. Findings should use the severity levels: CRITICAL, HIGH, MEDIUM, LOW, INFO.


Hostname: <hostname> IP: <ip address> OS: Kernel: Web Server: Audit Date: Uptime: Auditor:


Executive Summary

2–3 sentences summarizing overall risk posture and the top findings.

Overall Risk Posture: [ CRITICAL / HIGH / MEDIUM / LOW ]


Findings

CRITICAL

Issues that are actively exploitable or represent immediate serious risk.

C1. [Title]

  • Detail:
  • Evidence:
  • Impact:
  • Remediation:

HIGH

Significant vulnerabilities that should be addressed within days.

H1. [Title]

  • Detail:
  • Recommendation:

MEDIUM

Issues that increase attack surface or risk; address within 2–4 weeks.

M1. [Title]

  • Detail:
  • Recommendation:

LOW

Minor hardening improvements; address as time allows.

L1. [Title]

  • Detail:
  • Recommendation:

INFO

Observations and confirmations of good practices — no action needed.

I1. [Title]

  • Detail:

Prioritized Remediation Plan

Immediate (Today)

This Week

This Month


Hardening Checklist

SSH & Access

  • SSH key-based auth only (PasswordAuthentication no)
  • Root login disabled or key-only (PermitRootLogin no / prohibit-password)
  • X11 forwarding disabled
  • Non-root sudo admin user created and tested
  • Root SSH login disabled after admin user confirmed

Firewall

  • UFW active with default deny inbound
  • Only required ports open (SSH port, 80, 443)
  • No unexpected listening services

Intrusion Prevention

  • fail2ban installed and running
  • SSH jail active with appropriate thresholds
  • Apache jails configured (if applicable)

Apache

  • ServerTokens Prod set
  • ServerSignature Off set
  • mod_headers enabled
  • Security headers applied (HSTS, X-Content-Type-Options, Referrer-Policy, CSP)
  • .git / .svn access blocked
  • mod_status disabled or localhost-only
  • Options -Indexes on all vhosts

System

  • All pending security updates applied
  • Unattended-upgrades active
  • Kernel sysctl hardened (ICMP redirects, martian logging)
  • No world-writable files in web roots
  • No unexpected SUID binaries

TLS / Certificates

  • Valid cert on all vhosts
  • Auto-renewal working (certbot renew --dry-run)
  • HSTS header set with appropriate max-age

Monitoring

  • Log monitoring in place (Logwatch or equivalent)
  • fail2ban alert notifications working
  • Regular update reports scheduled

Notes

Additional observations, deferred items, or context.