Agente · em Proteger
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
Procedência
- Origem: davila7/claude-code-templates
- Caminho:
cli-tool/components/agents/security/powershell-security-hardening.md - Versão fixada:
57f899e5394bb8ca166f38eacae8f0853cbfe033 - Licença: MIT
- Espelhado em 25/09/2026
- 8 downloads no Claude Code Templates (lido em 25/09/2026)
Antes de instalar
1 arquivo · 4,6 KB · só texto, nenhum script
Instalar na sua CLI
O comando baixa a versão fixada (commit 57f899e) direto da origem, para a pasta que a CLI lê. Precisa de curl (macOS e Linux); no Windows não há comando, porque o Rook Labs é para macOS.
Claude Code
Neste projeto: instala em .claude/agents/powershell-security-hardening.md.
curl -fsSL --create-dirs \ -o ".claude/agents/powershell-security-hardening.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/security/powershell-security-hardening.md" \ -o ".claude/agents/powershell-security-hardening.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Global: instala em ~/.claude/agents/powershell-security-hardening.md.
curl -fsSL --create-dirs \ -o "$HOME/.claude/agents/powershell-security-hardening.md" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/cli-tool/components/agents/security/powershell-security-hardening.md" \ -o "$HOME/.claude/agents/powershell-security-hardening.LICENSE" "https://raw.githubusercontent.com/davila7/claude-code-templates/57f899e5394bb8ca166f38eacae8f0853cbfe033/LICENSE"
Codex
Neste projeto: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Global: O Codex define agentes como papéis em TOML, num formato diferente deste .md; ele não instala como está.
Antigravity
Neste projeto: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Global: O Antigravity lê agentes num formato próprio, e como este agente se comporta nele não foi provado; não damos comando.
Prévia do powershell-security-hardening.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. Specifically:\\n\\n<example>\\nContext: User needs to review a PowerShell script that connects to serv…
tools: Read, Write, Edit, Bash, Glob, Grep
---
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
…