How to choose a VPN: a practical threat-model checklist

A threat-model-led guide to choosing a VPN: match features to risks, ask the right questions about logs and jurisdiction, and use a simple checklist to pick a provider that meets your privacy and security goals.

Vpn, vpn for home security, vpn for android and vpn for mobile – How to choose a VPN: a practical threat-model checklist
Image by StefanCoders from Pixabay

Picking a VPN often feels like comparing slogans. Marketing focuses on speed, server count and celebrity endorsements, but the practical question for privacy-conscious users is simpler: which service reduces the specific risks you care about? This guide maps common threat models to VPN features, lists the questions to ask a provider, and offers a compact decision checklist you can use when comparing services.

Map your threat model to VPN features

Start by being explicit about what you want to protect and from whom. A one-size-fits-all VPN rarely exists; features trade off against cost, complexity and performance.

Common threat models

  • Casual privacy from advertising and ISP tracking: Hide your IP from trackers and stop ISPs from easily building connection logs. Look for encryption, basic leak protection and a trustworthy privacy policy.
  • Surveillance by a state or sophisticated attacker: Protection against active tampering, metadata correlation and legal pressure. Prioritise strong protocols, minimal logging, clearely defined jurisdiction and independent audits.
  • Bypassing regional restrictions: Reliable geolocation options and good performance from nearby servers; streaming-focused servers are sometimes useful but check their privacy trade-offs.
  • Operational security for journalists, activists or sensitive transfers: Prefilter for features such as adversary-resistant server architecture (RAM-only disks), obfuscation (to defeat DPI), and firm policies on warrant responses.

Feature-to-threat mapping

  • Logging policy + audits: Vital for defending against subpoenas and data requests. Minimal logs reduce what can be handed over; audits increase trust.
  • Jurisdiction: Determines how easily authorities can compel data and whether gag orders are legal options.
  • Protocol and encryption: Affects resistance to interception and performance. Some protocols are better for mobile and low-latency use.
  • Leak protections & kill switch: Prevent accidental exposure of your real IP when the VPN drops.
  • Server architecture: RAM-only or physically controlled servers limit persistent data storage and simplify audits.

What to ask about logging, audits and jurisdiction

Office, business, accountant and accounting – What to ask about logging, audits and jurisdiction
Image by Firmbee from Pixabay

Don’t accept a short “no-logs” line as proof. Ask precise questions and verify answers where possible.

Key vendor questions

  1. What exact data do you store about connections and accounts? (Examples: timestamps, source IPs, session durations, bandwidth totals.)
  2. Are logs retained, and for how long? If retained, where and why?
  3. Have you had independent audits of your infrastructure and logging claims? Who conducted them and what scope was audited?
  4. Do you operate your own physical servers or lease virtual machines from cloud providers?
  5. What is your legal jurisdiction and do you have any obligations to disclose customer data under local laws?
  6. Do you publish a transparency report or a warrant canary?

Ask for concrete documentation. An audited no-logs claim and published transparency reports are stronger signals than marketing text.

Leak protections, protocol choices and kill switches

Technical controls prevent accidental data exposure and influence resilience to active attacks.

Leak protections

  • DNS leaks: Ensure the VPN uses its own DNS resolvers or offers secure DNS options.
  • IPv6 leaks: If a provider does not support or properly route IPv6, disable IPv6 on the device or choose a provider that handles it safely.
  • WebRTC and browser leaks: Browsers can reveal local IPs; use browser settings or extensions to control WebRTC alongside the VPN.

Protocol and encryption

WireGuard and OpenVPN are common options; WireGuard is generally faster and simpler, while OpenVPN is widely supported and flexible. Choose a provider that supports modern, well-audited protocols and exposes configuration options if you need them.

Kill switches and connection handling

  • A system-level kill switch blocks all traffic outside the VPN tunnel if the connection drops—essential for high-risk users.
  • Application-level kill switches let you protect select apps while allowing other traffic to continue locally.

Performance and multi-device support

Performance matters because a slow VPN gets turned off. Consider these practical checks:

  • Server locations and proximity: More local servers usually mean better latency.
  • Concurrent connections: Count how many devices you need simultaneously and check the provider limit.
  • Platform support: Verify native apps for your OS, plus router or smart-TV options if needed.
  • Connection management: Does the client recover gracefully from network changes, and does it support split tunnelling if you want selective routing?

Alternatives and complementary tools

VPNs are one tool in a broader privacy toolbox. Understand trade-offs before choosing an alternative.

Proxies

Proxies can hide your IP for specific applications but generally do not encrypt traffic end-to-end. They are lighter-weight but provide weaker privacy guarantees than a VPN.

Tor

Tor is an anonymity network that routes traffic across volunteer-operated relays and is not a drop-in replacement for a VPN. It offers strong anonymity for supported use cases but comes with performance and compatibility limitations and should be used with its own threat model in mind.

Split tunnelling

Split tunnelling lets you route only selected apps or destinations via the VPN and is useful when you need local and private access simultaneously. That convenience can reduce protection for misconfigured apps, so use rules carefully.

A practical decision checklist

Use this checklist when you evaluate a candidate VPN provider. Treat missing answers as a red flag.

  • Define your threat model (advertisers, ISP, state-level, operational). Match features to that threat.
  • Request the exact logging policy and retention times; prefer providers with independent audits and transparency reports.
  • Confirm jurisdiction and server ownership model (physical vs virtual servers).
  • Verify leak protections (DNS, IPv6, WebRTC) and presence of a reliable kill switch.
  • Check supported protocols (WireGuard/OpenVPN) and whether you can configure the client.
  • Test performance and confirm concurrent connection limits and platform support.
  • Decide on extras: split tunnelling, obfuscation, RAM-only servers, and streaming or P2P policies.
  • Balance convenience and risk: if you need strong anonymity, consider Tor or layered approaches rather than solely relying on a consumer VPN.

For more on how browsers can leak identity through technical signals, read our guide Understanding Browser Fingerprinting: A Practical Privacy Guide. If you use mobile devices, our App permissions deep dive explains how to reduce app-level data exposure that a VPN cannot solve.

Closing: pick for risk, not hype

Choose a VPN by mapping features to the specific adversaries and risks you face. Ask targeted questions about logs, audits and jurisdiction; test technical protections such as kill switches and leak handling; and consider whether alternatives like Tor or proxies better match your goals. Keep a short comparison checklist when you evaluate services—clarity about risk is the best defence against marketing claims.

Share this articleXinf

About this article

  • Published November 15, 2026 · Last reviewed November 13, 2026
  • Written for defensive and educational purposes. Only test techniques on systems you own or have permission to assess.
  • Spotted an error or have new information? Tell our team and we will review it.

Written by

Maya Delacroix

Focuses on practical threat analysis and hands-on defensive techniques for small teams.

More articles by this author →

Join the discussion

Your email is never published. Please be respectful, and never post passwords, personal data or working exploits.