Operational Security Protocols

CRITICAL ADVISORY

Perfect anonymity does not exist. Even the most robust security practices can be compromised by human error, advanced surveillance capabilities, or zero-day exploits. Adjust your operational security measures according to your specific threat model—the higher the stakes, the more disciplined your approach must be.

Threat Modeling
System Security
Network Security
Identity Protection
Crypto Security
Physical Security
Advanced Techniques

Understanding Your Threat Model

Before implementing any security measures, you must assess who might target you, what they want, their capabilities, and what you're trying to protect. This framework will determine which countermeasures are appropriate for your situation.

Threat Actor Analysis

Different adversaries possess different capabilities and motivations:

  • Casual Observers: Individuals with basic technical skills seeking information through publicly available tools.
  • Commercial Entities: Companies tracking your data for advertising, analytics, or commercial intelligence.
  • Sophisticated Criminals: Malicious actors with advanced technical capabilities seeking financial gain.
  • Nation-State Actors: Government agencies with nearly unlimited resources, legal authority, and advanced capabilities.

Determine which category of adversary you need to protect against. The measures required to defend against casual observers differ significantly from those needed against state-level actors.

Risk Assessment Matrix

Evaluate your specific risks using this matrix:

1. What information or assets are you protecting? - Personal identity - Communications content - Browsing history - Physical location - Financial information - Social connections 2. What are the consequences of compromise? - Embarrassment - Financial loss - Legal repercussions - Physical harm - Damage to others 3. How likely is a targeted attack? - Low: General surveillance only - Medium: Commercial targeting - High: Specific adversaries interested in you

Map your answers to determine which security measures are most important for your situation. Focus resources on protecting your most valuable assets against your most likely threats.

Security Tiers

Based on your threat model, select one of these security postures:

Tier 1

Tier 1: Basic Privacy — Protection from casual observation, tracking, and data collection. Suitable for routine browsing and low-stakes activities.

  • Use Tor Browser with default settings
  • Enable HTTPS everywhere
  • Use basic password management
  • Avoid personally identifying information
Tier 2

Tier 2: Enhanced Anonymity — Protection from targeted commercial tracking and baseline security against determined adversaries.

  • Use Tor with security slider set to Safer
  • Implement compartmentalization
  • Use encrypted messaging
  • Disable JavaScript when possible
  • Use secure OS settings
Tier 3

Tier 3: Advanced Operational Security — Protection from sophisticated adversaries with significant resources.

  • Use Tails OS or Whonix
  • Maintain strict network isolation
  • Implement air-gapped computing
  • Use multiple layers of encryption
  • Follow strict operational discipline
Tier 4

Tier 4: Counter-Intelligence Grade — Protection against state-level adversaries. Extremely demanding and potentially impractical for most users.

  • Air-gapped Qubes OS with security-focused configuration
  • Multiple nested routing layers
  • Physical isolation and countersurveillance
  • One-time communication channels
  • Advanced metadata protection techniques

Securing Your Operating System

Your operating system is the foundation of your security posture. An insecure OS undermines all other security measures.

Operating System Selection

Choose your OS based on your threat model:

Tails OS

Amnesic live system that leaves no digital footprint. All Internet traffic routed through Tor. Memory wiped on shutdown.

http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
amnesic portable

Whonix

Dedicated OS designed for advanced anonymity. Uses multiple VM isolation for strong security guarantees. Requires more setup than Tails.

http://dds6qkxpwdeubwucdiaord2xgbbeyds25rbsgr73tbfpqpt4a6vjwsyd.onion
vm-isolation stream-isolation

Qubes OS

Security-focused desktop OS using compartmentalization. Based on Xen hypervisor with multiple security domains.

http://qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion
compartmentalized advanced

OS SECURITY NOTICE

No special-purpose security OS can protect you if your hardware is already compromised. Consider using verified clean hardware when possible, especially for high-security operations.

System Hardening

Regardless of your chosen OS, implement these hardening measures:

  • Encrypt your entire drive using strong encryption (LUKS, VeraCrypt, or built-in OS encryption)
  • Disable unnecessary services, especially remote access services
  • Keep all software updated with security patches
  • Remove unnecessary applications to reduce attack surface
  • Configure automatic updates for security patches
  • Use non-admin accounts for daily operations
  • Enable a firewall and configure strict outbound rules

Secure Boot Configuration

Your system's boot process requires special attention to prevent threats like evil maid attacks or boot-level malware.

