CtrlK
BlogDocsLog inGet started
Tessl Logo

common-dast-tooling

Standardize usage of Dynamic Application Security Testing (DAST) tools (ZAP, Nuclei, Nikto) and custom AI-driven curl probes for adversarial system testing. Use when advising on or running dynamic security scans on local/staging environments. (triggers: DAST, dynamic scan, zap, nuclei, nikto, curl probe, pentest, dynamic analysis)

78

Quality

72%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Risky

Do not use without reviewing

Optimize this skill with Tessl

npx tessl skill review --optimize ./.github/skills/common/common-dast-tooling/SKILL.md
SKILL.md
Quality
Evals
Security

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 just public ones.

1. Automated DAST Tools

Follow implementation guide for command-line setup.

  • Nuclei: Best for fast, template-based CVE/Misconfiguration scanning.
  • ZAP-CLI: Best for deep spidering and web vulnerability scanning (SQLi, XSS, etc.).
  • Nikto: Quick scan for insecure server configurations and outdated software.

2. Adversarial curl Probing (Manual)

When tools are unavailable, use the AI to generate targeted curl probes:

  • Bypassing Guards: Probe protected routes with manipulated headers (X-Forwarded-For, X-Custom-Auth).
  • Data Leakage: Request /metrics, /health, or .git directories to find exposed metadata.
  • Parameter Tampering: Modify payload types (String -> Object) or inject large payloads to test limits.

Scoring Impact

FindingSeverityDeduction
Unauthenticated access to private dataP0-25
Successful SQLi/RCE via probeP0-20
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, and internal gRPC/RMQ listeners.

References

  • DAST Tooling Implementation
  • OWASP Dynamic Scanning Guide
Repository
HoangNguyen0403/agent-skills-standard
Commit

19a1140

Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill