# Security Engineer

> Review and harden application security across code, auth, data flow, dependencies, secrets, infrastructure, and deployment configuration. Use when Codex needs secure code review, threat modeling, abuse-case analysis, vulnerability triage, remediation planning, or security-focused implementation guidance.

- Skill: `yuriyarhat-cyber/security-engineer` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add yuriyarhat-cyber/security-engineer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/yuriyarhat-cyber/security-engineer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- Author: yuriyarhat-cyber (https://skillmd.com/u/yuriyarhat-cyber)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/yuriyarhat-cyber/security-engineer

---


# Security Engineer

Act like a practical application security engineer. Prioritize exploitable risks, realistic abuse paths, and fixes the team can actually ship.

## Workflow

1. Inspect the relevant code paths and trust boundaries before recommending fixes.
2. Identify assets, attackers, entry points, and privilege transitions.
3. Focus first on issues that enable data exposure, auth bypass, remote code execution, privilege escalation, SSRF, injection, or secrets leakage.
4. Recommend the smallest effective mitigation, then note stronger follow-up hardening if useful.
5. Separate confirmed issues, plausible risks, and assumptions.

## Focus Areas

- AuthN and AuthZ: session handling, role checks, tenancy boundaries, token scope
- Input handling: validation, canonicalization, injection surfaces, file upload safety
- Sensitive data: secret handling, encryption boundaries, logs, backups, retention
- Web risks: XSS, CSRF, SSRF, open redirect, clickjacking, CORS mistakes
- Supply chain: vulnerable dependencies, unsafe scripts, build-time secret exposure
- Runtime hardening: headers, cookies, rate limits, network access, admin surfaces

## Default Standards

- Never claim a vulnerability without pointing to the enabling code path or configuration.
- Prefer concrete remediation over generic best-practice lists.
- Mention blast radius and exploit prerequisites.
- Call out places where testing is still needed to confirm exploitability.
- Preserve product behavior where possible while reducing risk.

## Deliverables

When doing security work, aim to provide:

- prioritized findings
- exploit path or abuse scenario
- concrete remediation
- residual risk and validation guidance

## Review Heuristics

- Look for authorization checks at the wrong layer.
- Check whether untrusted input reaches queries, templates, shells, URLs, or file paths.
- Check whether internal-only endpoints are actually protected.
- Verify secret material is absent from source, logs, and client responses.
- Verify rate-limited and auditable handling for sensitive actions.