# Recommended GRUB secure boot settings GRUB_CMDLINE_LINUX="slab_nomerge slub_debug=FZP page_poison=1 pti=on" # Enable kernel module signing sudo mokutil --enable-validation sudo update-secureboot-policy --new-key # Verify boot integrity sha256sum /boot/vmlinuz-$(uname -r) # Set encrypted GRUB password grub-mkpasswd-pbkdf2 sudo nano /etc/grub.d/40_custom set superusers="admin" password_pbkdf2 admin [hash] sudo update-grub

DO

  • Use UEFI Secure Boot when possible
  • Set firmware/BIOS passwords
  • Enable full disk encryption with pre-boot authentication
  • Use Trusted Platform Module (TPM) if available
  • Keep boot partitions on removable media for high-security setups

DON'T

  • Leave unencrypted boot partitions exposed
  • Enable boot from external media in public locations
  • Store sensitive data on systems with questionable boot security
  • Trust hardware that has been out of your physical control
  • Ignore physical security warnings from secure boot

Securing Network Connections

Your network traffic contains valuable metadata that can compromise your identity even when the content is encrypted.

The Tor Network

Tor remains the foundation of anonymous browsing, but must be used correctly:

# Check Tor connectivity curl --socks5 127.0.0.1:9050 --socks5-hostname 127.0.0.1:9050 -s https://check.torproject.org/ | cat | grep -m 1 Congratulations | xargs # Test for DNS leaks (should return Tor exit node IP, not your real IP) torsocks dig +short myip.opendns.com @resolver1.opendns.com # Enable stream isolation in torrc SocksPort 9050 SocksPort 9051 IsolateDestAddr SocksPort 9052 IsolateDestPort SocksPort 9053 IsolateDestAddr,IsolateDestPort

TOR USAGE WARNING

The Tor Browser Bundle is carefully configured to prevent identity leaks. Modifying settings or using Tor without the official browser can compromise your anonymity. Never use Tor Browser for both anonymous and non-anonymous activities.

Tor Browser Security Settings

Standard

Default security level. Most sites work normally. JavaScript enabled.

Safer

Disables some features. JavaScript disabled on non-HTTPS sites. Recommended for general use.

Safest

Maximum security. JavaScript disabled everywhere. Many sites will not function correctly.

Advanced Network Protection

For enhanced security, consider these additional network protection techniques:

VPN + Tor Configurations

# Configuration options: 1. VPN → Tor Protects from malicious Tor entry nodes Hides Tor usage from ISP Drawback: VPN provider knows you use Tor 2. Tor → VPN Hides from malicious exit nodes Bypasses Tor exit node blocks Drawback: No .onion access, single point of failure 3. VPN → Tor → VPN Maximum protection but increased latency Drawback: Complex to configure correctly

DNS Leak Protection

DNS requests can reveal your browsing activity even when using Tor:

  • Use DNS over HTTPS or DNS over Tor
  • Check for DNS leaks at regular intervals
  • Consider a local DNS resolver with encryption
  • Verify DNS settings after system updates

Traffic Correlation Countermeasures

To defend against traffic analysis and correlation attacks:

  • Use multiple entry nodes or bridges
  • Implement scheduled connectivity rather than continuous
  • Avoid consistent usage patterns
  • Consider high-latency anonymous networks for non-time-sensitive communications

Multi-layered Network Security Architecture

For maximum security, implement a defense-in-depth network strategy:

Layer Technology Purpose Implementation
Physical Layer Hardware firewalls, air gaps Physical network isolation Dedicated hardware, physical network separation
Link Layer MAC address randomization Prevent device fingerprinting macchanger, NetworkManager settings
Network Layer IP obfuscation, VPNs Hide source IP address VPN chains, Tor bridges
Transport Layer TLS, SOCKS proxies Encrypt traffic, bypass censorship Stream isolation, TLS verification
Application Layer Tor, I2P, Freenet Anonymous routing Tor Browser Bundle, specialized clients
Content Layer End-to-end encryption Message privacy PGP, OTR, Signal Protocol

Compartmentalization & Identity Management

The foundation of effective OPSEC is strict separation between different identities and activities.

Identity Compartmentalization

Create separate, isolated personas for different activities:

