---
title: "PowerShell automation hardening reviewer: review, role & definition · Undominated.ai"
canonical: https://undominated.ai/agents/voltagent-powershell-security-hardening/
description: "A PowerShell security profile for remoting boundaries, credential handling and sanitized operational logs."
---

# PowerShell automation hardening reviewer: review, role & definition · Undominated.ai

> A PowerShell security profile for remoting boundaries, credential handling and sanitized operational logs.

[← Explore all agents](/agents/)

SECURITY OPERATIONS / VoltAgent

# PowerShell automation hardening reviewer

A PowerShell security profile for remoting boundaries, credential handling and sanitized operational logs.

 [Use this definition ↓](#setup)[Original source ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher VoltAgent
 Licence [MIT ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/LICENSE)
 Revision 408d3c9eee2d
 [Read what was—and wasn’t—checked ↓](#review)

“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.”

 [VoltAgent · upstream description ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - It considers scheduled tasks, WinRM endpoints and automation service accounts as part of the script’s security context.
- It checks both error and verbose output for secret disclosure instead of considering only literal passwords in source.

### A good fit for

 - Supply scripts, endpoint configuration, service-account scope and hardening requirements.
- Receive a prioritized hardening review with proposed controls and verification steps.

### Weigh up before choosing

 - Execution Policy is not an authorization boundary; logging can itself capture sensitive values, and this profile grants shell and edit tools. Named compliance baselines are not bundled.
- Unchanged definition, licence and attribution are downloadable; the download does not install the host or the external toolchain.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - categories/04-quality-security/powershell-security-hardening.md (pinned complete source retained)
- LICENSE
- Repository README and current official host configuration documentation

### Our findings

 - It considers scheduled tasks, WinRM endpoints and automation service accounts as part of the script’s security context.
- It checks both error and verbose output for secret disclosure instead of considering only literal passwords in source.

### Not established by this review

 - Source review only: no agent was installed or invoked. Task correctness, effective host restrictions and integration behaviour were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Use the role in your project.

[Upstream setup instructions ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md)
 - Read the pinned source and its licence, then configure an explicitly bounded host context.
- Use the actual policy version and a test endpoint, review log access/retention and restrict execution credentials before applying changes.
- Supply scripts, endpoint configuration, service-account scope and hardening requirements.

### Before you start

 - PowerShell environment and endpoint configuration
- Selected hardening baseline and credential-store integration

### Compatibility

Claude Code

### Implementation

Markdown

### Host-mediated agent profile

 - Declared tools: Read, Write, Edit, Bash, Glob, Grep. Effective host permissions still govern access; shell or execution tools can write files and contact networks.

### Cost model

The definition has the stated open-source licence. Model/host usage and any connected service or execution environment can incur separate costs.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download definition + licence ↗](/resources/agents/voltagent-powershell-security-hardening/bundle.zip)[Raw Markdown ↗](/resources/agents/voltagent-powershell-security-hardening/definition.md)
 ---
name: powershell-security-hardening
description: "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."
tools: Read, Write, Edit, Bash, Glob, Grep
model: inherit
---

You are a PowerShell and Windows security hardening specialist. You build,
review, and improve security baselines that affect PowerShell usage, endpoint
configuration, remoting, credentials, logs, and automation infrastructure.

## Core Capabilities

### PowerShell Security Foundations
- Enforce secure PSRemoting configuration (Just Enough Administration, constrained endpoints)
- Apply transcript logging, module logging, script block logging
- Validate Execution Policy, Code Signing, and secure script publishing
- Harden scheduled tasks, WinRM endpoints, and service accounts
- Implement secure credential patterns (SecretManagement, Key Vault, DPAPI, Credential Locker)

### Windows System Hardening via PowerShell
- Apply CIS / DISA STIG controls using PowerShell
- Audit and remediate local administrator rights
- Enforce firewall and protocol hardening settings
- Detect legacy/unsafe configurations (NTLM fallback, SMBv1, LDAP signing)

### Automation Security
- Review modules/scripts for least privilege design
- Detect anti-patterns (embedded passwords, plain-text creds, insecure logs)
- Validate secure parameter handling and error masking
- Integrate with CI/CD checks for security gates

## Checklists

### PowerShell Hardening Review Checklist
- Execution Policy validated and documented
- No plaintext creds; secure storage mechanism identified
- PowerShell logging enabled and verified
- Remoting restricted using JEA or custom endpoints
- Scripts follow least-privilege model
- Network & protocol hardening applied where relevant

### Code Review Checklist
- No Write-Host exposing secrets
- Try/catch with proper sanitization
- Secure error + verbose output flows
- Avoid unsafe .NET calls or reflection injection points

## Integration with Other Agents
- **ad-security-reviewer** – for AD GPO, domain policy, delegation alignment
- **security-auditor** – for enterprise-level review compliance
- **windows-infra-admin** – for domain-specific enforcement
- **powershell-5.1-expert / powershell-7-expert** – for language-level improvements
- **it-ops-orchestrator** – for routing cross-domain tasks

The download contains powershell-security-hardening.md . Keep its filename when placing it in the agent directory described above.

By **VoltAgent**. [Exact upstream source ↗](https://raw.githubusercontent.com/VoltAgent/awesome-claude-code-subagents/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md) · [Licence](/resources/agents/voltagent-powershell-security-hardening/LICENSE.txt) · [Attribution](/resources/agents/voltagent-powershell-security-hardening/ATTRIBUTION.txt)

SHA-256 b4b43e7389d6ab2b74439267b535308adb7e7b59b906389473a613ed1b46396e

 Read the applicable licence MIT License

Copyright (c) 2025 VoltAgent

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream agent definition ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md) Checked 2026-10-14 https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/categories/04-quality-security/powershell-security-hardening.md Supports: Workflow, inputs, outputs and stated boundaries
- [Applicable licence ↗](https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/LICENSE) Checked 2026-10-14 https://github.com/VoltAgent/awesome-claude-code-subagents/blob/408d3c9eee2d0c75c12a3abb5de29e53c2ca6b9e/LICENSE Supports: Redistribution and attribution
- [Host configuration and tool inheritance ↗](https://code.claude.com/docs/en/sub-agents.md) Checked 2026-10-14 https://code.claude.com/docs/en/sub-agents.md Supports: Host loading and effective permission boundaries
- [Official PowerShell execution-policy limitations ↗](https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies) Checked 2026-10-14 https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_execution_policies Supports: Dependency setup and source-review boundary

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Active Directory security posture reviewer ↗ An AD review profile tracing privilege, delegation, protocol and service-account risks into a remediation plan.](/agents/voltagent-ad-security-reviewer/)[### Credential lifecycle and leak-response planner ↗ A credential-lifecycle profile connecting detection, ownership, provider revocation and controlled rotation.](/agents/agency-security-secrets-credential-engineer/)[### Github Actions Expert ↗ Designs and reviews GitHub Actions workflows around minimal token permissions, immutable action references, OIDC, deployment concurrency and validation.](/agents/github-github-actions-expert/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Find reusable instructions](/skills/)
- [Inspect connections](/mcp-servers/)
- [Build a toolkit](/tools/)
- [Choose the model](/compare/)
