Skip to content

Update API Security settings in Secure Binaries template

Herber Madrigal requested to merge 362921-update-secure-binaries-template into master

Issue

Related to #362921 (closed)

Summary

  • Update template: Secure-Binaries.gitlab-ci.yml
    • Replace api-fuzzing with api-security
    • Latest version for API Security is now 2
  • Add tests to prevent Secure-Binaries.gitlab-ci.yml gets out sync compared to the templates DAST-API, DAST-API.latest, API-Fuzzing, and API-Fuzzing.latest.
    • For each DAST-API, DAST-API.latest, API-Fuzzing and API-Fuzzing.latest templates, it checks:
      • use the same image prefix
      • the image name is listed in the secure binaries analyzers
      • there is a job named aster the image name
      • the job sets the image version
      • the job filters the list of secure binaries analyzers
    • pipeline: sets the correct version in the api-security job

Manual QA

This is the test project, .gitlab-ci.yml file is pulling the request directly from this MR . In my understanding, the template Secure-Binaries.gitlab-ci.yml is meant to download images and add them to the registry container. Here is the registry container after a succeeded pipeline:

Edited by Herber Madrigal

Merge request reports