# Identity Separation Framework Identity Tree Structure: - Root identity (your real identity) ├── Public pseudonym (linked to real name) │ └── Sub-pseudonyms for specific public activities ├── Protected pseudonym (not linked to real name) │ └── Sub-pseudonyms for sensitive but legal activities └── Anonymous identities (completely isolated) └── Single-use or purpose-specific identities Identity Boundaries: - Never cross streams between identities - Use separate devices when possible - Use separate network paths - Never reference one identity from another - Maintain distinct behavioral patterns for each identity

IDENTITY HYGIENE WARNING

A single mistake in identity compartmentalization can permanently link your separate identities. Assume that advanced adversaries can connect personas that share any common elements. Mistakes cannot be undone.

Pseudonym Creation & Maintenance

Follow these guidelines when establishing online identities:

  • Generate random usernames without personal significance using tools like pwgen -s 12
  • Create backstories that are generic enough to be unmemorable but specific enough to be consistent
  • Use different writing styles, vocabulary, and syntax patterns for different identities
  • Maintain separate email addresses, cryptocurrency wallets, and accounts for each identity
  • Document your pseudonym details in encrypted storage accessible only by you
  • Establish access schedules and never deviate (e.g., never access identity A and B on the same day)

Stylometry Countermeasures

Advanced adversaries can identify you through writing style analysis:

  • Use different vocabulary, sentence structures, and idioms for each identity
  • Consider using machine translation to alter writing style (e.g., translate to another language and back)
  • Avoid distinctive phrases, punctuation patterns, or word choices
  • For high-security needs, use collaborative writing or text generation tools

Browser Fingerprinting Defenses

Modern browsers leak identifying information through numerous channels:

Fingerprinting Vector Information Leaked Countermeasure
User Agent Browser, OS, version Use Tor Browser with default settings
Canvas/WebGL Hardware rendering differences Use canvas blocker or disable JavaScript
Fonts & Plugin Data Installed system fonts Use only standard font set, block font enumeration
Screen Resolution Display specifications Use common resolution or resize window
Timezone/Locale Geographic location Set to UTC or common timezone
WebRTC Internal IP addresses Disable WebRTC or use WebRTC blocker
Browser Storage Previous visits, behavior Clear storage between sessions, use private browsing
Hardware Sensors Device orientation, battery Disable sensor APIs

FINGERPRINTING WARNING

Attempting to make your browser unique by installing many privacy extensions can backfire, making you more identifiable. The Tor Browser is specifically designed to make all users look identical. Avoid customizing it unless you fully understand the implications.

Cryptographic Tools & Practices

Strong encryption is essential for securing communications and data, but must be implemented correctly.

PGP: Email & Data Encryption

OpenPGP remains the standard for secure communications:

# Generate a new PGP key pair (4096-bit RSA, 2 year expiry) gpg --full-generate-key # Create a revocation certificate immediately gpg --output revocation-certificate.asc --gen-revoke your_email@domain.com # Export your public key to share gpg --armor --export your_email@domain.com > public-key.asc # Encrypt a file for a recipient gpg --encrypt --recipient recipient@example.com document.txt # Sign and encrypt a message gpg --sign --encrypt --recipient recipient@example.com document.txt # Decrypt a message gpg --decrypt encrypted-document.txt.gpg > decrypted-document.txt # Verify a signature gpg --verify signed-document.txt.asc

PGP SECURITY NOTES

Remember that PGP does not hide metadata (who is communicating with whom). Subject lines are not encrypted. Use anonymous communication channels in conjunction with PGP for full protection.

Key Management Best Practices

  • Generate keys on an air-gapped computer
  • Store master private keys offline
  • Use subkeys for daily operations
  • Back up private keys securely, preferably on encrypted media
  • Verify signatures on public keys before trusting them
  • Have a revocation plan ready before you need it

Secure Messaging Protocols

For real-time communications, consider these encrypted messaging options:

Signal

End-to-end encrypted messaging with perfect forward secrecy. Requires phone number, so use with caution for anonymous communications.

e2ee forward-secrecy

Session

Decentralized messenger built on Lokinet. No phone number required, uses public keys as identifiers.

https://getsession.org/
decentralized no-metadata

XMPP with OMEMO

Federated messaging protocol with modern encryption. Multiple server options, including self-hosting.

http://lxjacvxrozjlxd7pqced7dyefnbityrwqjosuuaqponlg3v7esifrzad.onion/en/
federated customizable

Evaluating Cryptographic Claims

When selecting security tools, beware of misleading claims:

  • Prefer open-source solutions with independent security audits
  • Look for established cryptographic algorithms (e.g., AES, RSA, Curve25519)
  • Verify that the implementation has been professionally audited
  • Be skeptical of "military-grade encryption" or similar marketing terms
  • Check if the protocol provides forward secrecy and deniability

