kb-security-audit

Audit application attack surfaces and prioritize fixes using OWASP Top 10:2025 and EPSS.

Updated May 19, 2026
One-click install
npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-security-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-security-audit
Source: https://github.com/TimeKast/AgendaInteligente/tree/main/.claude/skills/kb-security-audit
Command: npx skills add https://github.com/TimeKast/AgendaInteligente --skill kb-security-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you perform offensive, adversarial security audits that identify real attack paths, correctly assess risk, and prioritize fixes based on exploit likelihood rather than severity alone.

Core Features & Use Cases

  • Threat modeling & attack-surface mapping: Clarifies what to protect, where trust boundaries sit, and how an attacker could chain exploits across entry points and data flows.
  • OWASP Top 10:2025 coverage (incl. A03 supply chain, A10 exceptional conditions): Guides focused reviews of broken access control, misconfiguration, injection, supply chain integrity, and dangerous error-handling/fail-open behavior.
  • EPSS/CVSS-based prioritization & reporting structure: Produces actionable findings with clear What/Where/Why/Impact/How-to-fix, including guidance for scanning phases and MITRE ATT&CK-informed red-team tactics.

Quick Start

Use the kb-security-audit knowledge base to audit a feature’s threat model, map its attack surface, and generate prioritized, adversary-aligned findings using OWASP Top 10:2025 and EPSS-informed ordering.

Frequently Asked Questions about kb-security-audit

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

FAQPage Schema
How do I prioritize vulnerability fixes based on actual attacker behavior instead of CVSS severity alone?

Use EPSS-driven prioritization and MITRE ATT&CK red-team tactics to rank vulnerabilities by exploit likelihood. This approach maps dangerous code patterns and attack paths to real adversary behavior, ensuring you fix the highest-risk exposures first.

How do I map an application's attack surface and identify trust boundaries for threat modeling?

Threat modeling maps your application's entry points, data flows, and trust boundaries to clarify what to protect. It identifies how an attacker could chain exploits across the attack surface, guiding targeted security audits of dangerous code patterns.

What's the best way to audit supply chain security and fail-open error handling using OWASP Top 10:2025?

OWASP Top 10:2025 audits guide focused reviews of supply chain integrity (A03) and exceptional conditions (A10), including dangerous fail-open error handling. This reveals dangerous code patterns and misconfigurations across any stack-agnostic environment.

Can I use this security audit methodology for secret detection and CVE patch planning across any tech stack?

Yes, this stack-agnostic security audit methodology applies to secret exposure review and CVE patch planning. It provides scanning phases and finding structures with What/Where/Why/Impact/How-to-fix guidance to address vulnerabilities across any technology stack.

Does this vulnerability auditing approach require specific dependencies or scanning tools to generate findings?

No dependencies are required to apply this vulnerability auditing methodology. It provides an offensive, adversarial reference framework for scanning phases and reporting structure, generating actionable findings independently of specific scanning tools.

Why should I use an adversarial security audit approach over standard vulnerability scanning for my application?

An adversarial security audit identifies real attack paths and prioritizes fixes based on exploit likelihood rather than severity alone. Unlike standard scanning, it applies offensive threat modeling and MITRE ATT&CK tactics to match attacker behavior and expose hidden risk.