Production Virtual Machine Hardening Policy
Purpose
Section titled “Purpose”This document outlines the security standards and configuration requirements for virtual machines (VMs) within our production infrastructure. These standards are designed to minimize security vulnerabilities and ensure consistent security practices across our VM fleet.
This policy applies to all virtual machines operated by the organization within the production environment.
Policy Requirements
Section titled “Policy Requirements”Operating System Standards
Section titled “Operating System Standards”- All public facing VMs should run a stable version of Ubuntu, with the version number being equal or greater to the most recent LTS
- Security patches must be applied at minimum every 14 days by means of the provisioning of a new base container
- System updates must be automatically logged for audit purposes
System Monitoring and Auditing
Section titled “System Monitoring and Auditing”Audit Daemon Configuration
Section titled “Audit Daemon Configuration”- Auditctl must be installed and configured on all VMs
- The following events must be monitored and logged:
- File system changes to critical system files
- SSH connection attempts (successful and failed)
- Privilege escalation events
- Changes to system configuration
- Alert reporting must be configured for:
- Unauthorized privilege escalation attempts
- Failed SSH authentication attempts exceeding defined thresholds
- Modifications to critical system files
Antivirus Protection
Section titled “Antivirus Protection”- ClamAV must be installed and configured on all VMs
- Real-time monitoring must be enabled for:
- File system changes
- New file creation
- File modifications
- Virus definition updates must occur on every new deploy
- All detected threats must generate immediate alerts
Network Security
Section titled “Network Security”Network Access Controls
Section titled “Network Access Controls”- VMs must be categorized as either:
- Private: Accessible only through WireGuard VPN or Cloudflare ZeroTrust
- Public: Limited exposure through Fly proxy
- For public-facing VMs:
- Only explicitly required ports may be exposed
- All exposed ports must be documented and justified
Firewall Configuration
Section titled “Firewall Configuration”- Host-based firewall must be enabled
- Default deny all inbound connections
- Explicit rules required for all allowed connections
- Regular firewall rule audits must be performed
System Hardening
Section titled “System Hardening”Package Management
Section titled “Package Management”- Unnecessary system packages should be removed
- Package installation requires approval process
- Regular audits of installed packages must be performed
Service Management
Section titled “Service Management”- Only required services may be enabled
- All enabled services must be documented
- Regular service audits must be performed
Policy Review
Section titled “Policy Review”- This policy will be reviewed annually and updated as necessary to reflect changes in our systems, processes, or regulatory requirements.
Internal & Confidential: This page is only available in the internal handbook and contains confidential information.