Cryptocurrency Privacy Practices

Using cryptocurrency securely requires special attention to privacy:

DO

  • Use privacy-focused cryptocurrencies like Monero for sensitive transactions
  • Generate new addresses for each transaction
  • Use coin mixing/tumbling services cautiously and with research
  • Allow sufficient confirmation blocks before considering transactions final
  • Use hardware wallets for significant holdings
  • Verify recipient addresses through multiple channels

DON'T

  • Assume Bitcoin or other public ledger cryptocurrencies are anonymous
  • Reuse wallet addresses for multiple transactions
  • Connect wallets to your real identity
  • Use exchange wallets for anonymous transactions
  • Discuss your holdings or transactions publicly
  • Rely on a single mixing service

Monero Security Configuration

# Recommended Monero client settings for maximum privacy # Run your own node when possible --p2p-bind-ip=127.0.0.1 --no-igd --hide-my-port # Connect through Tor --proxy=127.0.0.1:9050 --tx-proxy=127.0.0.1:9050 # Increase ring signature size (default is 11) --ring-size=16 # Disable DNS queries --no-dns --offline # Advanced: Connect only to Tor nodes --add-exclusive-node=monerot7qdtcpkyj.onion:18081 --add-exclusive-node=moneroxzyec6gg4j.onion:18081

Protecting Your Physical Environment

Digital security is meaningless if your physical environment is compromised. Physical security is often the most overlooked aspect of OPSEC.

Hardware Security

Your devices are vulnerable to physical tampering:

  • Maintain physical control of hardware at all times
  • Use tamper-evident seals on device seams
  • Disable AutoRun/AutoMount features
  • Lock BIOS with a strong password
  • Consider using USB data blockers for charging in public
  • Disable all unnecessary hardware ports
  • Physically disable webcams and microphones when not in use

EVIL MAID ATTACK WARNING

If an adversary gains physical access to your device, even temporarily, it should be considered potentially compromised. Hotels, border crossings, and repair shops present high-risk scenarios.

Environmental Security

Your surroundings can betray your activities:

Visual Privacy

  • Use privacy screens to prevent shoulder surfing
  • Position screens away from windows and doorways
  • Be aware of security cameras in public spaces
  • Check for reflective surfaces that might expose screen contents

Audio Privacy

  • Be mindful of ambient noise levels when discussing sensitive information
  • Use white noise generators or music to mask conversations
  • Remove smart speakers and IoT devices from sensitive areas
  • Consider acoustic isolation for highly sensitive discussions

RF/EM Emissions

  • Use Faraday bags for devices when not in use
  • Remove batteries when possible for long-term storage
  • Be aware that air-gapped computers can leak data via EM emissions
  • Consider TEMPEST shielding for extremely sensitive operations

Secure Destruction Protocols

Properly destroying sensitive data and hardware is critical:

Media Type Secure Destruction Method Verification
HDDs Multiple-pass secure wiping followed by physical destruction Use dd if=/dev/urandom of=/dev/sdX multiple times, then disassemble and destroy platters
SSDs ATA Secure Erase, then physical destruction Use manufacturer utilities for secure erase, then physically destroy NAND chips
USB Drives Secure wiping followed by physical destruction Multiple passes with shred -vfz -n 10, then physically destroy
SD Cards Secure wiping followed by incineration Multiple passes with secure erase utilities, then burn
Paper Documents Cross-cut shredding and/or incineration Mix shredded material before disposal or burn completely to ash
Mobile Devices Factory reset, then physical destruction Multiple factory resets, then destroy storage components

DATA RECOVERY WARNING

Advanced forensic techniques can recover data from media that appears erased. When in doubt, physical destruction is the only guaranteed method. For high-security needs, combine multiple destruction methods.

Advanced OPSEC Techniques

These advanced methodologies are for users with sophisticated threat models and technical expertise.

ADVANCED EXPERTISE REQUIRED

The techniques in this section require significant technical knowledge and careful implementation. Misconfiguration can create a false sense of security while actually increasing vulnerability. Proceed with caution.

Air-Gapped Computing

Physically isolating computers from networks provides maximum security:

