Skip to main content
subagent CX Codex

security-engineer · voltagent/awesome-codex-subagents — Codex subagent for infrastructure security

Subagent for infrastructure security engineering: IAM design, secrets lifecycle, network segmentation, and workload hardening. Delivers concrete fixes that preserve operability and rollback paths.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/security-engineer.toml
Open on GitHub

What security-engineer does

security-engineer owns infrastructure and platform security work as a production-safety task: analyzes identity and access boundaries, designs secret lifecycle and rotation, segments networks, hardens workloads, and ensures logging and detection coverage. It works methodically — maps the affected operational path (control plane, data plane, dependency edges), separates confirmed facts from assumptions, then proposes the smallest safe action that restores security without widening blast radius.

Each recommendation is validated: does it address a real threat, does it break critical workflows, can it be rolled back. Returns the exact boundary analyzed (service, environment, pipeline), the concrete issue with evidence, the tightest solution and why it is preferred, what validation passed and what requires live environment testing, plus residual risk and next actions.

Focuses on least-privilege enforcement, secret rotation and storage paths, network exposure minimization, host and container hardening, detection and auditability for high-risk operations, artifact integrity in build-deploy. Does not claim comprehensive coverage or mandate re-architecture unless asked.

What it helps with

  • enforce identity and access with least-privilege boundaries
  • design secret creation, rotation, storage and usage paths
  • segment networks to minimize exposure of critical assets
  • harden hosts, containers and runtime policies
  • add logging and detection for high-risk operations

Example prompts for the agent

  • Review our VPC IAM policies and show how to tighten access to least privilege with minimal risk
  • Design a credentials rotation cycle for the database that can be rolled back cleanly
  • Check build and deploy artifacts for integrity: how do we cryptographically verify them before deployment

How to install security-engineer

Manually: put the files in place

.codex/agents/security-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about security-engineer

How do I install security-engineer in Codex?

Create or edit .codex/agents/security-engineer.toml in your project root with the subagent configuration. Codex will load it at startup.

What does security-engineer do?

It handles infrastructure security engineering tasks: analyzes identity boundaries, secret management, network segmentation, and workload hardening. Delivers concrete changes that do not break operations and preserve rollback options.

How does security-engineer choose a solution?

It maps the affected operational paths, separates facts from assumptions, proposes the smallest safe change. Validates normal-path behavior and one rollback path; live environment testing is required for final assurance.

Source text

security-engineer.toml · MIT
# security-engineer

Use when a task needs infrastructure and platform security engineering across IAM, secrets, network controls, or hardening work.

Own infrastructure and platform security engineering work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- identity and access boundaries with least-privilege enforcement
- secret lifecycle management: creation, rotation, storage, and usage paths
- network segmentation and exposure minimization for critical assets
- workload hardening controls across hosts, containers, and runtime policies
- logging, detection, and auditability coverage for high-risk operations
- supply-chain and artifact integrity concerns in build/deploy systems
- risk prioritization by exploitability, impact, and remediation cost

Quality checks:
- verify each recommendation maps to a concrete threat scenario and control objective
- confirm mitigations preserve operability and do not break critical workflows
- check privilege reduction opportunities and residual high-risk permissions
- ensure detection and response visibility is included, not only prevention controls
- call out environment-specific validation required for final security assurance

Return:
- exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
- concrete issue/risk and supporting evidence or assumptions
- smallest safe recommendation/change and why this option is preferred
- validation performed and what still requires live environment verification
- residual risk, rollback notes, and prioritized follow-up actions

Do not claim comprehensive security coverage or mandate broad re-architecture unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Security →

security-engineer by other authors comes first.

security-engineer VoltAgent Community security-engineer automates DevSecOps workflows, CIS benchmark checks, and vulnerability scanning. Useful when securing cloud infrastructure or embedding security controls into CI/CD. CX Codex 3,243installs security-engineer SuperClaude-Org The security-engineer subagent reviews code for vulnerabilities, maps attack paths, and checks security standards. Use it for audits and risk analysis. CX Codex ★ 23,950repo stars security-engineer josstei security-engineer — a subagent for checking code against OWASP Top 10 vulnerabilities, auditing authentication, and scanning dependencies. Builds threat models and delivers prioritized remediation reports. CX Codex ★ 489repo stars infrastructure transilienceai The infrastructure skill tests network services, protocols, and perimeter security. Use it for authorized assessments that need structured checks and captured evidence. CX Codex +1 211installs macos-security-privacy-hardening reason-machines macos-security-privacy-hardening — a skill for securing and hardening macOS systems following enterprise security standards. Sets up full-disk encryption, firewall, firmware passwords, and disables telemetry. CX Codex +1 111installs macos-security-hardening reason-machines The macos-security-hardening skill guides you through setting up full-disk encryption, configuring firewalls, securing DNS, and disabling telemetry on macOS. Use it to protect your system against local access, data theft, and tracking. CX Codex +1 107installs devops-engineer VoltAgent Community The devops-engineer subagent reviews infrastructure and helps with CI/CD, containers, and deployment workflows. Use it when you want to automate software delivery or add security checks to the process. CX Codex 7,392installs network-engineer VoltAgent Community The network-engineer subagent for Claude Code designs and debugs cloud and hybrid networks. It handles VPC routing, zero-trust policies, and latency issues. CX Codex 1,871installs google-cloud-waf-security official google google-cloud-waf-security is a Claude Code skill that assesses Google Cloud workload security and suggests changes. It activates for questions about firewall rules, access controls, auditing, or AI security. CX Codex +1 14,620installs

From the same set176

The whole set →
windows-infra-admin The windows-infra-admin subagent handles Windows infrastructure work across Active Directory, DNS, DHCP, GPO, and PowerShell automation. Use it when a change needs safety checks. CX Codex ★ 6,505repo stars terragrunt-expert terragrunt-expert — a subagent for Terragrunt work: organizes modules across environments, validates dependency chains between stacks, ensures remote state and locking are safe for concurrent runs, and detects hidden configuration drift. CX Codex ★ 6,505repo stars terraform-engineer terraform-engineer reviews Terraform plans, audits state changes, and designs modules with small blast radiuses and clear rollbacks. CX Codex ★ 6,505repo stars sre-engineer The sre-engineer subagent handles SLOs, alerting, resilience, and operational risk. Use it when a change needs clear safety checks and rollback paths. CX Codex ★ 6,505repo stars platform-engineer platform-engineer designs internal developer platforms, self-service infrastructure boundaries, and golden paths focused on production reliability. CX Codex ★ 6,505repo stars network-engineer The network-engineer subagent traces network paths, investigates service connectivity, and reviews load balancers and infrastructure changes. It also checks failure and rollback paths. CX Codex ★ 6,505repo stars kubernetes-specialist kubernetes-specialist — a subagent for reviewing Kubernetes manifests, analyzing rollout safety and cluster workload debugging. Identifies risks before deployment and plans recovery or rollback paths. CX Codex ★ 6,505repo stars incident-responder incident-responder handles production incident triage, containment planning, and root-cause analysis. It focuses on minimal safe interventions and clear rollback paths. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open