[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWFRW2KTVKB0ZG0AS0Q8SD":3,"skill-same:01M7EWFRW2KTVKB0ZG0AS0Q8SD":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},"01M7EWFRW2KTVKB0ZG0AS0Q8SD","zero-trust-architect",null,"Design zero-trust architecture — identity-centric access, micro-segmentation, continuous verification, and phased migration.","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-zero-trust-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: zero-trust-architect\ndescription: Design zero-trust architecture — identity-centric access, micro-segmentation, continuous verification, and phased migration.\ncategory: security\n---\n\n## Overview\n\nZero trust is a strategy, not a product: **never trust, always verify**. Every access decision — user, device, workload — is authenticated, authorized, and encrypted based on identity and context, regardless of network location. It replaces the castle-and-moat model where \"inside the network\" meant trusted.\n\nThis skill covers the architecture: the pillars (identity, devices, networks, applications, data), policy design, and the phased migration path from legacy perimeter thinking. No vendor pitches — principles and practice.\n\nZero trust is a strategy for an uncomfortable truth: the network perimeter is gone, and 'inside' no longer means safe. The architecture replaces implicit trust with explicit, continuously evaluated decisions — which is powerful but operationally demanding. Organizations that succeed treat it as a multi-year program with visible milestones, not a product deployment with a go-live date.\n\n## When to use\n\n- Reducing blast radius so one compromised credential does not mean network-wide access.\n- Securing hybrid work: users and apps everywhere, no meaningful perimeter.\n- Planning phased migration away from VPN-centric remote access.\n- Meeting regulatory or customer expectations for modern access architecture.\n\n## Core concepts\n\n- **The core tenets (NIST SP 800-207):** all data sources and services are resources; all communication is secured; access is granted per-session; policy is dynamic (identity + device posture + behavior); the enterprise monitors integrity and security posture of all assets.\n- **Identity as the perimeter:** strong identity (phishing-resistant MFA), device posture, and risk signals drive each access decision — not source IP.\n- **Least privilege per request:** access is granted to specific resources for the session, continuously re-evaluated — not broad network segments for 8 hours.\n- **Micro-segmentation:** workloads isolated so lateral movement requires explicit authorization at each hop; assume breach between every segment.\n- **Policy engine + policy enforcement:** a central policy decision point evaluates trust signals; enforcement points (proxies, agents, gateways) carry it out. Design these before buying anything.\n- **It is a journey:** nobody \"buys zero trust.\" Maturity progresses pillar by pillar; the roadmap matters more than the starting point.\n\n- **Continuous diagnostics and mitigation (CDM).** Posture signals (patch level, EDR health, encryption status) must flow into access decisions in near real time — stale signals mean stale trust.\n- **Data-centric controls.** Classification, labeling, and DLP follow the data beyond any perimeter; zero trust without data governance protects the pipes but not the water.\n- **Legacy integration patterns.** Mainframes, OT, and ancient apps will not do OIDC — plan compensating controls (gateways, jump hosts with session recording) rather than permanent exemptions.\n\n## Practical workflow\n\n1. **Define protect surfaces:** inventory crown jewels — the data, apps, and services that matter most. Zero trust starts by protecting what matters, not by boiling the ocean.\n2. **Map transaction flows:** for each protect surface, document who\u002Fwhat accesses it, from where, on which devices, and what the current implicit trust assumptions are.\n3. **Architect the pillars:** identity (phishing-resistant MFA, lifecycle), devices (posture\u002Fcompliance checks), network (micro-segmentation, encrypted transport), applications (per-app access control), data (classification, DLP).\n4. **Build policy:** write access policies as code where possible — who (verified identity + group), what (specific resource), under which conditions (device compliant, risk low, business hours for sensitive). Start in monitor\u002Faudit mode.\n5. **Migrate in phases:** pilot on one protect surface (e.g., contractor access to one app via ZTNA); measure UX and security outcomes; expand surface by surface. Keep legacy paths only with explicit risk acceptance and sunset dates.\n6. **Monitor and adapt:** continuous diagnostics — policy decisions logged, anomalies investigated, posture signals fed back into risk scoring. Zero trust without monitoring is just complicated trust.\n\n### Phase plan template\n\n- **Phase 0:** inventory protect surfaces, map flows, baseline identity\u002Fdevice posture\n- **Phase 1:** identity hardening (phishing-resistant MFA, lifecycle) + pilot ZTNA on one surface\n- **Phase 2:** micro-segmentation around crown jewels; per-app policies in enforce mode\n- **Phase 3:** expand surfaces; retire legacy VPN paths; continuous verification everywhere\n- **Ongoing:** policy-as-code reviews, posture-signal tuning, maturity reassessment\n\n### Sustaining the practice\n\n- Reassess maturity annually against a model (e.g., CISA ZTMM) and publish the delta\n- Review policy-as-code changes with the same rigor as application code\n- Measure user friction continuously — degraded UX drives shadow IT\n- Sunset legacy access paths on committed dates, not 'when convenient'\n\n### Metrics that prove it works\n\n- Protect-surface coverage % under zero-trust policy\n- % of access flows via ZTNA\u002Fidentity-aware paths vs legacy network paths\n- Policy-decision audit completeness (can you reconstruct who accessed what?)\n- Phishing-resistant authentication % across the estate\n\n## Common pitfalls\n\n- **Buying \"zero trust in a box.\"** It is an architecture of identity, segmentation, and policy — no single product delivers it.\n- **Ignoring identity fundamentals.** Zero trust on top of weak passwords and no MFA is theater. Identity hygiene is phase one.\n- **Big-bang migration.** Ripping out network access wholesale breaks the business. Phase by protect surface.\n- **Forgetting devices and data.** Identity-only zero trust misses compromised endpoints and unclassified data. All pillars matter.\n- **Policies nobody can understand.** Over-complex policy-as-code becomes unmaintainable. Keep policies readable, reviewed, and tested.\n- **No UX measurement.** If the new model makes work painful, users route around it (shadow IT). Measure and optimize the experience, not just the security.\n- **Zero-trust slideware.** Architecture diagrams without defined protect surfaces and mapped transaction flows are marketing. Start with the crown jewels inventory.\n- **Forgetting non-human identities.** Service accounts and workloads need the same verify-every-request treatment, or they become the bypass.\n- **Declaring victory after SSO + MFA.** Identity hardening is phase one of five pillars, not the destination. Devices, networks, apps, and data need equal attention.\n- **Policy exceptions without owners.** Every legacy bypass needs a named owner, compensating controls, and a sunset date — or it becomes the permanent architecture.\n","## Overview\n\nZero trust is a strategy, not a product: **never trust, always verify**. Every access decision — user, device, workload — is authenticated, authorized, and encrypted based on identity and context, regardless of network location. It replaces the castle-and-moat model where \"inside the network\" meant trusted.\n\nThis skill covers the architecture: the pillars (identity, devices, networks, applications, data), policy design, and the phased migration path from legacy perimeter thinking. No vendor pitches — principles and practice.\n\nZero trust is a strategy for an uncomfortable truth: the network perimeter is gone, and 'inside' no longer means safe. The architecture replaces implicit trust with explicit, continuously evaluated decisions — which is powerful but operationally demanding. Organizations that succeed treat it as a multi-year program with visible milestones, not a product deployment with a go-live date.\n\n## When to use\n\n- Reducing blast radius so one compromised credential does not mean network-wide access.\n- Securing hybrid work: users and apps everywhere, no meaningful perimeter.\n- Planning phased migration away from VPN-centric remote access.\n- Meeting regulatory or customer expectations for modern access architecture.\n\n## Core concepts\n\n- **The core tenets (NIST SP 800-207):** all data sources and services are resources; all communication is secured; access is granted per-session; policy is dynamic (identity + device posture + behavior); the enterprise monitors integrity and security posture of all assets.\n- **Identity as the perimeter:** strong identity (phishing-resistant MFA), device posture, and risk signals drive each access decision — not source IP.\n- **Least privilege per request:** access is granted to specific resources for the session, continuously re-evaluated — not broad network segments for 8 hours.\n- **Micro-segmentation:** workloads isolated so lateral movement requires explicit authorization at each hop; assume breach between every segment.\n- **Policy engine + policy enforcement:** a central policy decision point evaluates trust signals; enforcement points (proxies, agents, gateways) carry it out. Design these before buying anything.\n- **It is a journey:** nobody \"buys zero trust.\" Maturity progresses pillar by pillar; the roadmap matters more than the starting point.\n\n- **Continuous diagnostics and mitigation (CDM).** Posture signals (patch level, EDR health, encryption status) must flow into access decisions in near real time — stale signals mean stale trust.\n- **Data-centric controls.** Classification, labeling, and DLP follow the data beyond any perimeter; zero trust without data governance protects the pipes but not the water.\n- **Legacy integration patterns.** Mainframes, OT, and ancient apps will not do OIDC — plan compensating controls (gateways, jump hosts with session recording) rather than permanent exemptions.\n\n## Practical workflow\n\n1. **Define protect surfaces:** inventory crown jewels — the data, apps, and services that matter most. Zero trust starts by protecting what matters, not by boiling the ocean.\n2. **Map transaction flows:** for each protect surface, document who\u002Fwhat accesses it, from where, on which devices, and what the current implicit trust assumptions are.\n3. **Architect the pillars:** identity (phishing-resistant MFA, lifecycle), devices (posture\u002Fcompliance checks), network (micro-segmentation, encrypted transport), applications (per-app access control), data (classification, DLP).\n4. **Build policy:** write access policies as code where possible — who (verified identity + group), what (specific resource), under which conditions (device compliant, risk low, business hours for sensitive). Start in monitor\u002Faudit mode.\n5. **Migrate in phases:** pilot on one protect surface (e.g., contractor access to one app via ZTNA); measure UX and security outcomes; expand surface by surface. Keep legacy paths only with explicit risk acceptance and sunset dates.\n6. **Monitor and adapt:** continuous diagnostics — policy decisions logged, anomalies investigated, posture signals fed back into risk scoring. Zero trust without monitoring is just complicated trust.\n\n### Phase plan template\n\n- **Phase 0:** inventory protect surfaces, map flows, baseline identity\u002Fdevice posture\n- **Phase 1:** identity hardening (phishing-resistant MFA, lifecycle) + pilot ZTNA on one surface\n- **Phase 2:** micro-segmentation around crown jewels; per-app policies in enforce mode\n- **Phase 3:** expand surfaces; retire legacy VPN paths; continuous verification everywhere\n- **Ongoing:** policy-as-code reviews, posture-signal tuning, maturity reassessment\n\n### Sustaining the practice\n\n- Reassess maturity annually against a model (e.g., CISA ZTMM) and publish the delta\n- Review policy-as-code changes with the same rigor as application code\n- Measure user friction continuously — degraded UX drives shadow IT\n- Sunset legacy access paths on committed dates, not 'when convenient'\n\n### Metrics that prove it works\n\n- Protect-surface coverage % under zero-trust policy\n- % of access flows via ZTNA\u002Fidentity-aware paths vs legacy network paths\n- Policy-decision audit completeness (can you reconstruct who accessed what?)\n- Phishing-resistant authentication % across the estate\n\n## Common pitfalls\n\n- **Buying \"zero trust in a box.\"** It is an architecture of identity, segmentation, and policy — no single product delivers it.\n- **Ignoring identity fundamentals.** Zero trust on top of weak passwords and no MFA is theater. Identity hygiene is phase one.\n- **Big-bang migration.** Ripping out network access wholesale breaks the business. Phase by protect surface.\n- **Forgetting devices and data.** Identity-only zero trust misses compromised endpoints and unclassified data. All pillars matter.\n- **Policies nobody can understand.** Over-complex policy-as-code becomes unmaintainable. Keep policies readable, reviewed, and tested.\n- **No UX measurement.** If the new model makes work painful, users route around it (shadow IT). Measure and optimize the experience, not just the security.\n- **Zero-trust slideware.** Architecture diagrams without defined protect surfaces and mapped transaction flows are marketing. Start with the crown jewels inventory.\n- **Forgetting non-human identities.** Service accounts and workloads need the same verify-every-request treatment, or they become the bypass.\n- **Declaring victory after SSO + MFA.** Identity hardening is phase one of five pillars, not the destination. Devices, networks, apps, and data need equal attention.\n- **Policy exceptions without owners.** Every legacy bypass needs a named owner, compensating controls, and a sunset date — or it becomes the permanent architecture.\n",{"name":5,"category":24,"description":7},"security","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-zero-trust-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 zero-trust-architect",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill zero-trust-architect",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill zero-trust-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-zero-trust-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",[],[]]