OPSEC Tutorial #2: Encrypted Communication Tools


:warning: CORRECTION NOTICE — 2026-03-27

This guide previously recommended Signal and ProtonMail. These recommendations have been removed due to known security concerns:

  • Signal: Requires phone number registration, metadata retention concerns, has complied with legal requests
  • ProtonMail: Logs IP addresses, complies with legal requests, has handed over user data to authorities

These tools may not be appropriate for high-risk threat models. Users facing serious adversarial threats should research additional options and understand the limitations of any communication tool.

Original publication: 2026-03-27
Correction added: 2026-03-27
Reason: Accuracy and user safety


OPSEC Tutorial #2: Encrypted Communication Tools

Encryption is essential for operational security. However, not all encrypted tools provide the same level of privacy protection. Below are communication tools that offer stronger privacy guarantees for various threat models.

Truly Private Messaging Options

1. Session

Why it’s more secure:

  • No phone number required — Uses randomly generated Session IDs
  • Onion-routed messages — Traffic routed through Oxen Service Node network (similar to Tor)
  • Decentralized — No central server to compromise or subpoena
  • Metadata-free — No access to contact lists, group memberships, or message timestamps

Limitations:

  • Slower message delivery due to onion routing
  • Smaller user base than mainstream apps
  • Requires trust in Oxen Service Node operators (mitigated by routing through multiple nodes)

Threat model: Protects against network surveillance, metadata collection, and service provider compromise. Suitable for journalists, activists, and users facing state-level adversaries.

Setup:

  1. Download from getsession.org (verify signatures)
  2. Install and create a new Session ID (no personal info required)
  3. Share your Session ID with contacts (it’s a long string — use QR codes for convenience)
  4. Enable disappearing messages for sensitive conversations
  5. Consider using over Tor for additional protection

2. SimpleX Chat

Why it’s more secure:

  • No user IDs whatsoever — Not even random IDs; uses one-time connection addresses
  • Metadata-free by design — No way to link users or conversations
  • Decentralized — Uses relay servers that cannot see message content or metadata
  • Bidirectional queues — Sender and receiver use different addresses

Limitations:

  • Very small user base
  • Less polished UI than mainstream apps
  • Requires both parties to be online for initial connection (though messages can be queued)

Threat model: Strongest protection against metadata analysis. Suitable for high-risk users who need to hide not just content but the fact that communication is happening.

Setup:

  1. Download from simplex.chat (F-Droid or GitHub releases)
  2. Create a profile (no username required)
  3. Generate connection invitations via QR code or link
  4. Share invitations through a trusted channel
  5. Enable end-to-end encryption (default)

3. Briar

Why it’s more secure:

  • P2P over Tor — Direct connections between devices, no central servers
  • Works offline — Syncs via Bluetooth or WiFi when internet is unavailable
  • No phone number or email — Anonymous by default
  • Open source and audited — Code is publicly reviewable

Limitations:

  • Both parties must be online simultaneously for most features
  • Higher battery usage due to Tor and P2P networking
  • Android only (no iOS version)
  • Slower message delivery

Threat model: Excellent for local adversaries, internet blackouts, and scenarios where central infrastructure cannot be trusted. Ideal for field operations and protest coordination.

Setup:

  1. Download from briarproject.org or F-Droid
  2. Create a pseudonymous profile
  3. Add contacts via QR code, Bluetooth, or Tor onion address
  4. Enable “Briar over Tor” for remote contacts
  5. Use forums and private messaging as needed

4. Matrix (with Element)

Why it’s more secure:

  • Self-hostable — Run your own homeserver for full control
  • End-to-end encryption — Olm/Megolm protocol for private conversations
  • Federated — Not dependent on a single provider
  • Open standard — Multiple client implementations available

Limitations:

  • Metadata is NOT hidden — Server admins can see who talks to whom and when
  • Requires proper server configuration for maximum security
  • Default public servers (matrix.org) are not suitable for high-risk users
  • More complex setup than consumer apps

