OWASP PTK Findings as ZAP Alerts

The OWASP PTK add-on version 0.3.0 for ZAP (Zed Attack Proxy) now surfaces findings from the OWASP PenTest Kit browser extension as native ZAP alerts, bridging the gap between proxy-level scanning and client-side security testing. PTK runs inside the browser to detect issues that ZAP cannot reliably see from the proxy layer alone, including UI-driven flows in single-page applications, DOM updates, JavaScript sinks in bundled code, and runtime behavior. The add-on supports three engine types: SAST for analyzing loaded JavaScript scripts, IAST for capturing runtime signals during user flows, and DAST for browser-driven request mutation. Users can select which rule packs to run, optionally enable automated scanning when the browser launches, and review all findings in ZAP's standard Alerts tab with severity filtering, false positive marking, and reporting. The integration adds 142 OWASP PTK-tagged alert types to ZAP, with a Juice Shop walkthrough demonstrating the workflow of launching a ZAP browser, exercising application flows, and reviewing client-side findings alongside traditional proxy alerts. Future plans include full automation for CI/CD pipelines. 

https://www.zaproxy.org/blog/2026-04-01-owasp-ptk-findings-to-zap-alerts/

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

KEVIntel: Real-Time Intelligence on Exploited Vulnerabilities

KEVIntel is a dynamic platform providing up-to-date information on known exploited vulnerabilities (KEVs). It aggregates data from over 50 public sources, including CISA, and enriches each entry with metadata such as EPSS scores, online mentions, scanner inclusion, and exploitation status. The platform aims to serve as an early warning system, offering insights even before official publications. KEVIntel supports various formats like JSON, CSV, and RSS, facilitating integration into security operations. These entries include CVSS scores, exploit status, and links to proof-of-concept code, aiding organizations in prioritizing remediation efforts.   https://kevintel.com/
Read more

SecObserve: Simplified Vulnerability and License Management for CI/CD Pipelines

 SecObserve is an open-source tool for managing vulnerabilities and licenses in software development and cloud environments. It integrates various vulnerability scanners into CI/CD pipelines using GitLab CI templates and GitHub Actions for streamlined setup. It offers a centralized dashboard for assessing and reporting vulnerabilities, with tools for filtering, sorting, and evaluating results. SecObserve supports automation and manual assessments to focus on resolving critical issues.  https://github.com/MaibornWolff/SecObserve/tree/dev
Read more