security-auditor

Reviews NestJS and Next.js codebases for OWASP risks, tenant isolation, and PII exposure.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/SleyiW/iWana-neXt --skill security-auditor-sleyiw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-auditor
Source: https://github.com/SleyiW/iWana-neXt/tree/main/.agents/skills/security-auditor
Command: npx skills add https://github.com/SleyiW/iWana-neXt --skill security-auditor-sleyiw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews of a multi-tenant NestJS/Next.js application often miss stack-specific risks like cross-tenant data leaks, PII in logs, or weak authorization boundaries. This Skill provides a structured audit framework tailored to the iWana neXt stack so findings are prioritized, actionable, and grounded in the real architecture. ## Core Features & Use Cases - Stack-Focused Audit Scope: Reviews authentication, authorization, tenancy isolation, OpenAPI contracts, logging, persistence, and async jobs against OWASP guidance and internal governance rules. - Zero-Trust PII and Tenancy Checks: Verifies absence of PII and secrets in code, tests, and logs, and validates schema-level tenant isolation and bounded-context boundaries. - Prioritized Findings and Escalation: Classifies findings by severity, business impact, and merge-blocking status, with a defined escalation path to the CTO for critical vulnerabilities. - Use Case: Before merging a pull request that adds a new public endpoint, run this audit to confirm input validation, tenant resolution, authorization checks, and audit trail coverage, then receive a severity-ranked findings report with corrective actions. ## Quick Start Ask the AI to audit the current pull request for security risks covering tenancy isolation, PII exposure, and OWASP controls, and return prioritized findings with merge conditions.

Frequently Asked Questions about security-auditor

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

FAQPage Schema
How do I run a security audit on a NestJS application?

A NestJS security audit reviews authentication, role- or policy-based authorization, input validation at external boundaries, parameterized queries via TypeORM, and error handling that avoids leaking internals. This Skill structures that review into prioritized findings with corrective actions.

How to check for cross-tenant data leaks in a multi-tenant app?

Verify schema-level tenant isolation, confirm the tenant is resolved correctly per request, and check for direct table access across modules or bounded contexts. The audit treats tenancy boundaries as security controls and flags any potential cross-tenant leakage as a critical finding.

What OWASP controls apply to a Next.js and NestJS stack?

Key controls include validating all external inputs, safe output handling to prevent XSS in the frontend, parameterized database queries, rate limiting and CORS on public endpoints, and error responses that do not expose sensitive internals.

Can this audit declare legal compliance for personal data handling?

No. When findings touch personal data, billing, or regulated traceability, the audit documents the risk but does not assert closed legal compliance. Uncertain regulatory points are marked as requiring verification with an official source.

When should a security finding block a merge?

Findings block a merge when they involve critical vulnerabilities, potential cross-tenant data leakage, or attempts to weaken established security controls. These cases also trigger escalation to the CTO per the defined escalation rules.