Merge branch...

Merge branch '8887-update-group-security-dashboard-documentation-to-recommend-running-a-regular-pipeline' into 'master'

Add 'Keeping the dashboard up to date' section

Closes #8887

See merge request gitlab-org/gitlab-ee!8879

doc/user/group/security_dashboard/index.md

@@ -41,6 +41,15 @@ To use the group security dashboard:
 2. The configured jobs must use the [new `reports` syntax](../../../ci/yaml/README.md#artifactsreports) (see an [example job](../../../ci/examples/sast.md)).
 3. [GitLab Runner](https://docs.gitlab.com/runner/) 11.5 or above must be used to execute the jobs.
 
+## Keeping the dashboard up to date
+
+Vulnerabilities are spotted during CI/CD pipelines, so having up to date results
+depend on how often security jobs are run.
+
+In order to have the latest results displayed in the dashboard, you can
+[schedule a daily pipeline](../../project/pipelines/schedules.md), so reports
+are created even if no code change happens.
+
 ## Viewing the vulnerabilities
 
 First, navigate to the Security Dashboard found under your group's