Skip to content

Store DAST Settings external of .gitlab-ci.yml file

This issue is to discuss storing DAST settings in two locations

  • A database field that is part of the GitLab database instance.
  • A dedicated file hosted in the user's repo.

Both architectures permit multiple setting 'files', which allows the user to quick change the settings for a scan.

This diagram outlines how the DAST Analyzer would get the DAST Settings. Store_and_Use_DAST_Settings_

The benefit of externalizing the settings out of the .gitlab-ci.yml file include

  • Better setting file reuse.
  • Easer for DAST to ship with complex sample configurations.
  • Easer management of the configuration through web interfaces.
  • Workflows can be designed around the DAST settings instead of the .gitlab-ci.yml file.

Additional Issues

These issues are for the implementation of the above two strategies.