From ae9adabc4555bfb27e77274115d18b3c6d422f00 Mon Sep 17 00:00:00 2001 From: Corey Oas <coas@gitlab.com> Date: Fri, 21 Apr 2023 04:11:24 +0000 Subject: [PATCH] Clarify available DAST analyzers in FIPS mode --- doc/development/fips_compliance.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/doc/development/fips_compliance.md b/doc/development/fips_compliance.md index f0634107ba587..830a8e3cd2aa5 100644 --- a/doc/development/fips_compliance.md +++ b/doc/development/fips_compliance.md @@ -59,8 +59,7 @@ listed here that also do not work properly in FIPS mode: - [Container Scanning](../user/application_security/container_scanning/index.md) support for scanning images in repositories that require authentication. - [Code Quality](../ci/testing/code_quality.md) does not support operating in FIPS-compliant mode. - [Dependency scanning](../user/application_security/dependency_scanning/index.md) support for Gradle. -- [Dynamic Application Security Testing (DAST)](../user/application_security/dast/index.md) - does not support operating in FIPS-compliant mode. +- [Dynamic Application Security Testing (DAST)](../user/application_security/dast/index.md) supports a reduced set of analyzers. Browser-based and proxy-based analyzers are not available in FIPS mode today, however DAST API and DAST API Fuzzing images are available. - [License compliance](../user/compliance/license_compliance/index.md). - [Solutions for vulnerabilities](../user/application_security/vulnerabilities/index.md#resolve-a-vulnerability) for yarn projects. -- GitLab