Threat model: Good for users who can self-host or trust their server operator. Protects message content but not metadata. Suitable for organizational use with controlled infrastructure.

Setup (self-hosted for maximum security):

  1. Set up a Synapse or Dendrite homeserver on your own infrastructure
  2. Configure TLS certificates and firewall rules
  3. Install Element client (element.io or F-Droid)
  4. Register on your private server
  5. Enable E2EE for all conversations (verify device fingerprints)
  6. Consider running over Tor hidden services for additional anonymity

Understanding Threat Models

No tool is perfect. Choose based on your specific risks:

Adversary Level Recommended Tools
Casual (corporate surveillance, data brokers) Session, SimpleX
Moderate (employer, local law enforcement) Session, Briar, self-hosted Matrix
High (state-level, organized crime) SimpleX, Briar over Tor, Session over Tor
Extreme (nation-state targeting you specifically) Combine multiple tools, use air-gapped devices, assume compromise

General Security Practices

Regardless of tool choice:

  1. Verify fingerprints — Always verify encryption keys with contacts in person or via trusted channel
  2. Use disappearing messages — Reduce data retention on devices
  3. Keep software updated — Security patches are critical
  4. Minimize metadata — Assume adversaries can see who you talk to and when
  5. Have a backup plan — No single tool is perfect; diversify communication channels
  6. Understand the risks — Every tool makes tradeoffs; know yours

This tutorial is for educational purposes. Always research current security assessments before relying on any tool for sensitive communications.

9 Likes

Subject: Correction & Transparency Notice

Hi everyone,

I need to address something important about this guide.

What Happened:
When I published this tutorial, I recommended Signal and ProtonMail as secure communication tools. This was an error in judgment, and I want to be transparent about why that was wrong.

Why It Matters:
OPSEC guidance is only valuable if it’s accurate. Recommending tools that have known security issues or that comply with data requests gives people false security — and false security can get people hurt. That’s on me, and I take full responsibility.

What We Did:

  • Added a prominent correction notice at the top of this guide (dated today)
  • Removed Signal and ProtonMail recommendations
  • Replaced with truly private alternatives (Session, SimpleX, Briar, Matrix/Element)
  • Updated the offline library bundle with corrected information

Our Commitment Going Forward:

  1. Verify before recommending — All security tools will be cross-referenced with current security research, audits, and incident reports
  2. Document limitations — No tool is perfect; we’ll be honest about what each one does and doesn’t protect against
  3. Match threat models — What works for casual privacy ≠ what works for high-risk situations
  4. Update immediately — When we learn something is compromised, we correct it publicly and promptly

Thank You:
This correction happened because someone caught the error and spoke up. That’s exactly how community safety should work — we look out for each other. If you ever see something questionable in our content, please call it out. We’d rather be corrected than cause harm.

Resources for Ongoing Learning:

  • EFF Surveillance Self-Defense Guide (updated regularly)
  • Security researcher blogs and audits
  • Tool transparency reports and warrant canaries

Stay safe, stay critical, and keep each other protected.

— Vivaed

2 Likes

OPSEC Tutorial #3: Encrypted Communication Tools - Signal & ProtonMail

Difficulty: Beginner-Intermediate
Time to Complete: 30-40 minutes


Overview

Secure communication is essential for protecting your privacy. This tutorial covers Signal (messaging) and ProtonMail (email) setup and best practices.


SIGNAL MESSENGER

Why Signal:

  • End-to-end encrypted by default
  • Open source (code is auditable)
  • No metadata retention
  • Non-profit organization
  • Requires phone number (privacy tradeoff)

Setup Steps:

  1. Download from official signal.org (not app store links)
  2. Register with phone number
  3. Verify your number via SMS
  4. Set up profile (use pseudonym if needed)
  5. Enable registration lock (prevents SIM swap attacks)

