Checkmarx CxCE study guide
Checkmarx CxCE · Work through your exam, one topic at a time.
The Checkmarx Certified Engineer (CxCE) credential is aimed at security engineers, DevSecOps practitioners, and application security leads who administer and operate Checkmarx in real delivery pipelines rather than merely reading scan reports. It tests the working knowledge that separates someone who can install the platform from someone who can keep it producing trustworthy, actionable results across many projects and teams. The Checkmarx CxCE study guide has 8 sections and about 3,477 words.
01SAST Fundamentals and Secure Coding Concepts
This domain checks whether you understand how CxSAST decides that a line of code is a vulnerability, and whether you can map results back to secure-coding patterns. Questions rarely ask for a definition; they ask you to judge a code snippet, a sanitizer, or a claimed false positive.
429 words, about 2 min02Checkmarx Platform Architecture, Deployment, and Administration
Architecture questions ask you to place a symptom (slow scans, invisible project, failed login) on the right component, and administration questions ask how teams, roles, engines, and licensing shape what a user can scan and see. CxManager - the central server.
453 words, about 2 min03Scan Configuration: Projects, Presets, Queries, and Scan Scheduling
Whether you can configure a project so it scans the right code with the right rule set, at the right time, and understand what each setting silently includes or excludes. A project is the container for scans and belongs to a team.
453 words, about 2 min04Scan Execution, Results Triage, and False Positive Management
Your grasp of the scan lifecycle and of the result-state workflow that turns raw findings into a defensible audit trail. Most wrong answers here come from confusing scan states with result states, or from taking actions the role does not permit.
435 words, about 2 min05Query Language (CxQL) and Custom Query Development
Whether you can read and write a CxQL query, understand how queries become active, and debug the common reasons a query "works in CxAudit but not in a scan". A CxQL query is a script that builds CxList objects and ends by assigning the final set to result .
408 words, about 2 min06IDE and CI/CD Pipeline Integration (Plugins, CLI, and Automation)
How CxSAST is embedded in a developer's editor and in an automated pipeline: which component does what, how builds are gated, and where credentials and exit codes are handled. Plugins for Eclipse, IntelliJ IDEA, and Visual Studio let developers run scans from the editor (local or on the server), view results inline, read the source-to-sink path, mark false positives with a reason, and pull remediation guidance - keeping triage close to the code.
426 words, about 2 min07Vulnerability Remediation Guidance and Reporting
How you take a triaged result and turn it into a fix, a verification step, and a report that different audiences can act on without inflating or hiding risk. Prioritize on severity, exposure of the affected entry point, exploitability, and data sensitivity - not on raw count.
433 words, about 2 min08SCA and Open-Source Risk
How CxSCA identifies open-source risk, what its scores mean, and how to remediate a dependency problem without breaking the build - plus how SCA evidence complements SAST evidence. SCA works from dependency evidence: manifest and lock files (npm, Maven, Gradle, NuGet, pip and similar) and, where source is unavailable, binary artifacts.
440 words, about 2 min