With this update, Checkmarx Analytics will focus exclusively on production branches, such as main or master, of each project. This approach optimizes both clarity and performance by filtering out data from non-production branches, reducing noise, and ensuring that insights directly support production-critical decisions.
Historically, vulnerability data was collected and displayed across all project branches. This meant that security insights from non-production branches, such as testing or development branches, were included in the analytics. While comprehensive, this approach sometimes introduced noise, with issues from non-production branches potentially skewing the security posture and making it harder for teams to focus on critical vulnerabilities in production.
With the updated workflow, Checkmarx analytics will prioritize data collection and display for only the primary (production) branches of a project - typically branches named main, master, or as explicitly configured in project settings. This refined scope allows for clearer, production-focused vulnerability insights, removing non-essential data from non-production branches.
Historical Data: Remains unaffected and accessible across all branches, maintaining historical insights for all previous scans.
New Scans: For future scans, vulnerability data will be collected solely from production branches, excluding test and development branches to ensure cleaner, more production-relevant insights.
Improved Relevance: By limiting visibility to production branches, users gain a more accurate view of critical vulnerabilities impacting production environments.
Reduced Noise: Excluding test and development data from analytics views reduces distraction, allowing teams to focus on actionable vulnerabilities.
Performance Optimization: Focusing data processing on fewer branches enhances system performance, leading to faster load times and a more responsive experience.
Primary Branch Configuration: The branch designated as the primary branch on the project overview page is prioritized.
Protected Branches: Branches flagged as protected during the integration setup are included.
Naming Convention: The system automatically includes branches named
Main,Master, orDev.
Go to Project Settings in Checkmarx One and select the desired branch as primary. The system will then prioritize this branch in Analytics views upon the next scan.