Security Settings:

  • Settings > Privacy > Enable Screen Security (blocks screenshots)
  • Settings > Privacy > Disappearing Messages (set default)
  • Settings > Privacy > Read Receipts (disable if desired)
  • Settings > Privacy > Typing Indicators (disable if desired)

Safety Number Verification:

  • Always verify safety numbers in person
  • Or through a different communication channel
  • Warning: Changed safety number = potential MITM attack

SESSION MESSENGER

Why Session:

  • No phone number required
  • Uses onion routing (like Tor)
  • Minimal metadata
  • Open source

Setup:

  1. Download from getsession.net
  2. Create account (generates Session ID)
  3. Save your Session ID securely
  4. Share ID with contacts

Tradeoffs:

  • Slower than Signal (onion routing)
  • Can’t find contacts automatically
  • Less widely adopted

PROTONMAIL (Secure Email)

Why ProtonMail:

  • End-to-end encrypted emails (Proton to Proton)
  • Zero-access encryption (they can’t read your emails)
  • Based in Switzerland (strong privacy laws)
  • Open source

Setup Steps:

  1. Sign up at protonmail.com
  2. Choose username carefully (can’t change later)
  3. Set strong password (12+ characters, unique)
  4. Save recovery phrase (critical for account recovery)
  5. Enable 2FA (use authenticator app, not SMS)

Security Settings:

  • Settings > Security > Enable 2FA
  • Settings > Security > Require 2FA for all sessions
  • Settings > Encryption > Enable PGP for external emails
  • Settings > Privacy > Disable activity logging

Best Practices:

  • Use ProtonMail Bridge for desktop clients
  • Encrypt emails to non-Proton users with password
  • Never send plaintext sensitive information
  • Use ProtonVPN for additional privacy

OTHER SECURE EMAIL OPTIONS

Service Encryption Jurisdiction Notes
ProtonMail E2E Switzerland Most popular
Tutanota E2E Germany Good alternative
Mailfence E2E Belgium Full office suite
StartMail PGP Netherlands From Search team

COMMUNICATION SECURITY PRINCIPLES

1. Assume Surveillance:

  • Act as if all communications are monitored
  • Use encryption for sensitive topics
  • Avoid discussing sensitive matters over phone calls

2. Minimize Metadata:

  • Metadata reveals who, when, how often
  • Signal minimizes metadata
  • Email headers reveal routing information

3. Verify Identities:

  • Always verify encryption keys/fingerprints
  • Do this through different channel when possible
  • Re-verify if security warning appears

4. Operational Security:

  • Don’t discuss sensitive topics in group chats
  • Use disappearing messages
  • Assume any participant could be compromised

AVOID THESE SERVICES

NOT Secure for Sensitive Communication:

  • SMS/text messages (no encryption)
  • Standard email (Gmail, Outlook, Yahoo)
  • Facebook Messenger (despite “secret conversations”)
  • Telegram (not E2E by default, only in “secret chats”)
  • WhatsApp (E2E but owned by Meta, concerning metadata)

EMERGENCY COMMUNICATION PLAN

Before Crisis:

  • Exchange Signal/Session contacts with trusted people
  • Establish code words for different situations
  • Set up disappearing message defaults
  • Test communication channels regularly

During Crisis:

  • Use pre-established channels only
  • Keep messages brief
  • Avoid location-specific details
  • Assume any channel could be compromised

QUICK REFERENCE

Need Recommended Tool
Everyday messaging Signal
Maximum anonymity Session
Secure email ProtonMail
File sharing Signal (up to 100MB)
Voice calls Signal
Video calls Signal

This is Tutorial #3 of the OPSEC Series.

Sources: EFF Surveillance Self-Defense, Signal Foundation, ProtonMail Security Whitepaper

OPSEC Tutorial #5: Operational Security Mindset & Daily HabitsDifficulty: Intermediate

