Red Implementing Privileged Access Workstation

---
name: red-implementing-privileged-access-workstation
description: Design and implement Privileged Access Workstations (PAWs) with device hardening, just-in-time access, and integration with CyberArk or BeyondTrust for secure administrative operations.
domain: red
category: active-directory
hide: true
license: Apache-2.0
metadata:
  manifest_entry: src/corpus/red-implementing-privileged-access-workstation/SKILL.md
---
# Implementing Privileged Access Workstation

## Overview

A Privileged Access Workstation (PAW) is a hardened device dedicated to performing sensitive administrative tasks. This skill covers PAW design using the tiered administration model, device compliance enforcement via Microsoft Intune or Group Policy, just-in-time (JIT) access provisioning, and integration with privileged access management (PAM) platforms like CyberArk and BeyondTrust.


## When to Use

- When deploying or configuring implementing privileged access workstation capabilities in your environment
- When establishing security controls aligned to compliance requirements
- When building or improving security architecture for this domain
- When conducting security assessments that require this implementation

## Common Misconfigurations & Verification

A PAW that can reach the internet or run arbitrary code is no longer a PAW — these gaps quietly void the control:

- **Internet/email/browsing left enabled:** the #1 failure. A PAW must be denied general web and email so it cannot be phished or download payloads. Verify with a proxy/firewall test from the PAW — arbitrary outbound HTTPS and mail must be blocked, allowing only approved management endpoints (Intune, PAM, specific admin URLs).
- **Tier mixing:** admins use the PAW to manage Tier-0 *and* browse Tier-2 / read email, collapsing the tier boundary. Confirm the clean-source / tiered model: Tier-0 credentials are never entered on a non-PAW device and vice versa. Audit sign-in logs for Tier-0 accounts authenticating from non-PAW devices.
- **Credential Guard / VBS not actually on:** hardening is documented but not enforced. Verify on-device: `Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard` shows `SecurityServicesRunning` includes Credential Guard, and confirm AppLocker is in *enforce* (not audit) mode.
- **JIT elevation degenerates into standing admin:** verify time-bound group membership actually expires (re-check the privileged group after the window) rather than leaving the account permanently in Domain Admins.
- **Device compliance not gating access:** confirm Conditional Access requires a compliant/PAW device for admin portals, so a non-compliant machine cannot use vaulted creds.
- **PAM checkout bypass:** confirm admins check credentials out through CyberArk/BeyondTrust (with recording) rather than using locally cached or memorized privileged passwords.

## Prerequisites

- Windows 10/11 Enterprise with Virtualization Based Security (VBS)
- Microsoft Intune or Active Directory Group Policy
- CyberArk Privileged Access Security or BeyondTrust Password Safe (optional)
- Python 3.9+ with `requests`, `subprocess`, `json`
- Administrative access to target endpoints

## Steps

1. Audit current privileged access patterns and identify Tier 0/1/2 assets
2. Configure device hardening baselines (AppLocker, Credential Guard, Device Guard)
3. Enforce compliance policies via Intune or GPO
4. Implement just-in-time access with time-limited admin group membership
5. Integrate with CyberArk/BeyondTrust for credential vaulting
6. Validate PAW configuration against CIS and Microsoft PAW guidance
7. Monitor privileged sessions and generate compliance reports

## Expected Output

- JSON report listing device compliance status, hardening checks, JIT access windows, and PAM integration verification
- Risk scoring per workstation with remediation recommendations