Tailscale & WireGuard Zero-Trust Mesh Networking Architecture

--- description: Tailscale & WireGuard Zero-Trust Mesh Networking Architecture - Production zero-trust networking standard using Tailscale and WireGuard. Replaces public IP exposure and legacy VPN concentrators with peer-to-peer encrypted mesh tunnels, tag-based ACL governance, and MagicDNS routing. globs: **/*tailscale*.yaml, **/*wireguard*.conf, infrastructure/**/*.tf alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/tailscale-wireguard-mesh-networking" --- # Tailscale & WireGuard Zero-Trust Mesh Networking Architecture > **Severity**: CRITICAL | **Category**: devops > **Anti-Pattern Warning**: AI binds internal PostgreSQL and Redis ports to 0.0.0.0/0 on cloud VMs, exposing data to the public internet. ## System Constraints You are a zero-trust network security architect. When provisioning internal infrastructure (databases, caches, admin portals), NEVER bind listening ports to 0.0.0.0 on public network interfaces. Always bind to Tailscale interface IP ranges (100.64.0.0/10), enforce tag-based ACL policies, and use ephemeral auth keys for cloud instances. ## Strict Guidelines - Bind private databases and management interfaces exclusively to the Tailscale interface (tailscale0 / 100.x.y.z) or localhost. - Enforce least-privilege connectivity via Tailscale ACL tags (e.g. tag:prod-api can connect only to tag:prod-db:5432). - Use reusable ephemeral auth keys (tskey-auth-...) with tag pre-assignment for CI/CD runners and autoscaling cluster instances. - Enable MagicDNS with search paths to resolve internal microservices deterministically without maintaining manual /etc/hosts entries. ## Bad vs Good Implementations ### Tailscale Tag-Based ACL Policy vs Open Public Port Exposure #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Directly exposes database authentication endpoints to automated brute-force botnets on the public internet. ```json { "_comment": "ANTI-PATTERN: Overly permissive wildcard ACL exposing internal database to all IPs", "acls": [ { "action": "accept", "src": ["*"], "dst": ["*:5432"] } ] } ``` #### Production Standard (Correct) > **Standard**: Enforces cryptographic end-to-end WireGuard tunnels where traffic is mathematically unreachable from outside the mesh. ```json // PRODUCTION STANDARD: Tailscale HuJSON Declarative ACL Policy { "tagOwners": { "tag:prod-api": ["group:infra-leads"], "tag:prod-db": ["group:infra-leads"], "tag:admin": ["group:secops"] }, "acls": [ // Production API can only communicate with database on port 5432 { "action": "accept", "src": ["tag:prod-api"], "dst": ["tag:prod-db:5432"] }, // Engineers in secops can SSH into servers via Tailscale SSH { "action": "accept", "src": ["tag:admin"], "dst": ["tag:prod-api:22", "tag:prod-db:22"] } ], "ssh": [ { "action": "check", "src": ["tag:admin"], "dst": ["tag:prod-api", "tag:prod-db"], "users": ["ubuntu", "root"] } ] } ``` ### Ephemeral Auto-Registration for Auto-scaling Nodes #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Blocks startup waiting for a human to click a browser authentication link. ```bash # ANTI-PATTERN: Interactive login prompt during automated machine boot tailscale up ``` #### Production Standard (Correct) > **Standard**: Joins the mesh securely in seconds and automatically cleans up the node record when the instance terminates. ```bash # PRODUCTION STANDARD: Headless ephemeral registration with pre-assigned tags tailscale up --authkey="${TAILSCALE_EPHEMERAL_KEY}" --hostname="api-worker-$(hostname)" --ssh --reset ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Tailscale & WireGuard Zero-Trust Mesh Networking Architecture

Tailscale & WireGuard Zero-Trust Mesh Networking Architecture defines an industrial-grade behavioral standard for devops engineering. Production zero-trust networking standard using Tailscale and WireGuard. Replaces public IP exposure and legacy VPN concentrators with peer-to-peer encrypted mesh tunnels, tag-based ACL governance, and MagicDNS routing. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: AI binds internal PostgreSQL and Redis ports to 0.0.0.0/0 on cloud VMs, exposing data to the public internet. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	AI binds internal PostgreSQL and Redis ports to 0.0.0.0/0 on cloud VMs, exposing data to the public internet.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Bind private databases and management interfaces exclusively to the Tailscale interface (tailscale0 / 100.x.y.z) or localhost.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Enforce least-privilege connectivity via Tailscale ACL tags (e.g. tag

Enforce least-privilege connectivity via Tailscale ACL tags (e.g. tag:prod-api can connect only to tag:prod-db:5432).

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Use reusable ephemeral auth keys (tskey-auth-...) with tag pre-assignment for CI/CD runners and autoscaling cluster instances.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Enable MagicDNS with search paths to resolve internal microservices deterministically without maintaining manual /etc/hosts entries.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Tailscale & WireGuard Zero-Trust Mesh Networking Architecture critical for AI coding assistants?

Production zero-trust networking standard using Tailscale and WireGuard. Replaces public IP exposure and legacy VPN concentrators with peer-to-peer encrypted mesh tunnels, tag-based ACL governance, and MagicDNS routing. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (AI binds internal PostgreSQL and Redis ports to 0.0.0.0/0 on cloud VMs, exposing data to the public internet.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.