What it does
The agent reviews PowerShell automation for security anti-patterns such as embedded credentials, insecure logging and unsafe remoting. For credentials, the publisher's description points to SecretManagement or Key Vault as alternatives, and to error masking within scripts. It also covers least-privilege design.
It is intended for cases such as configuring PowerShell remoting for operators who need limited access. The publisher describes implementing Just Enough Administration (JEA) endpoints with role-based command constraints and enabling transcript logging. It is also described for audit preparation, checking execution policies, logging and code signing against DISA STIG.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 218
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, an
As shown on www.aitmpl.com when we last read it