> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-runs/add-gitlab-runner.md).
# GitLab Runner
Integrate Prisma Cloud Code Security with GitLab Runner to seamlessly embed vulnerability detection into your GitLab CI/CD pipelines. This integration enables continuous scanning of your workflow whenever changes are pushed or triggered,integrating security checks, and catching issues as soon as they are introduced. Additionally, it automates shift-left actions such as notifying developers or creating tickets, based on scan results.
1. Before you begin.
1. [Generate and copy the Prisma Cloud access key](/content-collections/administration/create-access-keys.md) to enable access to Prisma Cloud. The access key includes a Key ID and Secret.
2. Add the Prisma Cloud IP addresses and hostname for Application Security to an [allow list](/content-collections/get-started/console-prerequisites.md) to enable access to the Prisma Cloud Console.
2. Create or open the `.gitlab-ci.yml` file in your repository for editing, or alternatively, navigate to **CI/CD** > **Editor** in your GitLab project.
3. Add your Prisma **Access Key** and Prisma **Secret Key** as GitLab environment variables named `PRISMA_ACCESS_KEY` and `PRISMA_SECRET_KEY` respectively.
For additional information about GitLab variables, refer to the [GitLab documentation on creating custom variables](https://docs.gitlab.com/ee/ci/variables/#create-a-custom-variable-in-the-ui).
4. Add the following job code to the appropriate stage in the file.
```yaml
stages:
- validate
prisma-cloud:
variables:
PRISMA_API_URL: https://api.prismacloud.io
image:
name: bridgecrew/checkov:latest
entrypoint:
- '/usr/bin/env'
- 'PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
stage: validate
script:
- checkov -d . --bc-api-key $PRISMA_ACCESS_KEY::$PRISMA_SECRET_KEY --repo-id $CI_PROJECT_NAMESPACE/$CI_PROJECT_NAME --branch $CI_COMMIT_REF_NAME --use-enforcement-rules -o cli -o junitxml --output-file-path console,prismacloud.xml
artifacts:
paths:
- prismacloud.xml
reports:
junit: prismacloud.xml
```
Update the `PRISMA_API_URL` with the `API URL` corresponding to your Prisma Cloud stack. Refer to the [available list of URLs](/content-collections/get-started/console-prerequisites.md) for more information.
## Verify Integration
To verify the integration with Prisma Cloud, in **Application Security**, select **Home** > **Settings** > **CICD Runs** tab. Your integrated repositories will be displayed. You may have to wait for up to three minutes before the status of the integration is updated.
Although the Prisma Cloud UI does not natively support a GitLab Runner integration, your repository will still be visible in the UI as a CLI Repository.
## USAGE
After completing the integration, Prisma Cloud will automatically conduct a scan, and the outcomes will be presented in the **Tests** section on GitLab and on the **Projects** page of the Prisma Cloud console.
GitLab Runner does not support CI/CD Security scans.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.prismacloud.io/content-collections/application-security/get-started/connect-code-and-build-providers/ci-cd-runs/add-gitlab-runner.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.