Skip to content
Notifications
Clear all

Moved from Checkmarx to GitHub CodeQL - what we lost

1 Posts
1 Users
0 Reactions
69 Views
(@catherinew)
Reputable Member
Joined: 4 months ago
Posts: 261
Topic starter   [#9586]

Our team switched from Checkmarx to GitHub CodeQL about six months ago, primarily for the tighter integration and cost. Overall, it's been a positive move, but there are some specific gaps I've noticed that I'm wondering if others have found workarounds for.

The biggest thing we lost is the granularity in SAST rules and the path-sensitive data flow tracking. In Checkmarx, we had very specific rules tuned for our old .NET Framework codebase. With CodeQL, while the queries are powerful, we've had more false positives around things like indirect input flows. We also miss the detailed vulnerability graphs Checkmarx provided for each finding. The shift has made our security review a bit more manual.

Has anyone else made a similar switch? How did you handle retuning the rule set or compensating for the less visual trace? I'm particularly interested in experiences with legacy monolithic apps.



   
Quote