common-dast-tooling
Standardize dynamic application security testing for backend APIs, frontend web apps, and mobile clients. Covers ZAP, Nuclei, Nikto, sqlmap, ffuf, browser automation, mobile proxy interception, and AI-driven curl probes. Use when advising on or running dynamic security scans on local/staging environments.
What this skill does
# DAST Tooling Standard ## **Priority: P1 (OPERATIONAL)** ## Always-Apply Rules - **No Scanning Production**: Never run DAST tools against live production environments. Use local or staging replicas only. - **No Uncapped Scans**: Always set `max-depth` or `max-duration` to avoid infinite loops on dynamic routes. - **No Anonymous Probing**: Use authenticated headers (`Authorization`) to test protected surfaces, not public ones. - **No Mobile on Real Devices in Prod**: Use emulators/simulators for mobile interception testing. ## 1. Backend / API Tools ### Scanner Tools See [implementation guide](references/implementation.md) for setup commands. - **Nuclei**: Fast, template-based CVE/misconfiguration scanning. - **ZAP-CLI**: Deep spidering for SQLi, XSS, CSRF, session issues. - **Nikto**: Server configuration audit (version disclosure, headers). - **sqlmap**: Automated SQL injection detection and exploitation (suggest only — human confirms). - **ffuf / feroxbuster**: Content discovery and endpoint fuzzing. ### API-Specific Probing - **GraphQL**: Introspection query, nested query depth attack, field suggestion enumeration. - **gRPC**: `grpcurl` for service enumeration and method probing. - **WebSocket**: Connection hijacking, message injection testing. ## 2. Frontend / Web Tools - **Browser DevTools**: Network tab for auth token leakage, console for client-side errors. - **Playwright/Puppeteer** (suggested): Automated DOM XSS detection, form submission, CSRF testing. - **Lighthouse**: Security/performance audit (CSP, HTTPS, mixed content). - **CSP Evaluator**: Validate Content-Security-Policy headers. ## 3. Mobile Interception Tools - **mitmproxy / Burp Suite**: Proxy mobile traffic for API inspection. - **Frida**: Runtime instrumentation for cert pin bypass, biometric bypass, jailbreak detection bypass. - **adb / xcrun simctl**: Device-level inspection, deep link testing, storage extraction. - **Objection**: Mobile runtime exploration (iOS/Android). ## 4. AI-Driven `curl` Probing (Manual Fallback) When automated tools unavailable, generate targeted `curl` probes: - **Bypassing Guards**: Probe with manipulated headers (`X-Forwarded-For`, `X-Custom-Auth`). - **Data Leakage**: Request `/metrics`, `/health`, `.git`, `/.env`, `/api-docs`. - **Parameter Tampering**: Modify payload types (String→Object), inject large payloads. - **JWT Manipulation**: Test with expired token, no token, modified claims. See [implementation guide](references/implementation.md) for all commands. ## Scoring Impact | Finding | Severity | Deduction | |---|---|---| | Unauthenticated access to private data | P0 | -25 | | Successful SQLi/RCE via probe | P0 | -20 | | Mobile API interception (no cert pin) | P1 | -15 | | DOM XSS confirmed via browser | P1 | -10 | | Info Leakage (Server versions/Env vars) | P1 | -10 | | Missing security headers (CSP/HSTS) | P2 | -5 | ## Anti-Patterns - **No relying solely on static analysis**: Pentesting MUST include dynamic execution feedback. - **No ignoring non-web protocols**: Check Docker ports, SSH banners, gRPC/RMQ listeners. - **No skipping mobile**: If mobile app exists, proxy its traffic and inspect API calls. ## References - [DAST Tooling Implementation](references/implementation.md) - [OWASP Dynamic Scanning Guide](https://owasp.org/www-community/Vulnerability_Scanning)
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.