Security Hardening
Use when you have a security finding (from code audit or pentest) and need to fix it correctly with secure-coding patterns, then verify the fix actually closes it. Covers fixes for injection, access control, XSS, auth, secrets, and config across the stack.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill security-hardeninggit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/security-hardening ~/.claude/skills/security-hardeningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Hardening (FIX phase) ## Overview Turn findings into correct, verified fixes. Fix the **root cause** at the right layer, add **defense in depth**, then **re-test** to prove the hole is closed. **Core principle:** A fix you didn't re-test is a hope, not a fix. Reproduce the original exploit and confirm it now fails. ## Process per finding 1. **Root cause** — why is untrusted data reaching the sink? Fix *there*, not by blocklisting symptoms. 2. **Apply the secure pattern** — see table below. 3. **Defense in depth** — add a second independent control (validation + parameterization, etc.). 4. **Re-test** — rerun the exact PoC from `active-pentest`/the audit; confirm it fails now. 5. **Regression** — add a test so it can't silently come back. ## Secure-pattern quick reference | Vulnerability | Root-cause fix | Defense in depth | |---------------|----------------|------------------| | SQL/NoSQL injection | Parameterized queries / ORM bindings; allowlist dynamic identifiers | Least-privilege DB user; input validation | | Command injection | Avoid shell; use exec arrays / safe APIs; no shell interpolation | Allowlist args; drop privileges | | XSS | Context-aware output encoding; framework auto-escape; `textContent` | CSP; sanitize HTML (DOMPurify); `HttpOnly` cookies | | Broken access control / IDOR | Enforce authz server-side on every action; scope queries to the user | Deny-by-default; centralized policy checks |
Details
- Skill name
security-hardening- Repository
- mn-youssef/security-skills
- Path
skills/security-hardening/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Security Hardening skill do?
Use when you have a security finding (from code audit or pentest) and need to fix it correctly with secure-coding patterns, then verify the fix actually closes it. Covers fixes for injection, access control, XSS, auth, secrets, and config across the stack.
How do I install the Security Hardening skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Hardening popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-youssef/security-skills
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
Security Testing
49mn-youssef/security-skills
Use when you want to security-test, pentest, audit, or find vulnerabilities in an application you own or are authorized to test — entry point that confirms authorization and routes to the right phase (threat model, code audit, active test, or hardening).
Security Code Audit
49mn-youssef/security-skills
Use when you have application source code and want to find security vulnerabilities by reading it — covers OWASP Top 10 across frontend, backend API, and database. Produces a findings register with severity, file:line, and exploitability.
Securitycards
21Reware-Labs/securitycards
Apply version-specific secure coding guidance to AI-generated or human-written code that uses supported open source libraries. Use when starting a software project, implementing a security-sensitive feature, or reviewing code for secure defaults, authentication, authorization, input handling, injection, cryptography, file handling, network boundaries, secrets, sessions, and other library-specific security concerns.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.