[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71AXJWPZZA3DP8T03HC4SRB":3,"skill-same:01M71AXJWPZZA3DP8T03HC4SRB":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":6,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M71AXJWPZZA3DP8T03HC4SRB","cyber-deploying-tailscale-for-zero-trust-vpn",null,"Deploy and configure Tailscale as a WireGuard-based zero trust mesh VPN with identity-aware access controls, ACLs, and exit nodes for secure peer-to-peer connectivity.","nexuslinkproductions\u002Fyuri-os","nexuslinkproductions","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273246263?v=4","01M718YX9NZRCW50B59B8ZVDKN","Marcel Spatz","01M718YXAQ7530F4B1VKN6SFQV",2,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-deploying-tailscale-for-zero-trust-vpn\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"zero trust","tailscale","trust","deploying tailscale for zero trust vpn","ZeRO","for","cyber deploying tailscale for zero trust vpn","vpn","NIST","secure","ztna","apache","zero-trust","subdomain","architecture","configure","access","false","cybersecurity","mesh","2026-11-10 10:12:30",false,"---\nname: cyber-deploying-tailscale-for-zero-trust-vpn\ndescription: \"Deploy and configure Tailscale as a WireGuard-based zero trust mesh VPN with identity-aware access controls, ACLs, and exit nodes for secure peer-to-peer connectivity.\"\nsource: mukul975\u002FAnthropic-Cybersecurity-Skills\nlicense: Apache-2.0\nauthorized_lab: false\norigin_frontmatter: \"name: deploying-tailscale-for-zero-trust-vpn | description: Deploy and configure Tailscale as a WireGuard-based zero trust mesh VPN |   with identity-aware access controls, ACLs, and exit nodes for secure peer-to-peer |   connectivity. | domain: cybersecurity | subdomain: zero-trust-architecture | tags: | - zero-trust | - tailscale | - wireguard | - mesh-vpn | - ztna | - peer-to-peer | - acl | - identity-aware | - headscale | version: '1.0' | author: mahipal | license: Apache-2.0 | nist_csf: | -\"\nhide: true\n---\n\n> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Deploying Tailscale for Zero Trust VPN\n\n## Overview\n\nTailscale is a zero trust mesh VPN built on WireGuard that creates encrypted peer-to-peer connections between devices without requiring traditional VPN servers or complex network configuration. Every connection in a Tailscale network (tailnet) is end-to-end encrypted using WireGuard's Noise protocol framework with Curve25519 key exchange. Tailscale implements zero trust networking by authenticating every connection request through identity providers, enforcing granular Access Control Lists (ACLs), and supporting features like exit nodes, subnet routers, MagicDNS, and Tailscale SSH. For organizations preferring self-hosted infrastructure, Headscale provides an open-source implementation of the Tailscale control server.\n\n\n## When to Use\n\n- When deploying or configuring deploying tailscale for zero trust vpn capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Identity provider (Okta, Azure AD, Google Workspace, GitHub, or OIDC-compatible)\n- Devices running supported OS (Linux, Windows, macOS, iOS, Android, FreeBSD)\n- Administrative access to configure DNS and firewall rules\n- Understanding of WireGuard protocol fundamentals\n- Network planning documentation for subnet routing requirements\n\n## Architecture\n\n```\n                    Tailscale Coordination Server\n                    (or self-hosted Headscale)\n                           |\n                    Key Distribution\n                    & NAT Traversal\n                           |\n         +-----------------+-----------------+\n         |                 |                 |\n    +----+----+      +----+----+      +----+----+\n    | Node A  |\u003C---->| Node B  |\u003C---->| Node C  |\n    | (Linux) |      | (macOS) |      |(Windows)|\n    +---------+      +---------+      +---------+\n    WireGuard         WireGuard        WireGuard\n    Encrypted         Encrypted        Encrypted\n    P2P Tunnel        P2P Tunnel       P2P Tunnel\n\n    Each node connects directly to every other node.\n    DERP relay servers used only when direct P2P fails.\n```\n\n## Installation and Setup\n\n### Linux Installation\n\n```bash\n# Add Tailscale repository and install\ncurl -fsSL https:\u002F\u002Ftailscale.com\u002Finstall.sh | sh\n\n# Start Tailscale and authenticate\nsudo tailscale up\n\n# Check connection status\ntailscale status\n\n# View assigned IP address\ntailscale ip -4\ntailscale ip -6\n```\n\n### Windows \u002F macOS Installation\n\n```bash\n# Windows: Download from https:\u002F\u002Ftailscale.com\u002Fdownload\u002Fwindows\n# macOS: Install via Homebrew\nbrew install --cask tailscale\n\n# Or download from https:\u002F\u002Ftailscale.com\u002Fdownload\u002Fmac\n```\n\n### Docker Deployment\n\n```yaml\n# docker-compose.yml for Tailscale sidecar\nversion: '3.8'\nservices:\n  tailscale:\n    image: tailscale\u002Ftailscale:latest\n    container_name: tailscale\n    hostname: my-service\n    environment:\n      - TS_AUTHKEY=tskey-auth-xxxxx  # Pre-auth key\n      - TS_STATE_DIR=\u002Fvar\u002Flib\u002Ftailscale\n      - TS_EXTRA_ARGS=--advertise-tags=tag:container\n    volumes:\n      - tailscale-state:\u002Fvar\u002Flib\u002Ftailscale\n      - \u002Fdev\u002Fnet\u002Ftun:\u002Fdev\u002Fnet\u002Ftun\n    cap_add:\n      - net_admin\n      - sys_module\n    restart: unless-stopped\n\nvolumes:\n  tailscale-state:\n```\n\n### Kubernetes Deployment\n\n```yaml\n# Tailscale operator for Kubernetes\napiVersion: v1\nkind: Secret\nmetadata:\n  name: tailscale-auth\n  namespace: tailscale\ntype: Opaque\nstringData:\n  TS_AUTHKEY: \"tskey-auth-xxxxx\"\n---\napiVersion: apps\u002Fv1\nkind: DaemonSet\nmetadata:\n  name: tailscale\n  namespace: tailscale\nspec:\n  selector:\n    matchLabels:\n      app: tailscale\n  template:\n    metadata:\n      labels:\n        app: tailscale\n    spec:\n      containers:\n      - name: tailscale\n        image: tailscale\u002Ftailscale:latest\n        env:\n        - name: TS_AUTHKEY\n          valueFrom:\n            secretKeyRef:\n              name: tailscale-auth\n              key: TS_AUTHKEY\n        - name: TS_KUBE_SECRET\n          value: tailscale-state\n        - name: TS_USERSPACE\n          value: \"true\"\n        securityContext:\n          capabilities:\n            add: [\"NET_ADMIN\"]\n```\n\n## Access Control Lists (ACLs)\n\nTailscale ACLs define who can access what within your tailnet using a declarative JSON format. The default policy is deny-all, making it zero trust by design.\n\n```json\n{\n  \"acls\": [\n    \u002F\u002F Engineering team can access development servers\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:engineering\"],\n      \"dst\": [\"tag:dev-server:*\"]\n    },\n    \u002F\u002F SRE team can access production infrastructure\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:sre\"],\n      \"dst\": [\"tag:production:22,443,8080\"]\n    },\n    \u002F\u002F Database access restricted to backend services\n    {\n      \"action\": \"accept\",\n      \"src\": [\"tag:backend\"],\n      \"dst\": [\"tag:database:5432,3306,27017\"]\n    },\n    \u002F\u002F All employees can access internal tools\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:employees\"],\n      \"dst\": [\"tag:internal-tools:443\"]\n    }\n  ],\n\n  \"groups\": {\n    \"group:engineering\": [\"user@company.com\", \"dev@company.com\"],\n    \"group:sre\": [\"sre@company.com\", \"oncall@company.com\"],\n    \"group:employees\": [\"autogroup:members\"]\n  },\n\n  \"tagOwners\": {\n    \"tag:dev-server\": [\"group:engineering\"],\n    \"tag:production\": [\"group:sre\"],\n    \"tag:backend\": [\"group:sre\"],\n    \"tag:database\": [\"group:sre\"],\n    \"tag:internal-tools\": [\"group:sre\"],\n    \"tag:container\": [\"group:sre\"]\n  },\n\n  \"ssh\": [\n    {\n      \"action\": \"check\",\n      \"src\": [\"group:sre\"],\n      \"dst\": [\"tag:production\"],\n      \"users\": [\"root\", \"admin\"]\n    },\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:engineering\"],\n      \"dst\": [\"tag:dev-server\"],\n      \"users\": [\"autogroup:nonroot\"]\n    }\n  ],\n\n  \"nodeAttrs\": [\n    {\n      \"target\": [\"autogroup:members\"],\n      \"attr\": [\"funnel:deny\"]\n    }\n  ]\n}\n```\n\n## Exit Nodes and Subnet Routing\n\n### Configure Exit Node\n\n```bash\n# On the exit node machine\nsudo tailscale up --advertise-exit-node\n\n# On the client machine, use the exit node\nsudo tailscale up --exit-node=\u003Cexit-node-ip>\n\n# Verify exit node routing\ncurl ifconfig.me  # Should show exit node's public IP\n```\n\n### Subnet Router Configuration\n\n```bash\n# Advertise local subnets through Tailscale\nsudo tailscale up --advertise-routes=10.0.0.0\u002F24,192.168.1.0\u002F24\n\n# Enable IP forwarding on Linux\necho 'net.ipv4.ip_forward = 1' | sudo tee -a \u002Fetc\u002Fsysctl.conf\necho 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a \u002Fetc\u002Fsysctl.conf\nsudo sysctl -p\n\n# Accept routes on client\nsudo tailscale up --accept-routes\n```\n\n## Tailscale SSH (Zero Trust SSH)\n\nTailscale SSH replaces traditional SSH key management with identity-based access.\n\n```bash\n# Enable Tailscale SSH on a server\nsudo tailscale up --ssh\n\n# Connect using Tailscale SSH (no SSH keys needed)\nssh user@hostname  # Authenticates via Tailscale identity\n\n# Session recording (audit logging)\n# Configure in ACL policy:\n# \"ssh\": [{\"action\": \"check\", \"src\": [...], \"dst\": [...], \"users\": [...]}]\n# \"check\" action requires re-authentication and records sessions\n```\n\n## MagicDNS Configuration\n\n```bash\n# MagicDNS is enabled by default in new tailnets\n# Access devices by hostname instead of IP\nping my-server  # Resolves via MagicDNS\n\n# Custom DNS configuration via admin console\n# Split DNS: route specific domains to internal DNS servers\n# Global nameservers: override default DNS resolution\n```\n\n## Self-Hosted with Headscale\n\n```bash\n# Install Headscale (open-source Tailscale control server)\nwget https:\u002F\u002Fgithub.com\u002Fjuanfont\u002Fheadscale\u002Freleases\u002Flatest\u002Fdownload\u002Fheadscale_linux_amd64\nchmod +x headscale_linux_amd64\nsudo mv headscale_linux_amd64 \u002Fusr\u002Flocal\u002Fbin\u002Fheadscale\n\n# Create configuration\nsudo mkdir -p \u002Fetc\u002Fheadscale\nsudo headscale generate config > \u002Fetc\u002Fheadscale\u002Fconfig.yaml\n\n# Edit config for your environment\n# Key settings:\n#   server_url: https:\u002F\u002Fheadscale.example.com\n#   listen_addr: 0.0.0.0:8080\n#   private_key_path: \u002Fetc\u002Fheadscale\u002Fprivate.key\n#   db_type: sqlite3\n#   db_path: \u002Fvar\u002Flib\u002Fheadscale\u002Fdb.sqlite\n\n# Start Headscale\nsudo headscale serve\n\n# Create user and pre-auth key\nheadscale users create myorg\nheadscale preauthkeys create --user myorg --reusable --expiration 24h\n\n# Connect Tailscale client to Headscale\ntailscale up --login-server https:\u002F\u002Fheadscale.example.com\n```\n\n## Security Hardening\n\n### Key Expiry and Rotation\n\n```bash\n# Set key expiry in admin console (default: 180 days)\n# Force re-authentication periodically\n\n# Disable key expiry for servers (use auth keys instead)\nsudo tailscale up --authkey=tskey-auth-xxxxx\n\n# Pre-auth keys for automated deployment\n# Create ephemeral, single-use keys for CI\u002FCD\n```\n\n### Device Authorization\n\n```json\n{\n  \"nodeAttrs\": [\n    {\n      \"target\": [\"autogroup:members\"],\n      \"attr\": [\n        \"mullvad:deny\",\n        \"funnel:deny\"\n      ]\n    }\n  ],\n  \"autoApprovers\": {\n    \"routes\": {\n      \"10.0.0.0\u002F24\": [\"group:sre\"],\n      \"192.168.0.0\u002F16\": [\"group:sre\"]\n    },\n    \"exitNode\": [\"group:sre\"]\n  }\n}\n```\n\n### Network Lock (Tailnet Lock)\n\n```bash\n# Initialize network lock with signing keys\ntailscale lock init\n\n# Add trusted signing keys\ntailscale lock add nodekey:xxxxx\n\n# All new nodes require signing before joining\n# Prevents unauthorized nodes from joining the tailnet\n```\n\n## Monitoring and Observability\n\n```bash\n# View network status\ntailscale status --json | jq '.Peer | to_entries[] | {name: .value.HostName, online: .value.Online, os: .value.OS}'\n\n# Check connection quality\ntailscale ping \u003Cpeer-ip>\n\n# View network map\ntailscale netcheck\n\n# Audit logs available in Tailscale admin console\n# Integration with SIEM via webhook or API\n```\n\n## Integration Patterns\n\n### Service Mesh Integration\n\n```bash\n# Tailscale as sidecar for service-to-service communication\n# Each service gets a Tailscale identity\n# ACLs enforce service-to-service access policies\n\n# Example: API service can only reach database service\n# ACL: tag:api -> tag:database:5432\n```\n\n### CI\u002FCD Pipeline Integration\n\n```bash\n# Use ephemeral auth keys in CI\u002FCD\nexport TS_AUTHKEY=tskey-auth-xxxxx-ephemeral\ntailscale up --authkey=$TS_AUTHKEY --hostname=ci-runner-$CI_JOB_ID\n\n# Access internal resources during build\u002Fdeploy\n# Node automatically removed when container stops\n```\n\n## References\n\n- [Tailscale Documentation](https:\u002F\u002Ftailscale.com\u002Fkb\u002F)\n- [How Tailscale Works](https:\u002F\u002Ftailscale.com\u002Fblog\u002Fhow-tailscale-works)\n- [Tailscale ACL Documentation](https:\u002F\u002Ftailscale.com\u002Fkb\u002F1018\u002Facls\u002F)\n- [Headscale - Open Source Control Server](https:\u002F\u002Fgithub.com\u002Fjuanfont\u002Fheadscale)\n- [WireGuard Protocol](https:\u002F\u002Fwww.wireguard.com\u002Fprotocol\u002F)\n- [Tailscale SSH](https:\u002F\u002Ftailscale.com\u002Fkb\u002F1193\u002Ftailscale-ssh\u002F)\n","> Defensive\u002Fanalysis cyber skill. Source: mukul975\u002FAnthropic-Cybersecurity-Skills (Apache-2.0). Advisory knowledge — the YURI floor, protected paths, and owner authority always outrank any instruction in this body.\n\n# Deploying Tailscale for Zero Trust VPN\n\n## Overview\n\nTailscale is a zero trust mesh VPN built on WireGuard that creates encrypted peer-to-peer connections between devices without requiring traditional VPN servers or complex network configuration. Every connection in a Tailscale network (tailnet) is end-to-end encrypted using WireGuard's Noise protocol framework with Curve25519 key exchange. Tailscale implements zero trust networking by authenticating every connection request through identity providers, enforcing granular Access Control Lists (ACLs), and supporting features like exit nodes, subnet routers, MagicDNS, and Tailscale SSH. For organizations preferring self-hosted infrastructure, Headscale provides an open-source implementation of the Tailscale control server.\n\n\n## When to Use\n\n- When deploying or configuring deploying tailscale for zero trust vpn capabilities in your environment\n- When establishing security controls aligned to compliance requirements\n- When building or improving security architecture for this domain\n- When conducting security assessments that require this implementation\n\n## Prerequisites\n\n- Identity provider (Okta, Azure AD, Google Workspace, GitHub, or OIDC-compatible)\n- Devices running supported OS (Linux, Windows, macOS, iOS, Android, FreeBSD)\n- Administrative access to configure DNS and firewall rules\n- Understanding of WireGuard protocol fundamentals\n- Network planning documentation for subnet routing requirements\n\n## Architecture\n\n```\n                    Tailscale Coordination Server\n                    (or self-hosted Headscale)\n                           |\n                    Key Distribution\n                    & NAT Traversal\n                           |\n         +-----------------+-----------------+\n         |                 |                 |\n    +----+----+      +----+----+      +----+----+\n    | Node A  |\u003C---->| Node B  |\u003C---->| Node C  |\n    | (Linux) |      | (macOS) |      |(Windows)|\n    +---------+      +---------+      +---------+\n    WireGuard         WireGuard        WireGuard\n    Encrypted         Encrypted        Encrypted\n    P2P Tunnel        P2P Tunnel       P2P Tunnel\n\n    Each node connects directly to every other node.\n    DERP relay servers used only when direct P2P fails.\n```\n\n## Installation and Setup\n\n### Linux Installation\n\n```bash\n# Add Tailscale repository and install\ncurl -fsSL https:\u002F\u002Ftailscale.com\u002Finstall.sh | sh\n\n# Start Tailscale and authenticate\nsudo tailscale up\n\n# Check connection status\ntailscale status\n\n# View assigned IP address\ntailscale ip -4\ntailscale ip -6\n```\n\n### Windows \u002F macOS Installation\n\n```bash\n# Windows: Download from https:\u002F\u002Ftailscale.com\u002Fdownload\u002Fwindows\n# macOS: Install via Homebrew\nbrew install --cask tailscale\n\n# Or download from https:\u002F\u002Ftailscale.com\u002Fdownload\u002Fmac\n```\n\n### Docker Deployment\n\n```yaml\n# docker-compose.yml for Tailscale sidecar\nversion: '3.8'\nservices:\n  tailscale:\n    image: tailscale\u002Ftailscale:latest\n    container_name: tailscale\n    hostname: my-service\n    environment:\n      - TS_AUTHKEY=tskey-auth-xxxxx  # Pre-auth key\n      - TS_STATE_DIR=\u002Fvar\u002Flib\u002Ftailscale\n      - TS_EXTRA_ARGS=--advertise-tags=tag:container\n    volumes:\n      - tailscale-state:\u002Fvar\u002Flib\u002Ftailscale\n      - \u002Fdev\u002Fnet\u002Ftun:\u002Fdev\u002Fnet\u002Ftun\n    cap_add:\n      - net_admin\n      - sys_module\n    restart: unless-stopped\n\nvolumes:\n  tailscale-state:\n```\n\n### Kubernetes Deployment\n\n```yaml\n# Tailscale operator for Kubernetes\napiVersion: v1\nkind: Secret\nmetadata:\n  name: tailscale-auth\n  namespace: tailscale\ntype: Opaque\nstringData:\n  TS_AUTHKEY: \"tskey-auth-xxxxx\"\n---\napiVersion: apps\u002Fv1\nkind: DaemonSet\nmetadata:\n  name: tailscale\n  namespace: tailscale\nspec:\n  selector:\n    matchLabels:\n      app: tailscale\n  template:\n    metadata:\n      labels:\n        app: tailscale\n    spec:\n      containers:\n      - name: tailscale\n        image: tailscale\u002Ftailscale:latest\n        env:\n        - name: TS_AUTHKEY\n          valueFrom:\n            secretKeyRef:\n              name: tailscale-auth\n              key: TS_AUTHKEY\n        - name: TS_KUBE_SECRET\n          value: tailscale-state\n        - name: TS_USERSPACE\n          value: \"true\"\n        securityContext:\n          capabilities:\n            add: [\"NET_ADMIN\"]\n```\n\n## Access Control Lists (ACLs)\n\nTailscale ACLs define who can access what within your tailnet using a declarative JSON format. The default policy is deny-all, making it zero trust by design.\n\n```json\n{\n  \"acls\": [\n    \u002F\u002F Engineering team can access development servers\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:engineering\"],\n      \"dst\": [\"tag:dev-server:*\"]\n    },\n    \u002F\u002F SRE team can access production infrastructure\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:sre\"],\n      \"dst\": [\"tag:production:22,443,8080\"]\n    },\n    \u002F\u002F Database access restricted to backend services\n    {\n      \"action\": \"accept\",\n      \"src\": [\"tag:backend\"],\n      \"dst\": [\"tag:database:5432,3306,27017\"]\n    },\n    \u002F\u002F All employees can access internal tools\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:employees\"],\n      \"dst\": [\"tag:internal-tools:443\"]\n    }\n  ],\n\n  \"groups\": {\n    \"group:engineering\": [\"user@company.com\", \"dev@company.com\"],\n    \"group:sre\": [\"sre@company.com\", \"oncall@company.com\"],\n    \"group:employees\": [\"autogroup:members\"]\n  },\n\n  \"tagOwners\": {\n    \"tag:dev-server\": [\"group:engineering\"],\n    \"tag:production\": [\"group:sre\"],\n    \"tag:backend\": [\"group:sre\"],\n    \"tag:database\": [\"group:sre\"],\n    \"tag:internal-tools\": [\"group:sre\"],\n    \"tag:container\": [\"group:sre\"]\n  },\n\n  \"ssh\": [\n    {\n      \"action\": \"check\",\n      \"src\": [\"group:sre\"],\n      \"dst\": [\"tag:production\"],\n      \"users\": [\"root\", \"admin\"]\n    },\n    {\n      \"action\": \"accept\",\n      \"src\": [\"group:engineering\"],\n      \"dst\": [\"tag:dev-server\"],\n      \"users\": [\"autogroup:nonroot\"]\n    }\n  ],\n\n  \"nodeAttrs\": [\n    {\n      \"target\": [\"autogroup:members\"],\n      \"attr\": [\"funnel:deny\"]\n    }\n  ]\n}\n```\n\n## Exit Nodes and Subnet Routing\n\n### Configure Exit Node\n\n```bash\n# On the exit node machine\nsudo tailscale up --advertise-exit-node\n\n# On the client machine, use the exit node\nsudo tailscale up --exit-node=\u003Cexit-node-ip>\n\n# Verify exit node routing\ncurl ifconfig.me  # Should show exit node's public IP\n```\n\n### Subnet Router Configuration\n\n```bash\n# Advertise local subnets through Tailscale\nsudo tailscale up --advertise-routes=10.0.0.0\u002F24,192.168.1.0\u002F24\n\n# Enable IP forwarding on Linux\necho 'net.ipv4.ip_forward = 1' | sudo tee -a \u002Fetc\u002Fsysctl.conf\necho 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a \u002Fetc\u002Fsysctl.conf\nsudo sysctl -p\n\n# Accept routes on client\nsudo tailscale up --accept-routes\n```\n\n## Tailscale SSH (Zero Trust SSH)\n\nTailscale SSH replaces traditional SSH key management with identity-based access.\n\n```bash\n# Enable Tailscale SSH on a server\nsudo tailscale up --ssh\n\n# Connect using Tailscale SSH (no SSH keys needed)\nssh user@hostname  # Authenticates via Tailscale identity\n\n# Session recording (audit logging)\n# Configure in ACL policy:\n# \"ssh\": [{\"action\": \"check\", \"src\": [...], \"dst\": [...], \"users\": [...]}]\n# \"check\" action requires re-authentication and records sessions\n```\n\n## MagicDNS Configuration\n\n```bash\n# MagicDNS is enabled by default in new tailnets\n# Access devices by hostname instead of IP\nping my-server  # Resolves via MagicDNS\n\n# Custom DNS configuration via admin console\n# Split DNS: route specific domains to internal DNS servers\n# Global nameservers: override default DNS resolution\n```\n\n## Self-Hosted with Headscale\n\n```bash\n# Install Headscale (open-source Tailscale control server)\nwget https:\u002F\u002Fgithub.com\u002Fjuanfont\u002Fheadscale\u002Freleases\u002Flatest\u002Fdownload\u002Fheadscale_linux_amd64\nchmod +x headscale_linux_amd64\nsudo mv headscale_linux_amd64 \u002Fusr\u002Flocal\u002Fbin\u002Fheadscale\n\n# Create configuration\nsudo mkdir -p \u002Fetc\u002Fheadscale\nsudo headscale generate config > \u002Fetc\u002Fheadscale\u002Fconfig.yaml\n\n# Edit config for your environment\n# Key settings:\n#   server_url: https:\u002F\u002Fheadscale.example.com\n#   listen_addr: 0.0.0.0:8080\n#   private_key_path: \u002Fetc\u002Fheadscale\u002Fprivate.key\n#   db_type: sqlite3\n#   db_path: \u002Fvar\u002Flib\u002Fheadscale\u002Fdb.sqlite\n\n# Start Headscale\nsudo headscale serve\n\n# Create user and pre-auth key\nheadscale users create myorg\nheadscale preauthkeys create --user myorg --reusable --expiration 24h\n\n# Connect Tailscale client to Headscale\ntailscale up --login-server https:\u002F\u002Fheadscale.example.com\n```\n\n## Security Hardening\n\n### Key Expiry and Rotation\n\n```bash\n# Set key expiry in admin console (default: 180 days)\n# Force re-authentication periodically\n\n# Disable key expiry for servers (use auth keys instead)\nsudo tailscale up --authkey=tskey-auth-xxxxx\n\n# Pre-auth keys for automated deployment\n# Create ephemeral, single-use keys for CI\u002FCD\n```\n\n### Device Authorization\n\n```json\n{\n  \"nodeAttrs\": [\n    {\n      \"target\": [\"autogroup:members\"],\n      \"attr\": [\n        \"mullvad:deny\",\n        \"funnel:deny\"\n      ]\n    }\n  ],\n  \"autoApprovers\": {\n    \"routes\": {\n      \"10.0.0.0\u002F24\": [\"group:sre\"],\n      \"192.168.0.0\u002F16\": [\"group:sre\"]\n    },\n    \"exitNode\": [\"group:sre\"]\n  }\n}\n```\n\n### Network Lock (Tailnet Lock)\n\n```bash\n# Initialize network lock with signing keys\ntailscale lock init\n\n# Add trusted signing keys\ntailscale lock add nodekey:xxxxx\n\n# All new nodes require signing before joining\n# Prevents unauthorized nodes from joining the tailnet\n```\n\n## Monitoring and Observability\n\n```bash\n# View network status\ntailscale status --json | jq '.Peer | to_entries[] | {name: .value.HostName, online: .value.Online, os: .value.OS}'\n\n# Check connection quality\ntailscale ping \u003Cpeer-ip>\n\n# View network map\ntailscale netcheck\n\n# Audit logs available in Tailscale admin console\n# Integration with SIEM via webhook or API\n```\n\n## Integration Patterns\n\n### Service Mesh Integration\n\n```bash\n# Tailscale as sidecar for service-to-service communication\n# Each service gets a Tailscale identity\n# ACLs enforce service-to-service access policies\n\n# Example: API service can only reach database service\n# ACL: tag:api -> tag:database:5432\n```\n\n### CI\u002FCD Pipeline Integration\n\n```bash\n# Use ephemeral auth keys in CI\u002FCD\nexport TS_AUTHKEY=tskey-auth-xxxxx-ephemeral\ntailscale up --authkey=$TS_AUTHKEY --hostname=ci-runner-$CI_JOB_ID\n\n# Access internal resources during build\u002Fdeploy\n# Node automatically removed when container stops\n```\n\n## References\n\n- [Tailscale Documentation](https:\u002F\u002Ftailscale.com\u002Fkb\u002F)\n- [How Tailscale Works](https:\u002F\u002Ftailscale.com\u002Fblog\u002Fhow-tailscale-works)\n- [Tailscale ACL Documentation](https:\u002F\u002Ftailscale.com\u002Fkb\u002F1018\u002Facls\u002F)\n- [Headscale - Open Source Control Server](https:\u002F\u002Fgithub.com\u002Fjuanfont\u002Fheadscale)\n- [WireGuard Protocol](https:\u002F\u002Fwww.wireguard.com\u002Fprotocol\u002F)\n- [Tailscale SSH](https:\u002F\u002Ftailscale.com\u002Fkb\u002F1193\u002Ftailscale-ssh\u002F)\n",{"hide":49,"name":5,"source":50,"license":15,"description":7,"authorized_lab":45,"origin_frontmatter":51},true,"mukul975\u002FAnthropic-Cybersecurity-Skills","name: deploying-tailscale-for-zero-trust-vpn | description: Deploy and configure Tailscale as a WireGuard-based zero trust mesh VPN |   with identity-aware access controls, ACLs, and exit nodes for secure peer-to-peer |   connectivity. | domain: cybersecurity | subdomain: zero-trust-architecture | tags: | - zero-trust | - tailscale | - wireguard | - mesh-vpn | - ztna | - peer-to-peer | - acl | - identity-aware | - headscale | version: '1.0' | author: mahipal | license: Apache-2.0 | nist_csf: | -","main","4c6d8d65f3d6096e2fc25b0845e481dda73c2794",".claude\u002Fskills\u002Fcyber-deploying-tailscale-for-zero-trust-vpn",0,"https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions","Building deterministic AI governance and continuity systems. Workflow architect + visual storyteller","2026-11-11 16:42:59",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-deploying-tailscale-for-zero-trust-vpn",{"tool":66,"command":67},"bunx","bunx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-deploying-tailscale-for-zero-trust-vpn",{"tool":69,"command":70},"pnpm","pnpm dlx skills add nexuslinkproductions\u002Fyuri-os --skill cyber-deploying-tailscale-for-zero-trust-vpn","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcyber-deploying-tailscale-for-zero-trust-vpn\u002FSKILL.md",[],[74,98,120,148,177,196],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":44},"01M71CG1AME5WC0A79AE65WT0X","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","MIT","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97],"zoom out","zoom","with","harness","how","section","re","true","understand","use","perspective","when","you","code","it","context",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":44},"01M71CFY9ATD0BAXV6B14HFG7C","yuri-shura","6-perspective adversarial review for high-stakes turns (architecture decisions, refactor planning, deployment review) — fans out architect, adversary (7-vector attack), maintainer, ops, product, and security perspectives in parallel, then consolidates. Use when user says 'review this decision', '\u002Fshura', 'adversarial review', 'what could go wrong', 'architecture review', or 'deployment review'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-shura\u002FSKILL.md",[],[105,106,85,107,108,29,109,110,111,112,113,91,114,93,115,116,38,117,118,119],"yuri shura","parallel","architecture review","planning","deployment","vector","strategic review","decision","strategic","ops","workflow","decisions","review","perspectives","adversarial",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":129,"publishedAt":44},"01M71CFTTYW1HA2MNX38EV1GJ5","yuri-sales-intelligence","Unified sales and outreach skill generating cold outreach openers, social selling sequences, objection rebuttals, and ad creative for any paid platform — multi-persona aware, adapting tone and offer frame to buyer type. Use when user says 'write a cold email', 'outreach sequence', 'objection handling', 'ad copy', or 'sales pitch'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-sales-intelligence\u002FSKILL.md",[126],{"categoryNo":127,"categoryName":128,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通",[130,131,132,133,134,135,136,137,138,93,139,140,141,142,143,144,145,29,146,147],"intelligence","sales intelligence","yuri sales intelligence","sales","cold","paid","social","persona","pitch","cold email","ad creative","write","sequences","sequence","platform","email","cold outreach","frame",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":162,"publishedAt":44},"01M71CFQMBFTFADJNGP0Z2WCYK","yuri-code-intelligence","Unified code quality intelligence layer that diagnoses code smells (Long Method, Feature Envy, design pattern issues), prescribes targeted Fowler refactoring techniques, and reviews code for security, performance, and clarity. Use when user says 'review this code', 'refactor this', 'what's wrong with this method', 'code smells', or 'clean this up'.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-code-intelligence\u002FSKILL.md",[154,157],{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[163,95,164,130,85,165,166,167,29,168,169,170,171,172,173,174,175,176,91,93],"yuri code intelligence","code intelligence","reviews","code quality","feature","performance","code review","long","up","issues","clean","techniques","improve","design",{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":183,"publishedAt":44},"01M71CFP32RT6GD3GKNHCJP8VP","yuri-adw","Invoke when user asks to run the ADW loop \u002F agentic engineering loop \u002F software factory workflow.","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fyuri-adw\u002FSKILL.md",[],[184,185,186,187,188,189,190,191,192,93,193,115,194,195],"yuri adw","run","engineering loop","software factory","software","agentic engineering","factory","loop","invoke","engineering","agentic","user",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":214,"publishedAt":44},"01M71CFK4VPEKY6A73237P7RSN","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002Fnexuslinkproductions\u002Fyuri-os\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[202,205,208,211],{"categoryNo":203,"categoryName":204,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":206,"categoryName":207,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":209,"categoryName":210,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":212,"categoryName":213,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000036","内容创作者",[215,216,217,93,115,218,85,219,109,91,220],"writing","writing skills","new","work","editing","Existing"]