Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation).

MITAuto-check passedLegal & Compliance

Install Paw Design

skills CLI
$ npx skills add vinayaklatthe/microsoft-security-skills --skill paw-design -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vinayaklatthe/microsoft-security-skills paw-design --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vinayaklatthe/microsoft-security-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paw-design .claude/skills/paw-design && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
paw-design
GitHub stars
175
Token cost
~1.9k tokens
SKILL.md length
880 words
Files
1
Skills in repo
50
Repo updated
First seen
Licence
MIT

At a glance

Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation).

  • Works in 7 steps: Adopt the enterprise access model — Map… → Apply the clean source principle — Any… → Build the PAW image — Entra-joined (not… → …
  • General endpoint hardening (use defender-for-endpoint)
  • SKILL.md covers When to use, Pick the device profile by…, Approach and Guardrails, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Paw Design is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation). Covers when to use Enterprise vs Specialized vs Privileged device profiles, hardening (Entra-join, Intune, app allowlisting, Credential Guard), Conditional Access enforcement, and rollout. WHEN: privileged access workstation, PAW, secure admin workstation, enterprise access model, privileged access strategy, admin isolation, secured…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Legal & Compliance, covering Regulatory compliance. It works with Microsoft Defender and Microsoft Azure. The repository describes itself as: Curated Microsoft Security skills for AI agents - Defender, Sentinel, Entra, Purview, Intune, Security Copilot. The licence is MIT.

When your agent uses it

  • General endpoint hardening (use defender-for-endpoint)
  • Device compliance policy (use intune-device-mgmt)

Example prompts

  • “/paw-design”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Adopt the enterprise access model — Map every privileged role to control / management
  2. Apply the clean source principle — Any security dependency must be as trustworthy as
  3. Build the PAW image — Entra-joined (not hybrid where possible), Intune-managed,
  4. Lock down user experience — No local admin, no email client, no general browsing
  5. Enforce via Conditional Access — CA policy: Tier 0 roles can sign in only from a
  6. Pair PAW with PIM, phishing-resistant MFA, and dedicated admin accounts — PAWs run
  7. Pilot 5 PAWs first — Tier 0 admins are vocal. Hand-deliver, walk through, gather

What it can do on your machine

Read from SKILL.md and the folder at commit 15f16df. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • learn.microsoft.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Paw Design loads about 1.9k tokens when it runs. Until then it costs about 199 tokens; SKILL.md has 880 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~199
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vinayaklatthe/microsoft-security-skills at commit 15f16df, republished under its MIT licence (© vinayaklatthe). 880 words, ~1,929 tokens.

Download SKILL.mdSave it as .claude/skills/paw-design/SKILL.md (or your agent's skills folder).
name
paw-design
description
Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation). Covers when to use Enterprise vs Specialized vs Privileged device profiles, hardening (Entra-join, Intune, app allowlisting, Credential Guard), Conditional Access enforcement, and rollout. WHEN: privileged access workstation, PAW, secure admin workstation, enterprise access model, privileged access strategy, admin isolation, secured workstation, clean source principle, tier 0 protection, control plane, dedicated admin device, hardened workstation, Credential Guard, FIDO2 admin. DO NOT USE for general endpoint hardening (use defender-for-endpoint) or device compliance policy (use intune-device-mgmt).
license
MIT
metadata.author
Microsoft
metadata.version
0.1.0

Privileged Access Workstation (PAW) Design

A Privileged Access Workstation (PAW) is a hardened, dedicated device used only for privileged tasks - isolating sensitive accounts from browsing, email, and arbitrary apps. PAWs are the device pillar of Microsoft's privileged access strategy and the enforcement point for the clean source principle.

When to use

Protecting administrators of high-value systems (Entra control plane, Azure root, domain controllers, identity infrastructure - "Tier 0") from credential theft, browser exploit, and supply-chain attack. Use this skill to choose the device tier, harden the build, and enforce PAW-only access via CA.

Do not use this skill for general endpoint hardening (defender-for-endpoint) or device compliance baseline (intune-device-mgmt).

Pick the device profile by admin tier

The enterprise access model maps admin roles to three device profiles. Wrong tier = either over-spending or under-protecting.

TierRoles in scopeDevice profileWhat's allowed
Privileged (PAW)Global Admin, Privileged Auth Admin, Tier 0 Azure Owner, Domain Admin, DC operatorsDedicated hardened deviceAdmin portals only; no email, no browsing
SpecializedWorkload admins (Exchange, SharePoint, Intune, SQL DBA), Tier 1 Azure ContributorHardened build; some productivityAdmin portals + curated productivity (Office)
EnterpriseHelp desk, Tier 2 ops, Reports Reader, Security ReaderStandard managed device + strong baselineFull productivity with MDE + ASR + tamper protection

