wslmanager

Security Hardening Guide for wslmanager

Least-privilege permissions

• Run the tool with minimal user rights: Avoid using administrator or "run as admin" mode unless absolutely necessary; use a standard user account with only WSL access granted.
• Restrict AI agent scope: Configure the MCP connector to allow only read-only operations (viewing distros, checking status) by default; require explicit approval for risky actions like deletion or backup restore.
• Lock down SSH access: If using remote SSH to control WSL, disable password login and require SSH keys; limit SSH connections to trusted IP addresses only.
• Separate backup credentials: Store backup encryption passwords and SSH keys in a dedicated secrets manager (e.g., Windows Credential Manager, 1Password, Bitwarden); never embed them in scripts or configuration files.

Network isolation

• Disable remote MCP unless needed: Keep the MCP server (agent communication interface) listening only on localhost (your own machine) by default; only expose it over SSH with strict firewall rules if remote access is required.
• Use VPN or firewall for SSH access: If accessing wslmanager remotely over SSH, route traffic through a corporate VPN or firewall that restricts which devices and users can connect.
• Encrypt all data in transit: Ensure SSH connections use encryption (enabled by default); for backups sent over the network, enable encryption at rest and in transit.
• Segment your network: Keep WSL environments and the wslmanager host on a separate network segment (VLAN) from general office systems to limit spread of any breach.

Monitoring

• Log all operations: Enable audit logging (if available) to track who launched backups, deleted distros, or modified configurations; review logs weekly for suspicious activity.
• Monitor distro access: Watch for unexpected SSH logins, file access, or process execution within your WSL distros; use host-based security tools (e.g., Windows Defender for Endpoint).
• Alert on privilege changes: Set up notifications if the wslmanager tool or related processes suddenly request administrator rights.
• Track credential use: Monitor for unusual or failed authentication attempts to SSH keys or backup passwords; alert if credentials are used from unexpected locations or times.

Red flags to watch for

• Unverified updates: Before installing a new version of wslmanager, verify the source on GitHub (check the official repository URL); do not download from third-party sites or mirrors without confirming authenticity with the maintainer.
• Unexpected prompts from AI agents: If an AI assistant suggests deleting, exporting, or modifying distros after a vague or odd user request, pause and review the command manually before confirming.
• Backup files without encryption: If wslmanager exports distro backups as plain uncompressed folders or archives, move them immediately to an encrypted disk or password-protected storage.
• Distro or agent behavior changes: If a WSL distro or the MCP connector begins making unexpected network connections, creating new user accounts, or accessing files outside its normal scope, isolate the system and investigate for tampering.