security-hardening

Review web app authentication, authorization, and OWASP Top 10 risks.

Updated May 6, 2026
One-click install
npx skills add https://github.com/korwlik23/skills --skill security-hardening-korwlik23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-hardening
Source: https://github.com/korwlik23/skills/tree/main/v1/security-hardening
Command: npx skills add https://github.com/korwlik23/skills --skill security-hardening-korwlik23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you identify security weaknesses and prevent production incidents by systematically reviewing authentication, authorization, input handling, secrets management, headers, and common OWASP Top 10 risks.

Core Features & Use Cases

  • Threat-aware security review: Evaluates authorization (IDOR, horizontal/vertical escalation), authentication (brute force, session fixation), and business-logic abuse with an evidence-first mindset.
  • Production hardening guidance: Provides concrete configuration baselines for security headers, cookies, CORS/CSRF, rate limiting, and secure file upload controls.
  • Framework coverage: Tailored checklists for Laravel, Next.js/Node.js, and Svelte/SvelteKit, plus a structured penetration-testing-style checklist (without running exploits).
  • L5 acceptance gates & safe output: Forces findings to be tied to exploitability/impact and validated by remediation verification steps, avoiding claims without evidence.

Quick Start

Use the security-hardening skill to review the codebase and configs for authentication, authorization, injection, file uploads, headers, and secrets handling, then output an evidence-based security review with prioritized fixes and verification steps.

Frequently Asked Questions about security-hardening

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform an evidence-based security review for my web application?

An evidence-based security review systematically evaluates authentication, authorization, OWASP Top 10 risks, and secure configuration, tying findings to exploitability and validating them with remediation verification steps and tests.

What's the best way to harden Laravel, Next.js, and SvelteKit endpoints against OWASP Top 10 risks?

Harden endpoints by applying framework-tailored checklists for Laravel, Next.js/Node.js, and Svelte/SvelteKit that assess IDOR, session fixation, injection, and business-logic abuse using a penetration-testing-style review.

How do I configure secure cookies, CORS, and CSRF protection for production web apps?

Configure secure cookies, CORS, and CSRF protection by applying concrete production hardening baselines that enforce strict security headers, rate limiting, and least-privilege authorization across endpoints and APIs.

Does this security review approach work for assessing secure file uploads and API sessions?

Yes, this security review approach works for secure file uploads and API sessions by evaluating upload controls and session management alongside authentication and authorization risks without executing real exploits.

Why should I avoid unverified vulnerability claims during an application security assessment?

Avoid unverified vulnerability claims because an effective security assessment requires an evidence-first mindset, ensuring findings map to actual exploitability and impact while enforcing strict non-disclosure of secrets or PII.

What is needed to validate security fixes and prevent production incidents?

To validate security fixes and prevent production incidents, you need acceptance gates that require findings to be tied to impact, prioritized remediation steps, and verifiable tests confirming the vulnerabilities are resolved.