security-hardening-audit

Identify and document security gaps through a structured multi-pass audit.

10|2|Updated Mar 12, 2026

Search Tags:#security #audit #threat-modeling #code-review #testing-framework #edge-case #regression-tests

Ready to run

npx skills add https://github.com/viktorbezdek/skillstack --skill security-hardening-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-hardening-audit
Source: https://github.com/viktorbezdek/skillstack/tree/main/skillstack-workflows/skills/security-hardening-audit
Command: npx skills add https://github.com/viktorbezdek/skillstack --skill security-hardening-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and document security gaps in a codebase through a structured multi-pass audit.

Core Features & Use Cases

Threat modeling to map attack surfaces and data flows.
Phase-based security review covering risk-management, code-review, edge-case analysis, and testing-framework integration.
Generated artifacts including threat model, findings with remediation, regression tests, and a remediation report for audits.

Quick Start

Run the security-hardening-audit workflow to map the threat surface, perform security-focused reviews, analyze edge cases, and generate a hardened test suite.

Frequently Asked Questions about security-hardening-audit

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

FAQPage Schema

How do I perform a structured security audit on my codebase?▼

A structured security audit identifies codebase vulnerabilities through multi-pass analysis. It applies threat modeling, security-focused code review, edge-case validation, and test hardening to produce actionable remediation and compliance evidence.

What is threat modeling and when do I need it for code review?▼

Threat modeling maps attack surfaces and data flows within a software project. It is needed during security-focused code review to identify edge cases and document gaps before generating regression tests and remediation reports.

How do I generate regression tests for identified security gaps?▼

Regression tests for security gaps are generated during the test hardening phase. This process follows threat modeling and code review to enforce actionable fixes, providing traceable findings and material artifacts for compliance audits.

Can I use this audit workflow for typical software projects to prepare compliance evidence?▼

Yes, this audit workflow applies phased analysis across typical software projects to produce compliance evidence. It generates material artifacts including a threat model, findings with remediation, and a final remediation report.

Why does security hardening require a multi-pass audit instead of a standard code review?▼

Security hardening requires a multi-pass audit because standard code review often misses edge cases. A multi-pass approach integrates threat modeling, targeted code review, and test hardening to map attack surfaces and enforce traceable fixes.

What are the limitations of automated threat modeling in a security audit?▼

Automated threat modeling in a security audit focuses on mapping attack surfaces and data flows but requires subsequent manual edge-case validation. It produces a baseline threat model that must be verified through test hardening and targeted code review.