From 2b60f62fc71295cf14a008721be0ffce99b0855f Mon Sep 17 00:00:00 2001
From: Russell Dickenson <rdickenson@gitlab.com>
Date: Wed, 1 Nov 2023 08:12:49 +0000
Subject: [PATCH] Include link to walkthrough of DAST proxy-based analyzer

---
 doc/user/application_security/dast/proxy-based.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/user/application_security/dast/proxy-based.md b/doc/user/application_security/dast/proxy-based.md
index ba64517570f08..9e59ecc64d99a 100644
--- a/doc/user/application_security/dast/proxy-based.md
+++ b/doc/user/application_security/dast/proxy-based.md
@@ -11,6 +11,9 @@ The DAST proxy-based analyzer can be added to your [GitLab CI/CD](../../../ci/in
 This helps you discover vulnerabilities in web applications that do not use JavaScript heavily. For applications that do,
 see the [DAST browser-based analyzer](browser_based.md).
 
+<i class="fa fa-youtube-play youtube" aria-hidden="true"></i>
+For a video walkthrough, see [How to set up Dynamic Application Security Testing (DAST) with GitLab](https://youtu.be/EiFE1QrUQfk?si=6rpgwgUpalw3ByiV).
+
 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.
-- 
GitLab