Skip to content
Back to skills

Sast Dast Interpretation

ASecurity

Interprets SAST and DAST results with a triage matrix, common false positives, and OWASP ZAP priority findings; use when reviewing security scan results, triaging vulnerabilities, or deciding which findings to fix or accept.

  • 19 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 19, 2026
ai-agentssqlsecurity

Works with

  • cli

Security analysis

A100/100

Scanned October 19, 2026

npx -y skills add sawrus/agent-guides --skill sast-dast-interpretation --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sast Dast Interpretation?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sast Dast Interpretation
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sawrus-sast-dast-interpretation/badge)](https://www.skillsdirectory.com/skills/sawrus-sast-dast-interpretation)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sast-dast-interpretation
description: "Interprets SAST and DAST results with a triage matrix, common false positives, and OWASP ZAP priority findings; use when reviewing security scan results, triaging vulnerabilities, or deciding which findings to fix or accept."
---

# Skill: SAST/DAST Results Interpretation

## When to load

When reviewing security scan results, triaging vulnerabilities, or deciding which findings to fix vs. accept.

## SAST Triage Matrix

| Severity | CVSS | Action | Timeline |
|:---|:---|:---|:---|
| Critical | 9.0–10.0 | Block merge, fix immediately | Same day |
| High | 7.0–8.9 | Block deploy | 72 hours |
| Medium | 4.0–6.9 | Track as tech debt | 2 weeks |
| Low | 0.1–3.9 | Backlog | Next quarter |

## Common False Positives

```
False positive: "SQL Injection" on ORM query
→ Verify ORM parameterizes internally → add suppression comment:
// snyk:ignore:sql-injection -- parameterized ORM query

False positive: "Hardcoded credential" on config key name
→ Verify value comes from env var → suppress with justification
```

## OWASP ZAP Priority Findings

1. Missing security headers (CSP, X-Frame-Options) → always exploitable, easy fix
2. Information disclosure in error responses → check stack traces
3. CSRF → verify token on all state-changing requests
4. Clickjacking → add `frame-ancestors` CSP directive
5. Insecure cookies → verify Secure, HttpOnly, SameSite=Strict/Lax

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.