Rule of thumb: the test for "needs a PAW" is can this account log into a domain controller, modify Conditional Access, or assume the root Azure subscription? If yes, PAW. If only managing one workload, Specialized. The PAW population should be small (typically < 1% of admins).

Approach

  1. Adopt the enterprise access model — Map every privileged role to control / management / data plane. Tier 0 = control plane (identity, cloud control plane, on-prem AD). Tier 1 = workload admins. Tier 2 = ops / read-only. Devices, accounts, and access paths must match the tier. Verify: tier mapping document signed off; Tier 0 role count documented.

  2. Apply the clean source principle — Any security dependency must be as trustworthy as the object it secures. Tier 0 administered only from Tier 0 devices. No "I'll just RDP from my laptop this once" - that breaks the model.

  3. Build the PAW image — Entra-joined (not hybrid where possible), Intune-managed, hardware root of trust (TPM 2.0 + UEFI Secure Boot), app allowlisting (WDAC or AppLocker), Credential Guard + Memory Integrity on, BitLocker, Defender for Endpoint with all ASR rules in block mode, no inbound RDP, restrictive outbound firewall. Verify: WDAC policy enforced (not audit); Credential Guard running (msinfo32).

  4. Lock down user experience — No local admin, no email client, no general browsing (block via DNS / firewall to non-admin endpoints), Edge restricted to admin portal URLs only. No USB storage. No app installs by user.

  5. Enforce via Conditional Access — CA policy: Tier 0 roles can sign in only from a compliant device with the PAW device filter (custom attribute). Anything else = block. This is the control that makes the PAW non-optional. Verify: CA policy in enforce mode; What If a Tier 0 sign-in from a non-PAW = blocked.

  6. Pair PAW with PIM, phishing-resistant MFA, and dedicated admin accounts — PAWs run with non-privileged accounts day-to-day; admin credential is FIDO2 + PIM-eligible, activated just-in-time for the task.

  7. Pilot 5 PAWs first — Tier 0 admins are vocal. Hand-deliver, walk through, gather friction reports, iterate. Then scale.

Show full SKILL.md (342 more words)Show less

Guardrails

  • A PAW used for productivity is no longer a PAW. No email, no browsing, no Teams chat. Provide a separate Enterprise device for productivity if needed (yes, two devices).
  • Protect the management chain. Intune and the imaging pipeline are part of the clean source. If Intune is administered from non-PAW devices, the PAW model is broken at the root.
  • No shared local accounts. Each admin has their own credential; no shared "PAW user" account.
  • CA enforcement is the control. Without "Tier 0 sign-in requires PAW", admins will use their laptops "just this once" and the model collapses.
  • Don't skip Credential Guard. Without it, Mimikatz-class credential theft is trivial on a privileged session.
  • Phishing-resistant MFA only. SMS / push MFA for PAW sign-in defeats the point.

Common anti-patterns

  • "We'll use VDI as a PAW" - VDI hosts that allow productivity workloads are not PAWs. The principle is dedicated, not virtual.
  • "PAW deployment in 2 weeks for 200 admins" - You'll get pushback, miss tier mapping, and produce shelf-ware. 5 admins first, iterate, scale over months.
  • "Admins administer Intune from their regular laptop" - Breaks clean source at the root. Intune admin from PAW.
  • "One device for both productivity and admin" - Single browser exploit = credential theft. Two devices for Tier 0.
  • "CA policy in report-only forever" - Not enforced = not real. Move to On after pilot.
  • "PAW user has local admin so they can install tools" - Defeats app allowlisting. Tools are managed via Intune.

Example prompts

  • Map our admin roles to PAW, Specialized, and Enterprise device tiers.
  • Design the PAW image - Entra join, WDAC allowlist, Credential Guard, restricted browsing.
  • Author the Conditional Access policy that requires PAW for Tier 0 role sign-ins.
  • Plan a 5-admin PAW pilot before scaling to all Tier 0 roles.
  • How do I enforce clean source when our imaging server runs on a regular laptop?
  • Should our Exchange admins get PAWs or Specialized devices?

Microsoft Learn

© vinayaklatthe, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/paw-design of vinayaklatthe/microsoft-security-skills.

Open the folder on GitHubat commit 15f16df

Compare with similar skills