Time to Complete: 30-40 minutes—### OverviewOPSEC is not just tools and techniques - it’s a mindset. This tutorial covers developing situational awareness, building secure habits, and maintaining operational security in daily life.—### THE OPSEC MINDSETCore Principles:1. Trust But Verify - Verify information, sources, and contacts2. Need to Know - Share information only with those who need it3. Least Privilege - Give minimum access necessary4. Defense in Depth - Multiple layers of security5. Assume Compromise - Plan for when (not if) security failsThinking Like an Adversary:- What information would be valuable?- Where are the weak points?- How would I attack this system?- What patterns would I exploit?—### SITUATIONAL AWARENESSCooper Color Code:| State | Awareness | Response ||-------|-----------|----------|| White | Unaware, distracted | Vulnerable || Yellow | Relaxed alertness | Optimal || Orange | Specific concern | Ready to act || Red | Active threat | Fighting/fleeing || Black | Overwhelmed, frozen | Dangerous |Stay in Yellow:- Scan your environment regularly- Notice exits, people, vehicles- Don’t fixate on phone while walking- Trust your instincts (gut feelings)Daily Practice:- When entering a room, note exits- When parking, note surrounding cars- When walking, observe who’s around- When online, question what you see—### INFORMATION DISCIPLINEWhat NOT to Share:- Travel plans before/during trip (post after)- Daily routines and schedules- Home address and neighborhood details- Workplace specifics and schedules- Children’s school names and schedules- Financial information and purchases- Security systems and preparationsSocial Media Guidelines:- Review privacy settings quarterly- Assume everything is public forever- Don’t post in real-time from events- Remove metadata from photos before posting- Consider separate accounts for different purposes- Regularly audit friend/follower listsConversation Security:- Be aware of who can overhear- Don’t discuss sensitive topics in public- Phone calls travel further than you think- Elevators, restaurants, planes = public spaces—### PATTERN DISRUPTIONWhy Patterns Matter:- Predictability enables surveillance- Routines make you an easy target- Patterns reveal valuable informationVary These Regularly:- Routes to work/store- Times you leave home- Restaurants and shops visited- Exercise routines- Social media posting times- Online browsing habitsPractical Implementation:- Have 3+ routes to common destinations- Leave at different times when possible- Try different stores/restaurants- Avoid posting at same time daily- Take different paths while walking dog—### DIGITAL HYGIENE HABITSDaily:- Lock devices when stepping away- Check for software updates- Review app permissions monthly- Clear browser data regularlyWeekly:- Review bank/credit statements- Check login activity on key accounts- Update password manager entries- Scan for malwareMonthly:- Audit social media privacy- Review security camera footage- Check credit reports- Update emergency contactsQuarterly:- Practice emergency procedures- Review and update emergency kits- Conduct personal security assessment- Training/skill development—### PHYSICAL SECURITY HABITSHome:- Lock doors and windows (always)- Use curtains/blinds at night- Don’t advertise when away- Know your neighbors- Secure trash (contains personal info)When Leaving:- Lock all entry points- Use timers on lights- Don’t post about being away- Have someone collect mail/packages- Consider security system monitoringWhen Returning:- Check for signs of entry before entering- Have keys ready before reaching door- Be aware of who’s around- Trust instincts about unsafe situations—### COMMUNICATION SECURITYSecure Communication Hierarchy:1. In person (most secure, no digital trail)2. Signal/Session (encrypted messaging)3. ProtonMail (encrypted email)4. Standard email (not secure)5. SMS/Phone calls (least secure)Communication Guidelines:- Sensitive topics = encrypted channels only- Don’t discuss security over insecure channels- Use code words for sensitive topics if needed- Assume all digital communication is monitored- Verify identity before sharing sensitive info—### EMERGENCY PREPAREDNESS MINDSETBefore Emergency:- Have plans for different scenarios- Practice procedures regularly- Maintain supplies and equipment- Train family members- Establish communication protocolsDuring Emergency:- Stick to established plans- Communicate through pre-arranged channels- Maintain security even in chaos- Document important events- Help trusted network membersAfter Emergency:- Debrief what worked/didn’t- Update plans based on lessons- Replenish used supplies- Check on network members- Return to normal security posture—### RED FLAGS & WARNING SIGNSDigital:- Unusual account activity- Password reset emails you didn’t request- Friends receiving spam from your accounts- Unknown devices logged into your accounts- Increased targeted advertisingPhysical:- Same people/vehicles seen repeatedly- Signs of entry when returning home- Items moved from where you left them- Unusual interest in your activities- Phone/computer behaving strangelyResponse Protocol:1. Document everything2. Change passwords from clean device3. Enable/strengthen 2FA4. Inform trusted contacts5. Consider professional help if persistent—### BUILDING THE HABITStart Small:- Pick one habit to focus on each week- Master it before adding another- Use reminders/alarms initially- Track your progressMake It Automatic:- Attach new habits to existing routines- Create checklists for important tasks- Use password manager for all passwords- Automate what you canStay Consistent:- Security is a practice, not a destination- Regular review and adjustment- Learn from mistakes and near-misses- Share knowledge with trusted network—### QUICK REFERENCE: Daily OPSEC ChecklistMorning:- Lock devices when leaving bed- Check for unusual account activity- Vary your route if leaving homeThroughout Day:- Maintain situational awareness (yellow)- Lock devices when stepping away- Be mindful of conversations in public- Don’t post real-time locationEvening:- Secure home (locks, alarms)- Review day for security concerns- Charge devices in secure location- Prepare for tomorrow (vary routine)Weekly:- Review financial statements- Check account login activity- Assess supply levels- Practice one security skill—*OPSEC Series - Tutorial #5 (Mindset & Habits)*Sources: Former Intelligence Community Professionals, Security Industry Best Practices, Situational Awareness Training Programs

OPSEC Tutorial #9: VPN Usage, Limitations & Best Practices

Difficulty: Intermediate
Time to Complete: 30-40 minutes


Overview

VPNs are widely misunderstood. This tutorial explains what VPNs actually do, their limitations, and how to use them effectively.


WHAT VPNS ACTUALLY DO

A VPN Provides:

  • Encrypts traffic (ISP cant see content)
  • Hides IP from websites
  • Bypasses geographic restrictions
  • Protects on public WiFi

A VPN Does NOT Provide:

  • Complete anonymity (VPN knows who you are)
  • Protection from all tracking
  • Immunity from malware
  • Legal immunity

VPN LIMITATIONS

Trust Shift:

  • You trust ISP less
  • But must trust VPN provider more
  • VPN can see all your traffic
  • VPN logs = potential privacy risk

Technical Limitations:

  • DNS leaks can expose browsing
  • WebRTC can leak real IP
  • VPN drops expose real IP
  • Speed reduction (10-50% typical)

CHOOSING A VPN

Recommended (2026):

  • Mullvad (Sweden, no account needed)
  • ProtonVPN (Switzerland, free tier)
  • IVPN (Gibraltar, transparent)
  • AirVPN (Italy, technical focus)

Avoid:

  • Free VPNs (youre the product)
  • VPNs owned by large corporations
  • VPNs in 5 Eyes countries without audits

Important Factors:

  • Jurisdiction (avoid 5/9/14 Eyes)
  • No-logs policy (verified by audit)
  • Transparent ownership
  • Crypto payment options

ESSENTIAL SETTINGS

Kill Switch:

  • Cuts internet if VPN disconnects
  • Enable this ALWAYS

DNS Settings:

  • Use VPNs DNS servers
  • Test for DNS leaks regularly

Protocol:

  • WireGuard: Modern, fast, secure (recommended)
  • OpenVPN: Proven, slower
  • Avoid: PPTP, L2TP (insecure)

TESTING YOUR VPN

Regular Checks:

  1. IP Leak Test: ipleak.net
  2. DNS Leak Test: dnsleaktest.com
  3. WebRTC Leak Test: WebRTC Leak Test - BrowserLeaks
  4. Kill Switch Test: Disconnect VPN during download

OPSEC Series - Tutorial #9 (VPN Usage)

