System Hardening Checklist
|About this System Hardening Checklist Page|
Contributor maintained wiki page.
Whonix comes with many security features. Whonix is Kicksecure™ Hardened by default and also provides extensive Documentation including this System Hardening Checklist. The more you know, the safer you can be.
This page is targeted at users who wish to improve the security of their systems for even greater protection.
It is possible to significantly harden the Whonix and/or host platform. This reduces the likelihood of a temporary or persistent compromise, while increasing the chances of successful, anonymous activity. Hardening is dependent upon a user's skill set, motivation and available hardware. The checklist below is intended to provide a quick overview of important issues, categorized by difficulty level - easy, moderate, difficult and expert.
Anonymous Blogging, Posting, Chat, Email and File Sharing
- To remain anonymous, follow all the Whonix recommendations to minimize threats of keyboard/mouse biometrics, stylometric analysis and other covert channels.
- A browser is an unsafe environment to directly write text, regardless of whether it is a forum post, email, webmail or IMAP-related reply.
- A browser is an unsafe environment to directly write text, regardless of whether it is a forum post, email, webmail or IMAP-related reply.
- Remove metadata from documents, pictures, videos or other files before uploading them to the Internet.
- Think twice before sharing "anonymous" photos due to unique embedded noise signatures that have no known countermeasures.
- Be careful sharing anonymous documents. Digital watermarks with embedded covert data are robust, so run documents through Optical Character Recognition (OCR) before sharing the output.
- Utilize OnionShare to anonymously share or receive files securely over the Tor network, anonymously chat, or host anonymous websites. 
Command Line Operations
- Do not run commands unless they are completely understood -- first refer to a suitable Whonix wiki resource if available.
- If root privileges are required, run the command with
sudorather than logging in as root or using
sudo su. 
- Consider disabling the root account permanently. 
- To prevent malware sniffing the root password, before performing administrative tasks that require root access, create an
adminuser account with sudo permissions.
sudoeditfor better security when editing files. 
- Defeat login spoofing by using the Secure Access Key ("Sak";
- Consider enabling SysRq "Security Keys" functionality as insurance against system malfunctions -- this assists in system recovery efforts and limits the potential harm of a malware compromise.
Disabling and Minimizing Hardware Risks
- Unplug external devices when not needed.
- Consider disabling microphones where possible (muting on the host) or better, physically removing them.
- Since speakers (all audio output devices) can be turned into microphones , if possible, physically remove speakers on the host and remove/disable the beeper . 
- Preferably detach webcams or even better, physically cover webcams with a sticker or switch unless they are in use.
- If using Qubes-Whonix, assign the webcam to an untrusted VM (if needed).
- Avoid using wireless devices, since they are insecure.
- Preferably disable or remove Bluetooth hardware modules.
- Disable or remove problematic devices like ExpressCard, PCMCIA, FireWire or Thunderbolt which may allow attackers with physical access to read RAM.
- Do not enable audio input to any VM unless strictly required.
- Apply CPU microcode updates . 
- Consider restricting hardware information to the root user in Whonix. 
- In Qubes-Whonix, only use a mouse and keyboard utilizing PS/2 ports (not USB ports) to prevent malicious compromise of dom0 (PS/2 adapters and available controllers are required).
- To mitigate against inadequate entropy seeding by the Linux Random Number Generator (RNG), it is recommended to install daemons that inject more randomness into the pool.
For high security, it's best to use a dedicated, physically different computer only for the purpose of using Whonix and nothing else. For other use cases, use completely different hardware including a different screen.
This is to lower the impact of fingerprinting VMs in case they get ever compromised.
Related: VM Fingerprinting
Forum discussion: https://forums.whonix.org/t/high-opsec-recommendation/17237
- In File Manager, disable previews of files from untrusted sources. Change file preferences in the Template's File Manager so future App Qubes inherit this feature.
- Files received or downloaded from untrusted sources (the internet, via email etc.) should not be opened in a trusted VM. Instead, open them in a Disposable:
Open In Disposable
- Untrusted PDFs should be opened in a Disposable or converted into a trusted (sanitized) PDF to prevent exploitation of the PDF reader and potential infection of the VM.
File Folder Permissions
- Linux user account
nobodyhas no special meaning.
- Also linux user group
nogrouphas no special meaning either.
- Therefore the user should avoid running programs under user
nogroupas well as avoid setting file or folder permissions to that user / group.
File Storage Location
- Avoid storing files directly in the root home folder and create appropriate sub-folders instead.
- Move files downloaded by Tor Browser from the
~/Downloadsfolder to another specially created one. 
Mandatory Access Control
- Enable all available apparmor profiles in the Whonix-Workstation™ and Whonix-Gateway™ Templates.
- Enable seccomp on Whonix-Gateway (
- Since the mobile devices security best practices for risk mitigation are often difficult / infeasible to adhere to, it might be easier to physically move all mobiles devices to a distant physical location such as a different room and close the door and/or to power off mobile devices.
Passwords and Logins
- Use strong, unique and random passwords for all online accounts, system logins and encryption / decryption purposes to prevent the feasibility of brute-forcing attacks.
- Use a trusted password manager (KeePassXC) , so hundreds of different passwords can be kept stored in an encrypted password database, protected by one strong master password. 
- For high-entropy passwords, consider using Diceware passphrases. 
- In Qubes-Whonix, store all login credentials and passwords in an offline vault VM (preferably with KeePassXC) and securely cut and paste them into the Tor Browser. 
- Read and follow all the principles for stronger passwords.
- At a minimum, lock the screen of the host when it is unattended.
- For better security, shut down the computer entirely -- screensavers are notoriously insecure.  
- Download Internet files securely using scurl instead of wget from the command line.
- When downloading with Tor Browser, prevent SSLstrip attacks by typing
https://links directly into the URL / address bar.
- Prefer onion services file downloads, which provide greater security and anonymity than https.
Secure Qubes Operation
- Refer to the Qubes-Whonix security recommendations and always follow the latest security news and advice from the Qubes team.
Secure Software Installation
- Default to Debian's official package manager APT for installing software, and avoid third party package managers.
- When possible, use mechanisms which simplify and automate software upgrades and installations, like apt functions.
- Prefer installation of software from signed (Debian) GNU/Linux repositories and avoid manually installing software, particularly if it is unsigned.
- Set the Qubes, Debian and Whonix package updates to Tor onion service repositories. 
- For safer installations or updates, first stop all activity/applications and rotate the Tor circuits .
- Always verify key fingerprints and digital signatures of signed software before importing keys or installing software.
- Operating System Updates: It is crucial to regularly check for operating system updates on the host operating system, and both the Whonix-Workstation and Whonix-Gateway.
- Stay tuned: It is absolutely crucial to subscribe to and read the latest Whonix news category 'important-news' to stay in touch with ongoing developments. This way users benefit from notifications concerning important security advisories, potential upgrade issues and improved releases which address identified issues, like those affecting the updater or other core elements. Follow Whonix Developments.
- Debian Security Announcements: Since Whonix is based on Debian, users should consider subscribing to the Debian security announcement mailing list to stay informed about the latest security advisories. See also chapter Debian Security Announcements.
Tor Browser Series and Settings
- Prefer the stable Tor Browser release over the alpha series in line with Tor developer recommendations; see footnotes.    
- Run the Tor Browser Security Slider in the highest position. 
- Do not configure custom NoScript (per-site) settings which persist across successive Tor Browser sessions because this aids fingerprinting.
- Use .onion services where possible to stay within the Tor network, such as defaulting searches to the DuckDuckGo onion service. 
- Use multiple Tor Browser instances or multiple Whonix-Workstation to better compartmentalize contextual identities.
- Follow all other Whonix recommendations for safe and anonymous use of Tor Browser.
- Install Tor Browser outside of Whonix so a second, working instance is always available for anonymous activities. 
- Remove the virtual audio controller to VMs from getting access to a microphone (eavesdropping risk) or speaker (profiling threat).
- Remove a host of VirtualBox features to reduce the attack surface.
- Take regular, clean VM snapshots that are not used for any activities.
- Spoof the initial virtual hardware clock offset.
- Consider disabling clipboard sharing to reduce the risk of identity correlation. 
- Shared folders are discouraged because they weaken isolation between the guest and the host. 
- Learn more about warrant canaries -- see Whonix Warrant Canary (forum discussion) and limitations of warrant canaries.
Create a USB Qube
Host Operating System Distribution
- For a truly private operating system, install GNU/Linux on the host. 
- The Debian distribution is recommended by Whonix as providing a reasonable balance of security and usability.
Host Operating System Hardening
- Use Full Disk Encryption (FDE) on the host.
- Apply a BIOS password for BIOS setup and boot.
- Torrify APT traffic on the host to prevent fingerprinting and leakage of sensitive security information.
- Follow all other Whonix recommendations to further harden the host OS against physical attacks.
- Harden the host Debian Linux OS.
Kernels / Kernel Modules
- To benefit from additional protections,  consider installing newer kernels.
- Consider installing the Linux Kernel Runtime Guard (LKRG) kernel module for improved detection and protection against common kernel exploits. 
- In Qubes-Whonix, consider installing the tirdad kernel module to protect against TCP ISN-based CPU information leaks.  
- Advanced users can undertake host kernel hardening to significantly increase security and privacy.
- Consider running Whonix with Live Mode in a VM or even better in Whonix as HOST os, so all writes go to RAM instead of the hard disk.
- If Debian is run as the host OS, consider also booting into Live Mode.
- Disable swap and program crash dumps as an anti-forensics precaution.
- When using Live Mode in a VM, consider enabling read-only hard drive mode to make it harder for malware to gain persistence. 
- Consider installing a hardened memory allocator ('Hardened Malloc') to launch regularly used applications. 
- If possible, use a dedicated network connection (LAN, WiFi etc.) that is not shared with other potentially compromised computers.
- If using a shared network via a common cable modem/router or ADSL router, configure a de-militarized zone (perimeter network). 
- Test the LAN's router/firewall with either an internet port scanning service or preferably a port scanning application from an external IP address.
- Change the default administration password on the router to a unique, random, and suitably long Diceware passphrase to prevent bruteforcing attacks.
- WiFi users should default to the WPA2-AES or WPA3 standard; the protocols are safer and have stronger encryption.  
- Follow all other Whonix recommendations to lock down the router.
- Disable TCP SACK to limit the risk of remote DoS and other attacks.
- Prefer the Debian Template for networking (
sys-firewall) since it is minimal in nature and does not "ping home", unlike the Fedora Template. 
- Consider using customized minimal templates for NetVMs to reduce the attack surface and memory requirements. Four options are currently available:
- For greater security, higher performance and a lower resource footprint, consider using an experimental MirageOS-based unikernel firewall that can run as a QubesOS ProxyVM.
- Consider utilizing OpenBSD for
sys-netto reduce the attack surface.  See also other OpenBSD considerations.
- Consider using Firejail to restrict Tor Browser, Firefox-ESR, VLC and other regularly used applications -- note this comes with an increased fingerprinting risk and any vulnerability in Firejail can allow escalation to root privileges. 
- In a future Non-Qubes-Whonix release, consider using
sandbox-app-launcher(Sandboxed Application Launcher) to restrict applications within a bubblewrap sandbox and confined by AppArmor. 
Spoof MAC Addresses
- In Qubes-Whonix, follow these steps to spoof the MAC address on the Debian or Fedora Template used for network connections.
- In Non-Qubes-Whonix, follow these steps to spoof the MAC address of the network card on a Linux, Windows or macOS host.
- Non-Qubes-Whonix only: Disable ICMP timestamps and TCP timestamps on the host operating system to prevent leakage of information. 
- Non-Qubes-Whonix only: Uninstall the NTP client on the host operating system and disable systemd's timdatectl NTP synchronization feature. 
- Prevent possible time leaks by blocking networking until sdwdate finishes.
- Consider enabling Tor connection padding for potentially better anonymity; note it is unclear whether this provides any additional benefit (see footnote). 
- Consider installing newer Tor versions directly from The Tor Project repository.
- Avoid regenerating the Tor state file or manually rotating Tor guards  because it degrades anonymity.
- Avoid configuring non-persistent entry guards, as this severely degrades anonymity.
- Consider using Bridges if Tor is censored, dangerous or deemed suspicious in your location.
- If using a bridge, configure alternating bridges for different physical locations.
- Heavily censored users should configure a meek-azure bridge with Anon Connection Wizard. 
- To help preserve anonymity, copy Tor configuration files and settings to any new
sys-whonixinstance which is created. 
Whonix VM Security
- Consider disabling the Control Port Filter Proxy to reduce the attack surface of both the Whonix-Gateway and Whonix-Workstation.
- Consider hardening systemcheck.
- Consider the periodic deletion and recreation of VMs that are used for sensitive operations.
- If a compromise of Whonix-Gateway and/or Whonix-Workstation is suspected, follow the compromise recovery instructions.
- Consider the Android Haven application for sensitive devices -- motion, sound, vibration and light sensors can monitor and protect physical areas. 
- If a Trusted Platform Module (TPM) is available, enable it in BIOS/UEFI and configure the required services to protect against Evil Maid Attacks.
- See Kicksecure™ AEM Documentation
Chaining Anonymizing Tunnels
- Avoid this course of action. The anonymity benefits are unproven and it may actually hurt a user's anonymity and security goals.
- Virtual Private Network (VPN) tunnel-links are strongly recommended against due to multiple security and anonymity risks.
- Run all instances of Tor Browser in a Disposable which is preferably uncustomized to resist fingerprinting. 
- Configure each ServiceVM as a static Disposable to mitigate the threat from persistent malware accross VM reboots. 
- Until fully ephemeral Disposables are available by default in a future Qubes release, advanced users can consider configuring them manually:
- Follow the Whonix recommendations to select an email provider compatible with privacy and anonymity.
- For anonymous PGP-encrypted email over Tor, use Mozilla Thunderbird. 
- For greater email or message security, consider using the OneTime application or a Physical One-time Pad for military-grade encryption.
- Follow all other email principles for greater safety.
- Use split-GPG for email to reduce the risk of key theft used for encryption / decryption and signing.
- Create an App Qube that is exclusively used for email and change the VM's firewall settings to only allow network connections to the email server and nothing else ("Deny network access except...").
- Only open untrusted email attachments in a Disposable to prevent possible infection.
Ethernet/FDDI Station Activity Monitor
- Consider running ArpON as a daemon to defend against ARP attacks like ARP spoofing, ARP cache poisoning and ARP poison routing. 
- Consider utilizing Arpwatch to be alerted about any changes to the database of Ethernet MAC addresses seen on the network. 
Flash the Router with Opensource Firmware
- Flash the insecure, limited-utility, proprietary firmware on the router with a powerful, open-source GNU/Linux alternative.
Mix Personal Tor Traffic with Own Tor Bridge or Relay
- See Host a Bridge or Tor Relay; this configuration might make adversary classification of Tor traffic more difficult. 
Multi-Factor User Authentication
- Set up two-factor authentication (2FA) to strengthen the security of online accounts, smartphones, web services, access to physical locations and other implementations.
- Configure PAM USB as a module that only allows user authentication by inserting a token (a USB stick), in which a one-time password is stored.
- For secure account logins, utilize a Nitrokey hardware authentication device which supports one-time passwords, public-key encryption, and the Universal 2nd Factor (U2F) and FIDO2 protcols.
- Qubes: Check the YubiKey (will be not much different from Nitrokey) instructions to enhance the security of Qubes user authentication, mitigate the risk of password snooping, and to improve USB keyboard security.
- Create drop-in
.conffiles to sandbox systemd services.
Whitelisting Tor Traffic
- Qubes-Whonix: Configure
sys-whonixto use corridor as a filtering gateway to ensure only connections to Tor relays pass through.  
- Non-Qubes-Whonix or Qubes-Whonix: Use a standalone corridor as a filtering gateway.
Disable Intel ME Functionality
- It is possible to partially deblob Intel's despicable ME firmware image by removing unnecessary partitions from it.
- Alternatively, Intel ME's "High-Assurance Platform" mode can be set manually to disable most ME capabilities.
Disable SUID-enabled Binaries
- Consider enforcing the SUID Disabler and Permission Hardener to increase the security of the system; see here for instructions. 
- Libreboot is no longer recommended as a proprietary firmware alternative; see footnote. 
- Coreboot is a possible BIOS/UEFI firmware alternative -- consider purchasing hardware that has it pre-installed (like Chromebooks), or research flashing procedures for the handful of refurbished motherboards that support it.
- Exception: Several laptops meet Qubes' Certified Hardware requirements and are configured with Coreboot, Heads and a partially disabled Intel Management Engine.
- OnionShare 2.0 and higher enforce v3 onion connections. Whonix 16 is based on Debian
bookwormwhich provides OnionShare v2.2.
- This reduces the likelihood of a successful root or non-root user compromise.
- Whonix 16 and later versions disable the root account by default.
This addresses spying techniques:
- SPEAKE(a)R: Turn Speakers to Microphones for Fun and Profit
- relying on watermarked, (in)audible sounds that can link multiple devices, as well as headphones/speakers being covertly used as a microphone.
- This applies to both Intel and AMD architecture.
- While this may introduce new vulnerabilities, this is objectively better than running a system that is vulnerable to known attacks.
- This hides hardware identifiers from unprivileged users.
- sudo apt install jitterentropy-rngd
- sudo apt install haveged
- The reason is AppArmor profiles (and possibly other mandatory access control frameworks) are unlikely to allow access to these folders by default.
- Debian KeePassXC package.
- For greater security, store the password manager off-line.
- To estimate strength, an 8-word Diceware passphrase provides ~90 bits of entropy, while a 10-word passphrase provides ~128 bits of entropy.
- For greater safety, copy something else into the clipboard after pasting so the password is purged and cannot be accidentally pasted elsewhere.
- For example, sensitive notifications (pop up dialog boxes) can appear over the screensaver while locked, and screensaver bypass bugs are common. Screen Locker (In)Security - Can we disable these at least 4 backdoors?
- Also see: Disconnecting a video output can cause XScreenSaver to crash (QSB-068, CVE-2021-34557).
- The Whonix and Debian repositories are no longer set to onion mirrors by default due to stability issues. This decision will be reviewed in the future once v3 onions have further matured.
- If a keyserver is required, utilize the v3 onion address for
- Tor Blog:
Note: this is an alpha release, an experimental version for users who want to help us test new features. For everyone else, we recommend downloading the latest stable release instead.
- Selfrando (load-time memory randomization) protection has been removed from alpha Tor Browser Linux builds. Although Selfrando provides a security improvement over standard address space layout randomization (ASLR) present in Tor Browser and other browsers, Tor developers believe it is relatively easy for attackers to bypass and not worth the effort.
- The "hardened" Tor Browser series has been deprecated, see: https://gitlab.torproject.org/legacy/trac/-/issues/21912
- Following the official release of the v8.0+ Tor Browser series (based on Firefox 60 ESR), the stable and alpha Tor Browser versions both have a native sandbox.
- This may affect usability and proper functioning on some websites.
- Take care to observe you stay within the Tor network -- 'downgrade' attacks have been observed that result in clearnet URLs being loaded in place of onion services across successive page loads on some sites.
- Thereby circumventing any possible future problems, like the breakage of Whonix.
- Bidirectional clipboard sharing is currently enabled by default in Whonix VirtualBox VMs. There are security reasons to disable clipboard sharing, for example to prevent the accidental copying of something (non-)anonymous and pasting it in its (non-)anonymous counterpart such as a browser, which would lead to identity correlation.
- Providing a mechanism to access files of the host system from within the guest system via a specially defined path necessarily enlarges the attack surface and provides a potential pathway for malicious actors to compromise the host.
- A USB qube is automatically created as of Qubes R4.0.
- USB keyboards and mice expose dom0 to attacks, and all USB devices are potential side channel attack vectors.
- Windows and macOS are surveillance platforms that do not respect user freedom or privacy.
- Kicksecure™ has an advanced multi-layer defense model, thereby providing in-depth security. In its default configuration, Kicksecure™ provides protection from many types of malware, with no customization required.
- The Truth about Linux 4.6:
The real "hard truth" about Linux kernel security is that there's no such thing as a free lunch. Keeping up to date on the latest upstream kernel will generally net all the bug fixes that have been created thus far, but with it of course brings completely new features, new code, new bugs, and new attack surface. The majority of vulnerabilities in the Linux kernel are ones that have been released just recently, something any honest person active in kernel development can attest to.
- Whonix contributor madaidan has noted:
LTS kernels have less hardening features and not all bug fixes are backported but it has less attack surface and potentially less chance of having bugs. Stable kernels have more hardening features and all bug fixes but more attack surface and more bugs.
- Including grsecurity elements being mainlined by the Kernel Self Protection Project.
- This will likely become the default in future, see: Simplify and promote using in-vm kernel.
- Do not raise Qubes VM Kernel issues at Whonix. Instead, contact Qubes support.
... LKRG attempts to post-detect and hopefully promptly respond to unauthorized modifications to the running Linux kernel (integrity checking) or to credentials (such as user IDs) of the running processes (exploit detection). For process credentials, LKRG attempts to detect the exploit and take action before the kernel would grant the process access (such as open a file) based on the unauthorized credentials.
- The TCP Initial Sequence Numbers (ISNs) are randomized.
- tirdad is installed in Non-Qubes-Whonix by default.
- This prevents remounting of the hard drive as read-write.
- This provides hardening against heap corruption vulnerabilities and improves overall memory performance and usage. Note that using Hardened Malloc with Tor Browser or Firefox is difficult and unsupported.
- This restricts Whonix-Gateway accessibility to/from other nodes on the network such as printers, phones and laptops.
- WPA3 protocol improvements include:
- Protection against brute force “dictionary” attacks -- adversaries cannot make multiple login attempts with commonly used passwords.
- Stronger encryption: WPA2 relies on a 64-bit or 128-bit encryption key, but WPA3 uses 192-bit encryption.
- Use of individualized data encryption in open networks to strengthen user privacy.
- Forward secrecy: if an adversary captures encrypted Wi-Fi transmissions and cracks the password, they cannot use it to read older data.
- Do not rely on WiFi Protected Set-up (WPS), which has major security flaws.
- Example: sudo qvm-template install centos-8-minimal
- Example: sudo qvm-template install debian-12-minimal
- Example: sudo qvm-template install fedora-36-minimal
Qubes tracker: Use OpenBSD as NetVM. OpenBSD is assessed as having a lower attack surface than Linux, uses less system resources, and has strong exploit mitigations. Note that OpenBSD cannot currently be configured as
- Previously The Tor Project's alpha sandbox was recommended to restrict Tor Browser, but the project has unfortunately been abandoned.
- Although not implemented yet, all user-installed applications will be automatically configured to run in the sandbox and a prompt will ask which permissions should be granted to the application.
- Such as system information, host time, system uptime, and fingerprinting of devices behind a router.
- This prevents time-related attack vectors which rely on leakage of the host time.
- Via creation of a new Whonix-Gateway (
- For example, Whonix users residing in China.
- This is useful when testing later Whonix releases to stymie deanonymization attempts by advanced adversaries, or when creating an identical backup that does not share any other persistent data, except for Tor state and custom torrc options.
- Notifications are made in real time for any potentially suspicious activity.
- Unauthorized modifications to BIOS or the boot partition will be notified.
- This is safe in the stable Qubes R4 release, but privacy issues were unresolved in Qubes R3.2 (now unsupported).
- Users can configure
sys-usbas static Disposables. This option has been available from Qubes R4 onward.
- Reminder: The Subject: line and other header fields are not encrypted in the current configuration.
- Attackers use these methods to redirect local network traffic and execute Man-in-the-middle Attacks.
- Administrators are advised of any changes via email, such as new station/activity, flip-flops and re-used/changed old addresses.
- The reason is adversaries observing traffic will need to perform classification of both traffic generated by the Tor relay or bridge and your personal client traffic.
- This provides an additional fail-safe to protect from accidental clearnet leaks that might arise from hypothetical Whonix bugs, but does not address potential Qubes ProxyVM leaks.
- This reduces the attack surface by disabling SUID-enabled binaries and improves Strong Linux User Account Isolation. Some SUID binaries have a history of privilege escalation security vulnerabilities. This feature is part of security-misc.
- Although Libreboot is a free, opensource BIOS or UEFI replacement that initializes the hardware and starts the bootloader for the OS, the absence of proprietary firmware means important microcode security updates are unavailable. Also, even experts risk bricking their hardware during the process and it is incompatible with newer architectures, making it impractical for the majority of the Whonix population.
- Using two different computers and virtualization is one of the most secure configurations available, but may be less secure than Qubes' approach (software compartmentalization).