Menu

Individual skill

vpn-architect

Design secure remote-access VPN architecture — protocol choice, authentication, segmentation, and migration to zero-trust access.

skills/vpn-architect/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
53
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

VPNs extend the trusted network to remote users and sites — which is exactly why their security posture matters so much: a VPN concentrator is one of the most attacked assets in any estate, and a compromised VPN credential historically meant broad network access. Modern practice hardens traditional VPNs while migrating toward zero-trust network access (ZTNA) where it fits.

This skill covers defensive VPN architecture: protocol and product selection, strong authentication, segmentation, logging, and the pragmatic path toward ZTNA.

VPN architecture sits at an awkward transition: still essential for many use cases, increasingly supplemented by zero-trust access. The pragmatic stance is to harden what you have while deliberately migrating what you can — running a neglected VPN 'until we do zero trust someday' is how appliances become the initial-access vector in someone else's incident report.

## When to use

- Designing or replacing remote-access VPN for a hybrid/remote workforce.
- Hardening an existing VPN (patches, MFA, config review) after incidents or audit findings.
- Segmenting VPN users so a compromised endpoint does not mean the whole network.
- Evaluating ZTNA as a VPN complement or replacement.