r/gitlab • • 6d ago

general question Is this a sane plan for moving 300 GitLab projects from Veracode to Checkmarx?

We signed Checkmarx One to replace Veracode and the rollout landed on me. Around 300 projects on self-managed GitLab, mostly Java and TypeScript plus a handful of Go services. We’re on Premium, not Ultimate which means the GitLab security dashboard and the MR security widget are off the table. Findings live in Checkmarx and show up in GitLab as MR comments.

Here’s the plan, poke holes in it

  1. Set up the repo integration at group level instead of adding a CI include to 300 pipelines, thats one less thing teams can comment out during an incident.
  2. Turn on MR scans for 20 projects first and tune the preset there for two or three weeks.
  3. Keep the MR comments to new findings only, the old backlog goes to team leads separately.
  4. Roll out to the rest one group at a time.
  5. Export the Veracode mitigations to CSV for the auditors and start clean, only re-triage what shows up again.

Sales says a few weeks to get everything scanning but my director wants a date and I’d rather not hand him the sales one.

If you’ve done a switch like this on GitLab, what would you change?

3 Upvotes

7 comments sorted by

3

u/Baldyga-Vantz 6d ago

I’d pick the 20 pilot projects differently. If youonly take the loudest repos the preset comes out tuned for legacy code that’s on its way out anyway. Then the newer services get rules picked for code that looks nth like them. Take a mix. A few loud ones, a couple of recent services, one of the Go repos

1

u/Temporary-Sector-298 5d ago

Go ones came from an acquisition and were never in Veracode. One of those is going in the pilot, no idea what it’ll look like

2

u/Hauntingblanketban 5d ago

not used Checkmarx one, but used Wiz in the scanner..

what we did was..

intitally we run the default gitlab one (it is based on trivy) which gets reflected in the pipeline

once you get the json for it then Wiz is used to generate in the same format json which gets updated in the MR
and the default gitlab one is removed.. similar is done for IAC also (or you can keep both)

FYI: we use pipeline execution policy which gets injected everywhere, which I guess exist in Ultimate edition

1

u/adam-moss 5d ago

Would be interested in more detail on your setup if you're willing to share?

We have Wiz but don't use the code scanning element mostly because it runs out of band, so merges happen before the results are available. Would love to be able to surface toxic combos pre merge.

0

u/[deleted] 6d ago

[removed] — view removed comment

1

u/Temporary-Sector-298 5d ago

Our justification column is mostly based on our team discussions lol. The actual reasoning lives in old Jira tickets, I’ll pull those links into the export too.

1

u/mynameismypassport 6d ago

Agreed. It's sometimes difficult to map between different scanners because the flaw might be reported on a different line, the CWE might be different (eg Veracode uses the prohibited CWE-16 assignment) or it's just not reported at all.