From 88127d34fcf7ceb52048d7ca2c3a29a8b2621a62 Mon Sep 17 00:00:00 2001 From: Russell Dickenson <rdickenson@gitlab.com> Date: Wed, 1 Nov 2023 08:15:57 +0000 Subject: [PATCH] Include link to walkthrough video on container scanning --- doc/user/application_security/container_scanning/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/user/application_security/container_scanning/index.md b/doc/user/application_security/container_scanning/index.md index bfe3dcd9def4c..34699360228b4 100644 --- a/doc/user/application_security/container_scanning/index.md +++ b/doc/user/application_security/container_scanning/index.md @@ -22,8 +22,9 @@ vulnerabilities. By including an extra Container Scanning job in your pipeline t vulnerabilities and displays them in a merge request, you can use GitLab to audit your Docker-based apps. -<i class="fa fa-youtube-play youtube" aria-hidden="true"></i> +- <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> For an overview, see [Container Scanning](https://www.youtube.com/watch?v=C0jn2eN5MAs). +- <i class="fa fa-youtube-play youtube" aria-hidden="true"></i> For a video walkthrough, see [How to set up Container Scanning using GitLab](https://youtu.be/h__mcXpil_4?si=w_BVG68qnkL9x4l1). Container Scanning is often considered part of Software Composition Analysis (SCA). SCA can contain aspects of inspecting the items your code uses. These items typically include application and system -- GitLab