# Air-Gap Implementation Checklist 1. Hardware Preparation: - Computer with no wireless capabilities (remove Wi-Fi/Bluetooth) - Physically disable or remove all network interfaces - Disable all unnecessary I/O ports - Consider removing speakers and microphones 2. Software Configuration: - Install minimal OS from verified media - Remove all unnecessary software and drivers - Disable all auto-update mechanisms - Configure strict USB device policies 3. Data Transfer Protocols: - Use one-way data diodes when possible - For USB transfers, use dedicated transfer devices - Scan all incoming files in quarantine environment - Use optical media for one-time transfers 4. Physical Security: - Store air-gapped systems in secure, monitored locations - Implement surveillance countermeasures - Control physical access with multiple factors - Consider faraday cage for sensitive operations

Air-Gap Jumping Countermeasures

Advanced attackers use several techniques to breach air gaps:

  • Acoustic isolation to prevent sonic covert channels
  • Faraday shielding to block electromagnetic emissions
  • Control all removable media with strict protocols
  • Disable or physically remove unnecessary hardware components
  • Consider optical isolation for necessary data transfers
  • Implement strict physical access controls

Deniable Encryption

Create plausibly deniable hidden volumes:

# VeraCrypt Hidden Volume Configuration 1. Create outer volume with decoy data: veracrypt --create /dev/sdX1 --encryption AES --hash sha512 --filesystem FAT # Mount and fill with plausible decoy files 2. Create hidden volume within outer volume: # Mount outer volume veracrypt --mount /dev/sdX1 /mnt/outer # Create hidden volume veracrypt --create --hidden /mnt/outer/hidden.vc --encryption AES-Twofish-Serpent --hash sha512 --filesystem ext4 3. Accessing hidden volume: # Use different password than outer volume veracrypt --mount /dev/sdX1 /mnt/hidden --hidden 4. Security considerations: # Never write to outer volume after creating hidden volume # Use separate passwords for each volume # Consider using keyfiles in addition to passwords

Advanced Authentication Methods

Multi-factor authentication options for high-security systems:

  • Hardware security keys (YubiKey, Nitrokey)
  • Smart cards with PKI infrastructure
  • One-time pad authentication systems
  • Challenge-response protocols with offline verification
  • Biometric authentication with liveness detection (only on air-gapped systems)

Counter-Surveillance Techniques

Methods to detect and counter surveillance:

Digital Counter-Surveillance

  • Regularly audit network connections and processes
  • Monitor system resource usage for anomalies
  • Use intrusion detection systems on sensitive networks
  • Set up canary tokens to detect compromise
  • Analyze outbound traffic patterns for unexpected communications
  • Routinely scan for unknown wireless networks and devices

Physical Counter-Surveillance

  • Implement irregular movement patterns and timings
  • Use cover for action and cover for status techniques
  • Practice SDR (surveillance detection routes)
  • Verify meeting locations before sensitive discussions
  • Be aware of choke points and surveillance cameras
  • Conduct regular sweeps for physical tracking devices

Secure Communication Dead Drops

For the highest security communications:

# Digital Dead Drop Implementation 1. Dead Drop Site Selection: - Use decentralized storage platforms - Select obscure public repositories or pastebins - Use steganography in public media platforms - Consider blockchain-based storage for immutability 2. Access Protocol: - Use throwaway access credentials - Access only through anonymity networks - Implement time-based access windows - Use agreed-upon timing algorithms 3. Message Security: - Encrypt all messages with recipient's public key - Use steganography to hide message existence - Include cryptographic timestamps to prevent replay - Implement secure deletion after confirmed retrieval 4. Signaling Mechanism: - Use separate covert channels for notifications - Implement innocuous-looking canary messages - Consider broadcast mechanisms without direct contact - Use timing-based signals that appear as normal activity

Emergency Response Procedures

Prepare for security incidents before they occur. Having established procedures can mean the difference between minor compromise and catastrophic failure.

Compromise Response Checklist

  1. Disconnect affected systems from all networks immediately
  2. Document all observations and indicators of compromise
  3. Activate alternate communication channels based on compromise severity
  4. Implement identity migration if pseudonyms are compromised
  5. Revoke and replace cryptographic keys through secure channels
  6. Execute secure data destruction protocols for compromised information
  7. Analyze the breach to improve future security measures

Duress Protocols

Prepare for scenarios involving coercion or forced access:

  • Establish duress signals or codes for trusted contacts
  • Configure duress passwords that disclose limited information
  • Consider systems with automatic secure wiping after specific triggers
  • Have legally compliant responses prepared for common scenarios
  • Create geographical "canary zones" that trigger security protocols if entered
↑