From 3a47628adf3ad15db62f6b43316165df91a6d150 Mon Sep 17 00:00:00 2001 From: Christopher Guitarte <cguitarte@gitlab.com> Date: Tue, 31 Oct 2023 20:32:36 +0000 Subject: [PATCH] Change ZAP mention from OWASP to SSP --- doc/user/application_security/dast/proxy-based.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user/application_security/dast/proxy-based.md b/doc/user/application_security/dast/proxy-based.md index 3ef888cbf24d5..ba64517570f08 100644 --- a/doc/user/application_security/dast/proxy-based.md +++ b/doc/user/application_security/dast/proxy-based.md @@ -15,7 +15,7 @@ WARNING: Do not run DAST scans against a production server. Not only can it perform *any* function that a user can, such as clicking buttons or submitting forms, but it may also trigger bugs, leading to modification or loss of production data. Only run DAST scans against a test server. -The analyzer uses the [OWASP Zed Attack Proxy](https://www.zaproxy.org/) (ZAP) to scan in two different ways: +The analyzer uses the [Software Security Project Zed Attack Proxy](https://www.zaproxy.org/) (ZAP) to scan in two different ways: - Passive scan only (default). DAST executes [ZAP's Baseline Scan](https://www.zaproxy.org/docs/docker/baseline-scan/) and doesn't -- GitLab