Customize which scanner(s) will trigger a vulnerability check
Why are we doing this work
Currently Vunerability-check rule applies to all scanners. Providing a way to define which scanner(s) should be considered will give the user more granularity.
Relevant links
Non-functional requirements
-
Documentation: -
Feature flag: -
Performance: -
Testing:
Implementation plan
-
frontend Add a dropdown with the scanners available from http://HOST/PROJECT/-/security/configuration
endpoint -
frontend Add all
as an option to keep support with the current behaviour -
backend Extend the model to support the scanners related to endpoint: http://HOST/api/v4/projects/PROJECT_ID/approval_settings/rules
-
backend Extend or derive the related rules to consider the scanners -
documentation Update related docs
Edited by Zamir Martins