Schedule execution of security tests to keep results up to date
Problem to solve
Security checks are effective at the moment they are executed, but with passing of time the results may be less and less useful because new security vulnerabilities may be found and added to the database. That's why they should be run periodically, so they can use the updated information even if the code is not changed.
Currently this process can be done using regular pipelines, but it is not optimal and not very clear to users.
Also, security testing will be mixed with "regular" jobs, and it can lower the readability of both.
Proposal
Add a feature to schedule regular security tests (once a day?), and update the security status of the app with the latest results.
It can be done in the Security Control Panel (https://gitlab.com/gitlab-org/gitlab-ee/issues/7207).
What does success look like, and how can we measure that?
Apps with security testing scheduled as a regular job.