Paw Design next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Paw Design compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Paw Design this skillvinayaklatthe/microsoft-security-skills175—~1.9kAutomated safety check: PassMIT
Implementing Azure Defender For Cloudmukul975/Anthropic-Cybersecurity-Skills34k—~3.1kAutomated safety check: PassApache-2.0
Computer InvestigationSCStelz/security-investigator249—~15kAutomated safety check: WarnMIT
Implementing Cloud Security Posture Managementmukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: PassApache-2.0
HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed5.5k—~2kAutomated safety check: PassApache-2.0
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • Implementing Azure Defender For Cloud

    mukul975/Anthropic-Cybersecurity-Skills

    Enable Microsoft Defender for Cloud (CSPM + CWPP) across VMs, containers, SQL, storage, and Key Vault, using Azure Policy for evaluation, Log Analytics for telemetry, Azure Arc for hybrid coverage…

    34k GitHub stars~3.1k tokensUpdated 1 mo ago
    DevOps & CloudAuto-check passed
  • Computer Investigation

    SCStelz/security-investigator

    A skill your agent uses when asked to investigate a computer, device, endpoint, or machine for security issues, suspicious activity, malware, or compliance review.

    249 GitHub stars~15k tokensUpdated 2 days ago
    Legal & ComplianceAuto-check: warnings
  • Implementing Cloud Security Posture Management

    mukul975/Anthropic-Cybersecurity-Skills

    Continuously monitor multi-cloud environments (AWS, Azure, GCP) for misconfigurations, compliance violations, and security risks using Prowler, ScoutSuite, AWS Security Hub, Microsoft Defender for…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed
  • ISO Standards Readiness Evidence

    K-Dense-AI/scientific-agent-skills

    Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.

    48k GitHub starsUsed in 1 repo~4.6k tokens
    Legal & ComplianceAuto-check: notes

More from vinayaklatthe/microsoft-security-skills

All 50 skills in this repo
  • API Security Design

    vinayaklatthe/microsoft-security-skills

    Guidance for designing secure APIs on Azure - authentication, authorization, gateway controls, input validation, rate limiting, secret management, and runtime threat detection - aligned to OWASP API…

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure App Service Security

    vinayaklatthe/microsoft-security-skills

    Guidance for securing Azure App Service web apps and APIs — managed identity, Easy Auth with Microsoft Entra ID, network isolation via private endpoints + VNet integration, HTTPS / TLS hardening…

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Arc

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Arc — projecting on-premises, multicloud (AWS/GCP), and edge servers, Kubernetes, and data services into Azure Resource Manager for unified governance, security, and management.

    175 GitHub stars~1.9k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Bastion Jit

    vinayaklatthe/microsoft-security-skills

    Guidance for secure remote VM management in Azure using Azure Bastion combined with Defender for Cloud just-in-time (JIT) VM access.

    175 GitHub stars~2.2k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Confidential Computing

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure Confidential Computing — protecting data in use through hardware-based Trusted Execution Environments (TEEs).

    175 GitHub stars~2.4k tokensUpdated 3 mo ago
    Auto-check passed
  • Azure Ddos Protection

    vinayaklatthe/microsoft-security-skills

    Guidance for Azure DDoS Protection — Network Protection (per-VNet) and IP Protection (per public IP) tiers built on the same always-on Microsoft platform.

    175 GitHub stars~2k tokensUpdated 3 mo ago
    Auto-check passed

Questions about Paw Design

What does Paw Design do?

Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation). Paw Design is an agent skill from vinayaklatthe/microsoft-security-skills. Guidance for designing Privileged Access Workstations (PAW) and the Microsoft privileged access strategy (enterprise access model, clean source principle, tiered admin isolation).

When should I use Paw Design?

Paw Design fits situations like: general endpoint hardening (use defender-for-endpoint); device compliance policy (use intune-device-mgmt).

How do I install Paw Design in Claude Code?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill paw-design -a claude-code`. Or copy the skill folder (skills/paw-design in vinayaklatthe/microsoft-security-skills) into .claude/skills/paw-design in your project. Claude Code loads it when a task matches its description.

How do I install Paw Design in Codex?

Run `npx skills add vinayaklatthe/microsoft-security-skills --skill paw-design -a codex`. Or copy the skill folder (skills/paw-design in vinayaklatthe/microsoft-security-skills) into .agents/skills/paw-design in your project. Codex loads it when a task matches its description.

Can I use Paw Design in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vinayaklatthe/microsoft-security-skills --skill paw-design -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paw-design, .gemini/skills/paw-design, .github/skills/paw-design and .opencode/skills/paw-design in your project.

What does Paw Design need to run?

SKILL.md names no scripts, command-line tools or credentials: Paw Design is instructions for the agent only.

Does Paw Design access the network?

SKILL.md names 1 domain. As links in the text: learn.microsoft.com. This is read from the text; nothing was executed.

Is Paw Design safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Paw Design use?

Paw Design is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Paw Design use?

About 1.9k tokens (SKILL.md is roughly 7.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Paw Design?

Skills that share tags, products or a category with Paw Design: Implementing Azure Defender For Cloud (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Computer Investigation (SCStelz/security-investigator, 249 stars), Implementing Cloud Security Posture Management (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Paw Design?

vinayaklatthe (a GitHub user) maintains it in vinayaklatthe/microsoft-security-skills, which has 175 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on June 18, 2026.

Source: vinayaklatthe/microsoft-security-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.