[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWBCR41RYPF919THSV9P9Q":3,"skill-same:01M7EWBCR41RYPF919THSV9P9Q":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EWBCR41RYPF919THSV9P9Q","vpn-architect",null,"Design secure remote-access VPN architecture — protocol choice, authentication, segmentation, and migration to zero-trust access.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-vpn-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vpn-architect\ndescription: Design secure remote-access VPN architecture — protocol choice, authentication, segmentation, and migration to zero-trust access.\ncategory: security\n---\n\n## Overview\n\nVPNs 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.\n\nThis skill covers defensive VPN architecture: protocol and product selection, strong authentication, segmentation, logging, and the pragmatic path toward ZTNA.\n\nVPN 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.\n\n## When to use\n\n- Designing or replacing remote-access VPN for a hybrid\u002Fremote workforce.\n- Hardening an existing VPN (patches, MFA, config review) after incidents or audit findings.\n- Segmenting VPN users so a compromised endpoint does not mean the whole network.\n- Evaluating ZTNA as a VPN complement or replacement.\n\n## Core concepts\n\n- **The VPN is a high-value target:** internet-facing, authentication-bearing, and historically vulnerability-prone. Patch aggressively, monitor auth logs, and treat it as crown-jewel infrastructure.\n- **Protocols:** WireGuard and IKEv2\u002FIPsec are the modern defaults (strong crypto, good performance); OpenVPN remains solid; avoid PPTP\u002FL2TP-with-PSK and SSL-VPN products with poor patch histories unless risk-accepted.\n- **Authentication:** MFA mandatory, ideally phishing-resistant; machine certificates plus user auth for managed devices; no split-tunnel exceptions without justification.\n- **Least-privilege network access:** VPN users should reach only what their role needs — per-group ACLs, segmented zones — not \"the whole corporate LAN.\" Full-tunnel by default for managed devices.\n- **Logging:** authentication attempts, session start\u002Fstop, bytes transferred, and endpoint posture — shipped to the SIEM with alerts on anomalies (impossible travel, off-hours admin access).\n- **ZTNA direction:** identity- and device-aware per-application access instead of network-level tunnels. Evaluate for new deployments; migrate high-risk use cases first.\n\n- **Always-on VPN for managed devices.** Removes the user decision entirely — the device is either connected and protected or it is not on the network. Pair with device compliance checks.\n- **Endpoint posture before access.** Require disk encryption, OS patch level, and EDR presence as VPN admission criteria — a compromised endpoint should not get a tunnel.\n- **Split tunneling governance.** Every split-tunnel exception needs a documented business reason and periodic review; default-deny the bypass, not the tunnel.\n\n## Practical workflow\n\n1. **Define access requirements:** who connects (employees, contractors, admins), from what devices, to which resources. This drives segmentation and auth design.\n2. **Select and harden the platform:** current, supported software; hardened config (strong ciphers, no legacy protocols); management interface not internet-exposed; tested backup\u002Ffailover.\n3. **Enforce strong auth:** MFA for all users; certificates for managed devices; lockout and rate-limiting on auth; disable or tightly control any legacy auth methods.\n4. **Segment:** role-based access groups mapped to firewall zones; admins get a separate, more restricted path; contractors get time-boxed, resource-scoped access.\n5. **Monitor:** SIEM alerts for brute force, impossible travel, concurrent sessions, and new-device enrollments; quarterly access reviews of VPN entitlements.\n6. **Plan the ZTNA path:** pilot ZTNA for a high-risk app or contractor population; measure user experience and security outcomes; expand where it wins, keep VPN where tunnels are genuinely needed (site-to-site, legacy).\n\n### VPN hardening checklist\n\n- [ ] Patched to current; management interface not internet-facing\n- [ ] MFA enforced for all users; weak auth methods disabled\n- [ ] Strong protocols\u002Fciphers only; legacy protocols removed\n- [ ] Role-based segmentation; no flat \"VPN = LAN\" access\n- [ ] Full-tunnel default for managed devices; split-tunnel justified and reviewed\n- [ ] Auth and session logging to SIEM with anomaly alerts\n- [ ] Quarterly entitlement reviews; contractor access time-boxed\n\n### Sustaining the practice\n\n- Review VPN access entitlements quarterly alongside all privileged access\n- Track appliance vulnerabilities as P1 patch items with dedicated SLAs\n- Measure ZTNA pilot outcomes to build the migration business case\n- Audit split-tunnel exceptions annually — they accumulate silently\n\n### Metrics that prove it works\n\n- Patch latency on VPN appliances (days from vendor release)\n- MFA enforcement coverage % of VPN users\n- Authentication-anomaly alerts triaged within SLA\n- % of remote access migrated to ZTNA (where targeted)\n\n## Common pitfalls\n\n- **Unpatched VPN appliances.** VPN vulnerabilities are routinely exploited within days of disclosure. Patch like your network depends on it — it does.\n- **Flat access.** VPN into the whole LAN turns one phished credential into a network-wide incident. Segment by role.\n- **MFA gaps.** \"MFA except for these legacy clients\" is the hole attackers find. Close it or document and mitigate the risk explicitly.\n- **Split-tunnel sprawl.** Convenience split tunneling exposes the endpoint to the open internet while connected. Default to full tunnel; exception with justification.\n- **No session monitoring.** Authentication without anomaly detection misses credential-reuse and session-hijack patterns.\n- **Treating VPN as the forever answer.** For app-level remote access, ZTNA usually offers better least-privilege and UX. Reassess periodically.\n- **Site-to-site VPNs forgotten in reviews.** Everyone hardens remote-access VPN; the decade-old site-to-site tunnels with static PSKs get ignored. Inventory them too.\n- **Vendor-default credentials on appliances.** Still found in real estates. Change them during deployment and verify in audits.\n- **Contractor VPN accounts that never expire.** Time-box every non-employee account at creation; expiry should be automatic, renewal deliberate.\n- **No bandwidth or session anomaly monitoring.** Data exfiltration over VPN looks like normal traffic without baselines. Monitor session patterns, not just logins.\n","## Overview\n\nVPNs 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.\n\nThis skill covers defensive VPN architecture: protocol and product selection, strong authentication, segmentation, logging, and the pragmatic path toward ZTNA.\n\nVPN 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.\n\n## When to use\n\n- Designing or replacing remote-access VPN for a hybrid\u002Fremote workforce.\n- Hardening an existing VPN (patches, MFA, config review) after incidents or audit findings.\n- Segmenting VPN users so a compromised endpoint does not mean the whole network.\n- Evaluating ZTNA as a VPN complement or replacement.\n\n## Core concepts\n\n- **The VPN is a high-value target:** internet-facing, authentication-bearing, and historically vulnerability-prone. Patch aggressively, monitor auth logs, and treat it as crown-jewel infrastructure.\n- **Protocols:** WireGuard and IKEv2\u002FIPsec are the modern defaults (strong crypto, good performance); OpenVPN remains solid; avoid PPTP\u002FL2TP-with-PSK and SSL-VPN products with poor patch histories unless risk-accepted.\n- **Authentication:** MFA mandatory, ideally phishing-resistant; machine certificates plus user auth for managed devices; no split-tunnel exceptions without justification.\n- **Least-privilege network access:** VPN users should reach only what their role needs — per-group ACLs, segmented zones — not \"the whole corporate LAN.\" Full-tunnel by default for managed devices.\n- **Logging:** authentication attempts, session start\u002Fstop, bytes transferred, and endpoint posture — shipped to the SIEM with alerts on anomalies (impossible travel, off-hours admin access).\n- **ZTNA direction:** identity- and device-aware per-application access instead of network-level tunnels. Evaluate for new deployments; migrate high-risk use cases first.\n\n- **Always-on VPN for managed devices.** Removes the user decision entirely — the device is either connected and protected or it is not on the network. Pair with device compliance checks.\n- **Endpoint posture before access.** Require disk encryption, OS patch level, and EDR presence as VPN admission criteria — a compromised endpoint should not get a tunnel.\n- **Split tunneling governance.** Every split-tunnel exception needs a documented business reason and periodic review; default-deny the bypass, not the tunnel.\n\n## Practical workflow\n\n1. **Define access requirements:** who connects (employees, contractors, admins), from what devices, to which resources. This drives segmentation and auth design.\n2. **Select and harden the platform:** current, supported software; hardened config (strong ciphers, no legacy protocols); management interface not internet-exposed; tested backup\u002Ffailover.\n3. **Enforce strong auth:** MFA for all users; certificates for managed devices; lockout and rate-limiting on auth; disable or tightly control any legacy auth methods.\n4. **Segment:** role-based access groups mapped to firewall zones; admins get a separate, more restricted path; contractors get time-boxed, resource-scoped access.\n5. **Monitor:** SIEM alerts for brute force, impossible travel, concurrent sessions, and new-device enrollments; quarterly access reviews of VPN entitlements.\n6. **Plan the ZTNA path:** pilot ZTNA for a high-risk app or contractor population; measure user experience and security outcomes; expand where it wins, keep VPN where tunnels are genuinely needed (site-to-site, legacy).\n\n### VPN hardening checklist\n\n- [ ] Patched to current; management interface not internet-facing\n- [ ] MFA enforced for all users; weak auth methods disabled\n- [ ] Strong protocols\u002Fciphers only; legacy protocols removed\n- [ ] Role-based segmentation; no flat \"VPN = LAN\" access\n- [ ] Full-tunnel default for managed devices; split-tunnel justified and reviewed\n- [ ] Auth and session logging to SIEM with anomaly alerts\n- [ ] Quarterly entitlement reviews; contractor access time-boxed\n\n### Sustaining the practice\n\n- Review VPN access entitlements quarterly alongside all privileged access\n- Track appliance vulnerabilities as P1 patch items with dedicated SLAs\n- Measure ZTNA pilot outcomes to build the migration business case\n- Audit split-tunnel exceptions annually — they accumulate silently\n\n### Metrics that prove it works\n\n- Patch latency on VPN appliances (days from vendor release)\n- MFA enforcement coverage % of VPN users\n- Authentication-anomaly alerts triaged within SLA\n- % of remote access migrated to ZTNA (where targeted)\n\n## Common pitfalls\n\n- **Unpatched VPN appliances.** VPN vulnerabilities are routinely exploited within days of disclosure. Patch like your network depends on it — it does.\n- **Flat access.** VPN into the whole LAN turns one phished credential into a network-wide incident. Segment by role.\n- **MFA gaps.** \"MFA except for these legacy clients\" is the hole attackers find. Close it or document and mitigate the risk explicitly.\n- **Split-tunnel sprawl.** Convenience split tunneling exposes the endpoint to the open internet while connected. Default to full tunnel; exception with justification.\n- **No session monitoring.** Authentication without anomaly detection misses credential-reuse and session-hijack patterns.\n- **Treating VPN as the forever answer.** For app-level remote access, ZTNA usually offers better least-privilege and UX. Reassess periodically.\n- **Site-to-site VPNs forgotten in reviews.** Everyone hardens remote-access VPN; the decade-old site-to-site tunnels with static PSKs get ignored. Inventory them too.\n- **Vendor-default credentials on appliances.** Still found in real estates. Change them during deployment and verify in audits.\n- **Contractor VPN accounts that never expire.** Time-box every non-employee account at creation; expiry should be automatic, renewal deliberate.\n- **No bandwidth or session anomaly monitoring.** Data exfiltration over VPN looks like normal traffic without baselines. Monitor session patterns, not just logins.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-vpn-architect",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill vpn-architect",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill vpn-architect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill vpn-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-vpn-architect\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]