How do I choose which profile my CI job scans?

Steps

1. Open Integrations and pick your code host tab.
2. Click the Scan profile picker. It is searchable, so type part of the profile name.
3. Select the profile you want the job to scan.
4. Check the YAML. The profile ID now sits inside it.
5. Click Copy and replace the job file in your repository.

Good to know

Where the ID lives depends on the tab.

You can edit the ID by hand later if you know the new one. Re-copying from the picker is safer, because it cannot contain a typo, and it only takes a few seconds. When a job suddenly scans the wrong app, a stale ID in an old copy is the first thing to check.

A profile belongs to one target, so one job scans one application, and a second application needs a second job that points at its own profile. Scope, authentication roles and reporting rules all come from the profile, so change those in Scan Profiles and leave the job alone. The job file then never needs an edit just because a scan setting changed.

The API also accepts a profile name in place of an ID. See how to trigger a scan by profile name. If you need the whole setup, start with how to trigger a scan from CI.

Related questions

• How do I trigger a Cyberlop scan from my CI pipeline?
• How do I copy the ready-made CI workflow for my code host?
• Can I trigger a CI scan by profile name instead of profile ID?
• Whose permissions does a CI-triggered scan run with?
• When does the generated CI workflow run?

Full tutorial

How to add security scanning to your CI/CD pipeline

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre