Secure Digital Organizing: A Practical Guide for Small Groups on Security, Operations, and Decision-Making

A practical guide for small groups of 3–15 people on surviving surveillance, infiltration, and internal fracture while building sustainable organization. Covers threat modeling, Signal hardening, Tails USB, Mullvad VPN, password management, cellular structure, entry/exit protocols, horizontal decision-making, and emergency scenarios (arrest, seizure, account compromise). Integrates with Guide #1 (comms) and Guide #2 (knowledge production) into a complete workflow, with political connections to anti-monopoly, anti-imperialist, and worker autonomy struggle.

Why This Guide Matters

The Digital Autonomy Infrastructure Guide (#1) covered communication and collaboration tools. The Autonomous Knowledge Production Guide (#2) covered knowledge production toolchains. The decisive question remains: how do you bind these tools into organized practice?

Tools alone do not make an organization. In South Korea, groups operating under the shadow of the National Security Act, labor unions confronting chaebol and state power, research collectives producing anti-imperialist discourse, activist networks advocating for minority rights — all face an adversary more fundamental than technical vulnerabilities: surveillance, infiltration, and internal fracture.

This guide enables small groups of 3–15 people to answer:

  1. Who threatens you? — Threat modeling to set realistic defense lines
  2. How to minimize digital traces? — Layered defense with Signal hardening, Tails, Tor, VPN
  3. How to protect the inside? — Need-to-Know, cellular structure, entry/exit protocols
  4. How to decide together? — Horizontal decision-making, trust building, conflict management
  5. How to prepare for worst-case scenarios? — Arrest, seizure, account compromise response

Core principle: Security is not a technical problem — it is a relational one. The strongest encryption is powerless against an insider's betrayal. The most sophisticated anonymity tools collapse from a single user error. This guide addresses technology and culture, tools and trust, defense and openness together.

Threat Modeling: Who Is Your Adversary?

All security begins with a threat model. The iron rule of security: "Protect everything and you protect nothing." Start with Activist Handbook's five questions:

  1. What must be protected? — Members' real names, addresses, contacts, internal discussions, future plans, sensitive data
  2. From whom? — Police, intelligence agencies (NIS, Police Security Investigation Unit), hostile hackers/trolls, service platforms (Kakao, Google), informants
  3. How badly do they want this information? — How threatening is your activity to power?
  4. What harm results from exposure? — Arrest, termination, social destruction, organizational collapse
  5. What will you sacrifice to prevent it? — Time, money, inconvenience, some organizational openness
Threat ActorCapabilitiesSouth Korean Specifics
State IntelligenceWiretapping, physical tracking, account seizure, undercover investigation, informant operationNational Security Act 'anti-state organization' designation, Communications Privacy Act exceptions
PoliceProtest intelligence, arrest, search & seizure, mobile forensicsAssembly and Demonstration Act preemptive detention, dedicated Security Investigation Unit
Private PlatformsData provision, account suspension, censorship, algorithmic detectionKakaoTalk lacks E2EE (except Secret Chat), plaintext server storage. Naver/Kakao cooperate with state agencies
Hostile Hackers/TrollsPhishing, credential theft, DDoS, malware, social engineeringOrganized harassment from far-right communities, doxxing
Internal ThreatsInformation leaks, informing, provocative actionsState informant operation history, plea bargain pressure upon arrest

Action: Today, gather all members and have each person write answers to these five questions and share. Recognizing that each member perceives threats differently is itself the first defense line. Use the most vulnerable member (precarious worker, foreign national, person with prior conviction, caregiver) as the organization's baseline threat level.

Stage 1: Start Today (Free, 2 Hours)

Signal Hardening — Truly Secure Communication

Guide #1 recommended Signal, but installation alone is insufficient. Signal's true security begins with Safety Number verification.

Safety Number Verification — Core MITM Defense

  1. Signal conversation → tap contact name → 'View Safety Number'
  2. Must be done in person (offline) via QR code scan — this is the trust anchor for Signal's E2EE guarantee.
  3. Remote members: voice call and read Safety Number digits one by one for verification.
  4. If Safety Number change notification appears: the contact changed devices, suffered a SIM swap attack, or a man-in-the-middle attack is occurring. Never send sensitive content before re-verification.

Additional Signal Settings

  • Registration Lock: Settings → Account → Enable Registration Lock. Prevents SIM swap re-registration.
  • Disappearing Messages: Conversation settings → Disappearing messages → Set default timer (1 day–1 week recommended based on sensitivity).
  • Screen Security: Settings → Privacy → Enable Screen Security. Blocks screenshots and app switcher preview.
  • Disable Relay Calls: Settings → Privacy → Advanced → Disable relay calls. Prevents calls from routing through Signal servers (IP exposure prevention).

Password Manager — Foundation of All Security

Password reuse is the most common and destructive vulnerability. One compromised account cascades into total exposure.

Recommended: Bitwarden (cloud sync, free tier sufficient) or KeePassXC (local file-based, no sync). Bitwarden balances convenience and security well. KeePassXC suits extreme offline security.

Actions:

  • Create Bitwarden account → set master password as 6+ word random passphrase (Diceware method).
  • Enable 2FA (TOTP — use Aegis or Raivo app).
  • Replace all critical account passwords (Signal, Matrix, email, Git, cloud) with Bitwarden-generated random 16+ character passwords.

2FA Hardening

SMS authentication is vulnerable to SIM swapping. Use TOTP (Time-based One-Time Password) apps.

Recommended: Aegis (Android) or Raivo (iOS) — both open-source with encrypted backup support. Prefer these over Google Authenticator: if Google data is breached, your account and auth codes shouldn't be tied to the same company.

Device Encryption — Preparing for Physical Seizure

  • Windows: BitLocker (Pro+) or VeraCrypt (all editions). Create an additional VeraCrypt virtual encrypted volume for sensitive work.
  • Mac: Enable FileVault (System Settings → Security → FileVault). Store recovery key in Bitwarden.
  • Linux: Choose LUKS encryption during installation (default in most distributions).
  • Smartphone: Android/iOS default full-disk encryption is already active, but short PINs defeat it. Set at least 8-digit PIN or password.

VPN — First Network Defense Line

Recommended: Mullvad VPN — Sweden-based, no logs, anonymous accounts (16-digit number only), cash/crypto payment. ~€5/month.

Why Mullvad: In 2023, Swedish police raid proved no customer data existed to execute the warrant. Proton VPN is a solid alternative.

Configuration: Use WireGuard protocol (faster and lighter than OpenVPN). Enable kill switch — instantly cuts internet if VPN drops, preventing IP leak.

Stage 2: This Week (2–4 Hours, Small Cost)

Tails — Traceless Work Environment

Tails (The Amnesiac Incognito Live System) is a complete OS booting from USB, routing all traffic through Tor and erasing all traces on shutdown. Essential for sensitive document work, anonymous research/analysis, and confidential meeting preparation.

USB Creation (30 min)

  1. Prepare two 8GB+ USB drives (one for persistent storage, one for install media).
  2. Download latest image from tails.net.
  3. Write image to USB #1 using balenaEtcher or GNOME Disks.
  4. Boot from USB #1 → Tails Greeter → Set up Persistent Storage → Create Persistent Storage on USB #2.
  5. Boot from USB #2 and verify normal operation.

What Tails Enables

  • Tor Browser: Default browser. All web traffic routes through Tor. .onion site access.
  • Thunderbird: Tor-routed email. Use with anonymous ProtonMail/TutaNota accounts.
  • KeePassXC: Offline password management. Store password DB in Tails Persistent Storage.
  • Electrum: Bitcoin wallet. Tor-routed transactions.
  • MAT2 (Metadata Anonymization Toolkit): Strips metadata (author, GPS, date) from PDFs, images, documents. Apply to all files before distribution.

Know the limits: Tor traffic can be observed at entry and exit nodes. Do not assume protection against a global adversary (NSA-level). Against South Korean police/NIS-level adversaries, it provides meaningful defense.

Building Security Culture — Practice Beyond Tools

Technical tools are 30% of security. The remaining 70% is culture.

Need-to-Know Principle

All information is shared only with those who "need to know." Member A should be able to collaborate without knowing Member B's real name. Collaboration by pseudonym, anonymous email, and Matrix ID should be the default.

Cellular Structure

Group 3–5 people into one cell. Only one representative connects between cells. If one cell is exposed, the entire organization is not. This precisely aligns with the security dimension of Leninist organizational theory.

Channel Separation Discipline

  • Daily chat: Signal group — operations, scheduling, general discussion.
  • Sensitive discussion: Matrix encrypted room — anonymous accounts only, read receipts disabled.
  • Emergency contact: Signal disappearing messages — "Code Red" keyword, read-once-destroy.
  • Never: Mention organizational content on KakaoTalk. One mistake can invalidate three months of security work.

Entry and Exit Protocols

New Member Entry (Trust Building)

  1. Recommendation from 2+ existing members.
  2. 2–4 week observation period — limited participation without sensitive information access.
  3. In-person meeting, then unanimous (or no objection) decision for formal entry.
  4. Complete security onboarding: verify completion of all Stage 1 items in this guide.

Member Exit (Damage Control)

  1. Immediately revoke all account permissions (Matrix room removal, shared folder access, Git repo access).
  2. Change all passwords and encryption keys the exiting member knew.
  3. Re-verify Safety Numbers for all rooms/channels the exiting member had access to.
  4. If malicious exit suspected: consider temporary operational freeze and communication channel replacement.

Stage 3: Next Month and Beyond (Ongoing Practice)

Decision-Making Structure — Horizontality Doesn't Happen Spontaneously

Leaderless organizations are a myth. In reality, shadow leaders emerge, accountability evaporates, and conflicts worsen. Explicit decision-making structures are necessary.

Small Group Decision Methods Compared

MethodWhen to UseStrengthsWatch For
Consensus≤5 members, high trustFull agreement, no post-decision defectionSlow, minority veto abuse possible
Modified Consensus6–15 members, operational decisionsOnly active objection is veto. Mere discomfort passes"Discomfort" vs "objection" can blur
DelegationSpecialist domains (security, servers, finances)Fast expert judgmentScope and term must be explicitly documented to prevent power concentration
Majority VoteEmergencies, time constraintsFastMinority defection risk, fracture potential

Action: In regular meetings (weekly, in-person or Signal voice call), rotate roles — facilitator, note-taker, timekeeper. Role rotation prevents power concentration and builds collective ownership.

Emergency Scenario Preparation

Scenario 1: Member Arrested

  • Immediately issue 'Code Red' upon arrest awareness → all members shorten Signal disappearing timer to 1 hour.
  • Change all passwords for accounts/directories the arrested member could access.
  • Remotely wipe arrested member's devices if possible (Android Find My Device, iOS Find My — only with prior consent).
  • Freeze all activity for 48 hours. Assess situation before deciding to resume.
  • Advance prep: Every member carries a police interrogation response card — three phrases only: "I invoke my right to remain silent," "I request an attorney," "Notify my family."

Scenario 2: Search and Seizure

  • Always store Tails USB separately — in a location not included in the search warrant scope.
  • Store primary data encrypted on Nextcloud + keep only minimal data on local devices.
  • Regularly delete Matrix room backups (history) — "keep only what you need" principle.

Scenario 3: Account Compromised

  • Immediately force-remove compromised account from Matrix rooms.
  • Re-verify all Signal Safety Numbers.
  • Rotate all Git repo access keys.
  • Identify compromise vector (phishing, malware, social engineering?) and share with all members.

Integrated Workflow: All Three Guides Combined

  1. Morning: Check daily schedule via Signal (12-hour disappearing timer). Log in via Bitwarden.
  2. Work: Push Markdown drafts to Forgejo (Git). Manage references with Zotero. Real-time co-edit with team via CryptPad. First-pass translation with DeepL, refinement with DeepSeek API.
  3. Sensitive Work: Boot Tails → access via Tor → authenticate with KeePassXC → strip metadata from sensitive documents with MAT2 before distribution.
  4. Evening Meeting: Discuss in Matrix room (read receipts off). Switch to Signal voice call if needed.
  5. Backup: Auto-sync work outputs to self-hosted server via Nextcloud.
  6. Weekly Check: Verify Safety Numbers, review account activity logs, repeat security training (when new members present).

In this workflow, Google, Microsoft, Naver, Kakao, Notion, Slack, and Zoom are all unnecessary. Everything runs on self-owned infrastructure.

Security Caveats and Limitations

  • This guide does not fully defend against nation-state-level attacks. Targeted investigation by NSA or NIS deploys zero-day vulnerabilities, physical surveillance, and legal wiretap warrants. This guide defends against routine surveillance, opportunistic data collection, and mid-level threats.
  • Security and convenience are inversely proportional. Booting Tails is inconvenient. But less inconvenient than being arrested. Find the right balance for your organization's threat level.
  • Perfect security does not exist. The weakest link is always human. Regular security culture review and mutual checking are the best defense.
  • The tools in this guide reflect May 2026. Software evolves, vulnerabilities are discovered, new tools emerge. Watch for Matrix 2.0, Signal protocol updates, and post-quantum cryptography transitions.

Political Connection: Security Is Autonomous Capacity

  • Anti-monopoly: Independence from Google, Microsoft, Naver, and Kakao platforms means escaping the chaebol data-extraction and surveillance ecosystem. This is daily anti-monopoly praxis.
  • Anti-imperialism: Mullvad (Sweden), Tails (decentralized), Matrix (UK nonprofit foundation) — all core tools are outside US and South Korean jurisdiction. Daily resistance against imperialist data sovereignty.
  • Worker autonomy: The capacity to build and operate your own security infrastructure is the capacity to control part of the means of production. This is the foundation enabling cooperatives, labor unions, and autonomous organizations to operate sustainably without dependence on external platforms.

When a cell operates according to this guide for six months, it becomes not merely a "security-aware group" but an autonomous unit with its own communication, production, and decision-making infrastructure. When such autonomous units connect, organized power beyond comprador-monopoly platform capitalism begins to form.

References

Checklist

  • Threat modeling meeting completed — all members answered the 5 questions
  • Signal Safety Numbers verified in person for all members
  • Signal: Registration Lock, disappearing timers, screen security, relay calls disabled
  • Bitwarden/KeePassXC installed and master passphrase set
  • All critical account passwords replaced with random 16+ characters
  • 2FA (TOTP) enabled — SMS authentication disabled
  • Device encryption active (BitLocker/FileVault/LUKS)
  • Mullvad VPN subscribed and configured
  • Tails USB created with Persistent Storage
  • MAT2 metadata stripping tested
  • Channel separation discipline established: Signal (daily), Matrix (sensitive), KakaoTalk (forbidden)
  • Entry and exit protocols documented
  • Decision-making method agreed and documented
  • Emergency scenario cards produced and distributed
  • Police interrogation response cards produced and carried