SkillVaultskills Browse all 500 skills

Security · Version 1.2.0 · Reviewed 2026-08-02

Zero Trust Architecture Advisor

Find and prioritize exploitable risk in identity-based access and segmentation strategy with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Designs identity-based access controls that replace network location as the trust boundary.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Identity-based access
  • Segmentation strategy
  • Migration sequencing

How Zero Trust Architecture Advisor works

You provide

Code, configuration, and the deployment trust model

It inspects

Reachable input-to-sink paths for identity-based access

It decides

A segmentation strategy finding ranked by blast radius

You verify

Re-attempt the exploit path after remediation

What it checks first

Zero Trust Architecture Advisor designs identity-based access controls that replace network location as the trust boundary. Use it when the work involves Identity-based access, Segmentation strategy, Migration sequencing.

  1. Trust boundaries and every point where untrusted input crosses one.
  2. Where authorization is enforced relative to where data is accessed.
  3. Secret handling: creation, storage, transmission, rotation, and revocation.
  4. What an attacker gains at each step, which determines whether a finding is material.

Failure modes it recognizes

  • Authorization enforced at the perimeter while internal callers reach the same data unchecked.
  • A single unparameterized query path among many parameterized ones.
  • Sensitive values written to logs or error responses.
  • A dependency vulnerability that is reachable in one code path and unreachable in the rest.

Answers it will reject

  • Reporting theoretical findings as exploitable without a demonstrated path.
  • Blocking a payload signature instead of removing the vulnerability class.
  • Treating obscurity as a control, which delays discovery without preventing exploitation.

Decision rules it applies

  • Prioritize by reachability and blast radius, not by scanner severity.
  • Fail closed on any ambiguity in an access decision.
  • Prefer eliminating the capability over sanitizing input into it.

Evidence it asks for

  • Trace input to sink and name every file and function on the path.
  • Verify the fix by attempting the original exploit path.
  • Check logs for prior exploitation before closing a finding.

The method inside

  1. Map the artifact, actors, boundaries, and invariants relevant to identity-based access.
  2. Trace concrete failure or abuse paths for segmentation strategy; do not report checklist items without a mechanism.
  3. Prioritize migration sequencing findings by impact, likelihood, confidence, and cost of correction.
  4. Recommend the smallest defensible change, then define how an independent reviewer can verify it.

Deliverables

  • Identity-based access assessment
  • Segmentation strategy decision and action plan
  • Migration sequencing verification checklist

Evidence requirements

  • Code, configuration, data flows, and trust boundaries
  • Identity, authorization, and deployment context
  • Threat model, controls, and known assumptions

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

We want to move from VPN-based access to zero trust for internal tools. Where do we start without breaking work?

Expected output

Start with identity and device posture on one low-risk application rather than the network layer, because a network-first rollout blocks everyone the day it lands. Prove the access path end to end, then migrate applications by risk, retiring VPN routes only after traffic reaches zero...

Boundaries and compatibility

Ideal for

  • Identity-based access: produce a decision or artifact grounded in supplied evidence.
  • Segmentation strategy: produce a decision or artifact grounded in supplied evidence.
  • Migration sequencing: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Authorizing offensive actions against systems without permission
  • Reporting theoretical issues as exploitable without a path

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.