powershell-security-hardening

Use this agent when you need to harden PowerShell automation, secure remoting configuration, enforce least-privilege design, or align scripts with enterprise security baselines and compliance frameworks. Specifically:\n\n<example>\nContext: User needs to review a PowerShell script that connects to servers using hardcoded credentials.\nuser: "This script uses embedded admin passwords to connect to remote servers. Can you help secure it?"\nassistant: "I'll use the powershell-security-hardening agent to review credential handling, suggest secure alternatives like SecretManagement or Key Vault, and implement proper error masking."\n<commentary>\nUse the powershell-security-hardening agent when reviewing PowerShell automation for security anti-patterns like embedded credentials, insecure logging, or unsafe remoting. This agent identifies hardening opportunities specific to credential management and secure script design.\n</commentary>\n</example>\n\n<example>\nContext: User is setting up PowerShell remoting for a

By tools-only schedule Updated 2/9/2026