Operational Security Guide
An operational security guide distils the principles used by security professionals, journalists, and researchers to protect sensitive activities from adversarial observation. The term originates in military doctrine — where it referred to protecting mission-critical information from intelligence collection — and has since been adopted across digital privacy, activism, and investigative journalism contexts. This guide synthesises publicly documented OPSEC principles from academic research, security journalism, and open-source intelligence resources.
The core principle of operational security is simple: identify what you need to protect, identify who might want to obtain it, assess the likelihood and impact of each threat, and apply countermeasures proportionate to the assessed risk. This threat-modelling framework is described in detail by the Electronic Frontier Foundation's Surveillance Self-Defense project (ssd.eff.org) and serves as the foundation for all specific technical guidance below.
Tor Browser: Core Tool for Staying Anonymous Online
Tor Browser (torproject.org/download) is the primary tool for anonymising web traffic. It routes all connections through three Tor relay nodes, each knowing only the previous and next hop in the chain. No single relay can observe both the source and destination of a connection. The Tor Project publishes detailed security documentation and a list of known limitations at tb-manual.torproject.org.
Critical Tor usage rules documented by the Tor Project and security researchers: do not resize the browser window (breaks the uniform fingerprint); do not install additional extensions (each extension potentially uniquifies the fingerprint); do not log in to identity-linked accounts; do not enable JavaScript on sites where it is not required; and do not open downloaded files (PDFs, DOCXs) while connected to Tor, as these can make external network connections that bypass the Tor circuit. Tails OS (tails.boum.org) routes all system traffic through Tor by design, providing a stronger separation between Tor and non-Tor activity than running Tor Browser on a standard operating system.
PGP Encryption: Protecting Communication on Privacy in Internet
Pretty Good Privacy (PGP) provides end-to-end encryption for text messages and file attachments. Gpg4win (gpg4win.org) for Windows and GnuPG (gnupg.org) for Linux and macOS implement the OpenPGP standard. Key management — understanding what a fingerprint is, how to verify a key through independent channels, and how to sign keys to build a web of trust — is documented in the GnuPG User Guide at gnupg.org/documentation/guides.
When communicating with darknet platform support, vendor contacts, or other parties whose identity you cannot verify in person, never send plaintext messages containing sensitive operational details. Always encrypt to the recipient's verified public key and sign with your own private key to prevent message injection. The key to "verified" is: independently cross-check the key fingerprint through at least two separate channels (for example, the platform's onion-site key-display page and an archived copy from a trusted forum post).
Common PGP mistakes documented in security research: using a key generated with insufficient entropy; not setting a strong passphrase on the private key; sharing the private key file in an unencrypted backup; using an email address in the key that links to a real identity; and failing to check the expiry date of a recipient's key before encrypting. Key best practice: generate keys on an air-gapped machine or within Tails OS, and store the private key only on encrypted storage.
Common OPSEC Mistakes Documented in Research
Security research and court documents have documented recurring OPSEC failures that have led to real-world identification of individuals who believed they were operating anonymously. The most common documented failure mode is identity bleed: using the same username, writing style, avatar, or other identifiable characteristic across both anonymous and identified contexts. Researchers at Draper Laboratory published a stylometric analysis demonstrating that writing style alone can identify anonymous authors with high accuracy from relatively short text samples.
A second major documented failure is operational pattern consistency: accessing anonymous platforms from the same location (home network, workplace), at the same times of day, on the same device. Network timing correlation studies have demonstrated that consistent access patterns can enable partial de-anonymisation even when Tor is used correctly. Best practice: use a dedicated device for all anonymous activity, accessed from diverse network locations, with varied timing.
Third documented failure: inadequate compartmentalisation. Using an anonymous cryptocurrency wallet for both privacy-sensitive purposes and mundane purchases — particularly purchases that can be mapped to a physical delivery address — creates a transaction-graph link between the anonymous and identified contexts. Strict wallet compartmentalisation, using separate wallets for each distinct operational context, is documented as the most effective mitigation.
The EFF's Surveillance Self-Defense (ssd.eff.org/module/your-security-plan) threat-modelling guide provides a structured framework for identifying and prioritising the specific risks relevant to a given use case. The Privacy Guides project (privacyguides.org) maintains an up-to-date list of recommended privacy tools across all major operating systems. For cryptocurrency-specific privacy practices, see the anonymous payment guide.
Device and Network Security for an Opsec Guide
Device security begins with software hygiene: all operating system and application updates applied promptly, full-disk encryption enabled (BitLocker on Windows, FileVault on macOS, LUKS on Linux), and a strong login passphrase. Hardware considerations for high-security use include disabling or physically removing the microphone and camera, using a Faraday bag when not in active use, and avoiding devices with closed-source firmware in the baseband processor.
Network-level security for anonymous operations: use Tor Browser or Tails for all sensitive activity; avoid Wi-Fi networks associated with your legal identity; consider using a mobile hotspot with a no-registration SIM for high-risk sessions; and never access both your identified accounts and anonymous platforms in the same browser session or on the same device. The combination of device discipline and network discipline is documented in security research as the most robust available defence against correlation attacks.