TMA-GITLAB-2.1.10
Ensure webhooks of the build environment are secured
Description
Use secured webhooks of the build environment. Webhooks are used for triggering an HTTP request based on an action made in the platform. Typically, build environment feature webhooks for a pipeline trigger based on source code event. Since webhooks are an HTTP POST request, they can be malformed if not secured over SSL. To prevent a potential hack and compromise of the webhook or to the environment or web server excepting the request, use only secured webhooks.
How it is checked
Audit method: Manual review
This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --include-manual.
For each webhook in use, ensure it is secured (HTTPS) via the following process: - In your project or group, on the left sidebar, select Settings > Webhooks. - For each webhook, click Edit. - Verify if the Enable SSL verification checkbox is checked. - Select Add webhook.
How it is fixed
Fix method: Guidance or infrastructure patch
For each webhook in use, change it to secured (over HTTPS). - In your project or group, on the left sidebar, select Settings > Webhooks. - For each webhook, click Edit. - Ensure the Enable SSL verification checkbox is checked. - Select Save.
Properties
- Operating systems
- Any
- Tags
- devsecopsgitlab
- Reference
- CIS GitLab Benchmark v1.0.1 - 2.1.10 Ensure webhooks of the build environment are secured