Sources: EFF Surveillance Self-Defense, VPN Transparency Reports, Technical Security Audits

OPSEC Tutorial #10: Router & Network Security Hardening

Difficulty: Intermediate
Time to Complete: 60-90 minutes


Overview

Your router is the gateway between your home network and the internet. Securing it protects all devices.


INITIAL SETUP

Change Admin Password:

  • Default passwords are publicly known
  • Use 12+ characters, mixed case, numbers
  • Store in password manager

Update Firmware:

  • Check for updates immediately
  • Enable auto-update if available
  • Dont interrupt power during update

Wireless Security:

  • Encryption: WPA3 (or WPA2)
  • Disable WPS (vulnerable)
  • Use 20+ character WiFi password
  • Change default SSID (no personal info)

NETWORK SEGMENTATION

Network Purpose
Main Computers, phones
Guest Visitors
IoT Smart home devices

Why Segment:

  • IoT devices often have poor security
  • Compromised IoT cant reach main devices
  • Guests cant access personal devices

ADVANCED SETTINGS

Disable:

  • Remote administration
  • UPnP (Universal Plug and Play)
  • WPS

DNS Configuration:

  • Quad9: 9.9.9.9 (blocks malware)
  • Cloudflare: 1.1.1.1 (fast, private)
  • NextDNS: Configurable filtering

Firewall:

  • Enable router firewall
  • Block incoming by default
  • Only forward necessary ports

MONITORING

Monthly:

  • Review connected devices
  • Check for unknown devices
  • Verify firmware current

Signs of Compromise:

  • Unknown devices
  • Slow internet speeds
  • Settings changed unexpectedly

OPSEC Series - Tutorial #10 (Network Security)

Sources: NIST Network Security Guidelines, EFF Surveillance Self-Defense, SANS Institute

OPSEC Tutorial #12: Secure Email Practices & Encrypted Communication

Difficulty: Intermediate
Time to Complete: 45-60 minutes


Overview

Email is one of the most vulnerable communication channels. This tutorial covers securing your email accounts and protecting communications.


EMAIL ACCOUNT SECURITY

Enable Two-Factor Authentication (2FA):

Provider 2FA Setup
Gmail myaccount.google.com → Security → 2-Step Verification
Outlook account.microsoft.com → Security → Advanced options
ProtonMail Settings → Security → Two-Factor Authentication
iCloud appleid.apple.com → Sign-In and Security

2FA Methods (Best to Good):

  1. Security key (YubiKey) - Most secure
  2. Authenticator app (Raivo, 2FAS) - Very secure
  3. SMS - Better than nothing

Use Strong, Unique Passwords:

  • Minimum 12 characters
  • Store in password manager
  • Unique for each account

ENCRYPTED EMAIL PROVIDERS

Recommended:

  • ProtonMail (Free-$10/mo) - Most users
  • Tutanota (Free-$12/mo) - Privacy focus
  • Mailbox.org ($1-3/mo) - Business use

Why Encrypted Email:

  • Provider cant read your emails
  • Protected from subpoenas
  • End-to-end encryption

Limitations:

  • Metadata still visible (to/from, date)
  • Both parties need encrypted email for full protection

EMAIL COMPARTMENTALIZATION

Email Type Purpose
Personal Family, close friends
Financial Banks, investments
Shopping Online purchases
Public Forums, social media

Email Aliases:

  • SimpleLogin (forwarding)
  • AnonAddy (forwarding)
  • Apple Hide My Email
  • Firefox Relay

AVOIDING PHISHING

Red Flags:

  • Urgent language (act now!)
  • Suspicious sender address
  • Generic greetings
  • Requests for sensitive info
  • Unexpected attachments

Verification:

  1. Check sender address carefully
  2. Hover over links before clicking
  3. Navigate directly to website
  4. Contact sender through known channel

OPSEC Series - Tutorial #12 (Secure Email)

Sources: EFF Surveillance Self-Defense, ProtonMail Security, NIST Email Guidelines