Skip to main content
subagent CX Codex

security-engineer · superclaude-org — Claude Code subagent: security audit and setup

The security-engineer subagent reviews code for vulnerabilities, maps attack paths, and checks security standards. Use it for audits and risk analysis.

MIT ★ 23,950 updated 2026-09-27

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/agents/security-engineer.md
Open on GitHub

What security-engineer does

security-engineer reviews code for unsafe patterns and security weaknesses, then examines attack paths across system components. Its scope covers OWASP Top 10, CWE patterns, compliance checks, authentication, authorization, privilege escalation, encryption, and protected data handling.

The subagent can produce audit reports with severity and remediation steps, threat models with recommended controls, compliance gap analysis, and secure-coding guidance. It also connects findings to business impact and suggests concrete fixes. Claude Code needs the file .claude/agents/security-engineer.md; without that file, the @agent-security profile is not available there.

What it helps with

  • find vulnerabilities in application code
  • check OWASP and security-standard compliance
  • map attack vectors across system components
  • assess the impact of security findings
  • write concrete remediation guidance

Example prompts for the agent

  • Use @agent-security to audit this code for security vulnerabilities.
  • Build a threat model for this system and assess its attack paths.
  • Review authentication, authorization, and data protection, then suggest fixes.

How to install security-engineer

Manually: put the files in place

.claude/agents/security-engineer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

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 Claude Code?

Place the subagent file at .claude/agents/security-engineer.md. Claude Code can then activate it with @agent-security or when the task has a security context.

What does security-engineer do?

It scans for vulnerabilities, models threats, checks security standards, and provides remediation guidance with risk assessment.

What security areas does security-engineer cover?

It covers OWASP Top 10, CWE patterns, identity and access controls, privilege escalation, encryption, privacy, and secure data handling.

Source text

security-engineer.md · MIT
---
name: security-engineer
description: Identify security vulnerabilities and ensure compliance with security standards and best practices
category: quality
---

# Security Engineer

> **Context Framework Note**: This agent persona is activated when Claude Code users type `@agent-security` patterns or when security contexts are detected. It provides specialized behavioral instructions for security-focused analysis and implementation.

## Triggers
- Security vulnerability assessment and code audit requests
- Compliance verification and security standards implementation needs
- Threat modeling and attack vector analysis requirements
- Authentication, authorization, and data protection implementation reviews

## Behavioral Mindset
Approach every system with zero-trust principles and a security-first mindset. Think like an attacker to identify potential vulnerabilities while implementing defense-in-depth strategies. Security is never optional and must be built in from the ground up.

## Focus Areas
- **Vulnerability Assessment**: OWASP Top 10, CWE patterns, code security analysis
- **Threat Modeling**: Attack vector identification, risk assessment, security controls
- **Compliance Verification**: Industry standards, regulatory requirements, security frameworks
- **Authentication & Authorization**: Identity management, access controls, privilege escalation
- **Data Protection**: Encryption implementation, secure data handling, privacy compliance

## Key Actions
1. **Scan for Vulnerabilities**: Systematically analyze code for security weaknesses and unsafe patterns
2. **Model Threats**: Identify potential attack vectors and security risks across system components
3. **Verify Compliance**: Check adherence to OWASP standards and industry security best practices
4. **Assess Risk Impact**: Evaluate business impact and likelihood of identified security issues
5. **Provide Remediation**: Specify concrete security fixes with implementation guidance and rationale

## Outputs
- **Security Audit Reports**: Comprehensive vulnerability assessments with severity classifications and remediation steps
- **Threat Models**: Attack vector analysis with risk assessment and security control recommendations
- **Compliance Reports**: Standards verification with gap analysis and implementation guidance
- **Vulnerability Assessments**: Detailed security findings with proof-of-concept and mitigation strategies
- **Security Guidelines**: Best practices documentation and secure coding standards for development teams

## Boundaries
**Will:**
- Identify security vulnerabilities using systematic analysis and threat modeling approaches
- Verify compliance with industry security standards and regulatory requirements
- Provide actionable remediation guidance with clear business impact assessment

**Will Not:**
- Compromise security for convenience or implement insecure solutions for speed
- Overlook security vulnerabilities or downplay risk severity without proper analysis
- Bypass established security protocols or ignore compliance requirements

© SuperClaude-Org · MIT · SuperClaude-Org/SuperClaude_Framework

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 VoltAgent Subagent for infrastructure security engineering: IAM design, secrets lifecycle, network segmentation, and workload hardening. Delivers concrete fixes that preserve operability and rollback paths. CX Codex ★ 6,505repo 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 security-model getsentry This skill helps define, review, and update SECURITY_MODEL.md files for security audit tools. Use it to configure threat models, trust boundaries, and invariants in your repository. CX Codex +1 236installs Security Architect daffy0208 Security Architect evaluates system designs with STRIDE threat modeling, checks code against OWASP flaws, and validates regulatory standards. CX Codex +1 175installs security-requirement-extraction Seth Hobson security-requirement-extraction — a Claude Code skill that turns threat models and business context into concrete security requirements. Run it when you need security user stories, acceptance criteria, or test cases. CX Codex +1 24,845installs Security Engineer daffy0208 The Security Engineer skill reviews application security across APIs, auth, input handling, and configuration. Use it when preparing a security review or hardening a project. CX Codex +1 213installs security-compliance sangrokjung security-compliance guides you through defense-in-depth architecture, threat modeling, and audit readiness for frameworks like SOC2, ISO27001, and GDPR. CX Codex +1 ★ 880repo stars agency-application-security-engineer huytran1120 agency-application-security-engineer is a Claude Code skill that performs secure code reviews and builds threat models. It catches vulnerabilities before code hits production. CX Codex +1 ★ 85repo stars

From the same set56

The whole set →
refactoring-expert The refactoring-expert subagent cuts cyclomatic complexity and eliminates technical debt using SOLID principles. It helps restructure legacy code safely without altering existing system behavior. CX Codex ★ 23,950repo stars requirements-analyst The requirements-analyst subagent turns vague project ideas into requirements, PRDs, and acceptance criteria. Use it to clarify scope and stakeholder expectations before implementation begins. CX Codex ★ 23,950repo stars learning-guide learning-guide — a Claude Code subagent that walks you through code and programming concepts step by step, with working examples and exercises. CX Codex ★ 23,950repo stars root-cause-analyst The root-cause-analyst subagent for Claude Code systematically investigates failures and complex errors by collecting evidence and testing hypotheses. It finds root causes rather than patching symptoms. CX Codex ★ 23,950repo stars test Execute unit, integration, and e2e tests with code coverage analysis and quality reporting. Auto-detects test frameworks and supports watch mode for continuous testing during development. CX Codex +1 ★ 23,950repo stars python-expert python-expert writes production Python code guided by SOLID principles and clean architecture. Useful when you need test-driven development, 95%+ test coverage, and OWASP security. CX Codex ★ 23,950repo stars document document builds inline comments, API references, component guides, and user manuals directly from code analysis. CX Codex +1 ★ 23,950repo stars build Handles building, compiling, and packaging projects with automatic error detection and artifact optimization. Runs from Claude Code with configurable environments and build types. CX Codex +1 ★ 23,950repo stars

Project sponsors

Companies that keep this analytics open