Security&Compliance tab not showing to my gitlab ce
Prior to starting the security release work
-
Read the [security process for developers] if you are not familiar with it. -
Mark this [issue as related] to the Security Release Tracking Issue. You can find it on the topic of the #releasesSlack channel. - Fill out the Links section:
-
Next to Issue on GitLab, add a link to the gitlab-org/gitlabissue that describes the security vulnerability.
-
Development
-
Run scripts/security-harnessin your local repository to prevent accidentally pushing to any remote besidesgitlab.com/gitlab-org/security. -
Create a new branch prefixing it with security-. -
Create a merge request targeting masterongitlab.com/gitlab-org/securityand use the [Security Release merge request template].
After your merge request has been approved according to our [approval guidelines] and by a team member of the AppSec team, you're ready to prepare the backports
Backports
-
Once the MR is ready to be merged, create MRs targeting the latest 3 stable branches - At this point, it might be easy to squash the commits from the MR into one
- You can use the script
bin/secpickinstead of the following steps, to help you cherry-picking. See the [secpick documentation]
-
Create each MR targeting the stable branch X-Y-stable, using the [Security Release merge request template].- Every merge request will have its own set of to-dos, so make sure to complete those.
-
On the "Related merge requests" section, ensure that 4merge requests are associated: The one targetingmasterand the3backports. -
If this issue requires less than 4merge requests, post a message on the Security Release Tracking Issue and ping the Release Managers.
Documentation and final details
-
Ensure the Links section is completed. -
Add the GitLab versions and editions affected to the details section - The Git history of the files affected may help you associate the issue with a release
-
Fill in any upgrade notes that users may need to take into account in the details section -
Add Yes/No and further details if needed to the migration and settings columns in the details section -
Add the nickname of the external user who found the issue (and/or HackerOne profile) to the Thanks row in the details section
Summary
Links
| Description | Link |
|---|---|
| Issue on GitLab | #TODO |
Details
| Description | Details | Further details |
|---|---|---|
| Versions affected | X.Y | |
| GitLab EE only | Yes/No | |
| Upgrade notes | ||
| GitLab Settings updated | Yes/No | |
| Migration required | Yes/No | |
| Thanks |
Hi there,
I am using gitlab-ce, and trying to use template SAST.gitlab-ci.yml After to update my gitlab-ci.yml with following values:
include:
- template: Security/SAST.gitlab-ci.yml
I am getting below error: $ /analyzer run bash: line 111: /analyzer: No such file or directory.
Also, I'm not seeing the Security & Compliance tab in the left side. Could you please help me out?
Thanks.