Checkmarx CxCE key terms

A method of analyzing source code without executing it to find security vulnerabilities. It inspects code structure, data flow, and control flow to identify patterns that could lead to exploitable weaknesses.

A technique that tracks untrusted input (taint) from sources to sensitive operations (sinks). If tainted data reaches a sink without being sanitized, a vulnerability is reported.

In taint analysis, a point in code where untrusted data enters the application, such as user input from HTTP requests, files, or databases. Sources are starting points for tracking potentially malicious data.

A sensitive operation in code that can cause harm if it receives untrusted data, such as a database query, file write, or command execution. Sinks are where tainted data must be checked.

A function or routine that cleans or validates untrusted data before it reaches a sink, preventing exploitation. Proper sanitization breaks the taint flow and removes the vulnerability.

A technique that examines how data moves through a program by building a graph of dependencies. It helps identify paths from sources to sinks and detect potential vulnerabilities.

A representation of all possible execution paths in a program, where nodes are basic blocks and edges show jumps. It is used in static analysis to understand code behavior and reachability.

A tree representation of the syntactic structure of source code, where each node denotes a construct. It is a fundamental data structure for static analysis and code querying.

A reported vulnerability that is not actually exploitable or real in the given context. Reducing false positives is crucial for efficient triage and developer trust.

A vulnerability that exists in the code but is not detected by the scanning tool. False negatives represent missed security issues and reduce the effectiveness of SAST.

The process of reviewing, prioritizing, and assigning scan results to determine which are genuine vulnerabilities and which are false positives. It often involves manual inspection and team collaboration.

A label assigned to a scan result to indicate its status, such as To Verify, Confirmed, False Positive, or Fixed. States help track remediation progress and filter results.

A rating that indicates the potential impact of a vulnerability, typically ranging from Low to Critical. It helps prioritize remediation efforts based on risk.

A declarative query language used to write custom security queries for the Checkmarx SAST engine. It allows analysts to define patterns and data flows to detect specific vulnerabilities.

A set of instructions written in CxQL that defines the logic to detect a specific type of vulnerability. Queries are organized into query packs and executed during scans.

A collection of queries grouped by category or purpose, such as OWASP Top 10 or PCI DSS. Query packs are used to configure which checks are run during a scan.

A predefined set of queries and settings that determines which vulnerabilities a scan looks for. Presets simplify scan configuration by providing ready-to-use configurations for common standards.

A container in Checkmarx that holds the source code, scan settings, and results for a specific application. Projects are the primary unit for organizing scans and managing remediation.

An execution of the static analysis engine on a project's source code using a defined configuration. Scans produce results that are stored and can be reviewed over time.

The set of parameters that define how a scan is performed, including preset, query filters, scan type, and scheduling. Proper configuration ensures relevant and efficient analysis.

A scan that analyzes only the changes made since the last scan, rather than the entire codebase. It reduces scan time and is useful for continuous integration.

A scan that analyzes the entire codebase from scratch, providing a complete picture of vulnerabilities. It is more time-consuming but ensures no issues are missed due to changes.

The Checkmarx Static Application Security Testing solution that analyzes source code for security vulnerabilities. It includes the scanning engine, management console, and query language.

Checkmarx Certified Expert, a certification for professionals who demonstrate advanced knowledge of Checkmarx products and secure coding practices. The exam covers SAST, SCA, and integration.

Checkmarx Software Composition Analysis, a tool that identifies open-source components and their known vulnerabilities. It helps manage risks from third-party libraries.

The process of identifying open-source components in a codebase and assessing their security, license, and quality risks. It is essential for managing third-party dependencies.

The potential security, legal, or operational issues introduced by using open-source software, such as vulnerabilities, license violations, or outdated components. Managing this risk is a key part of SCA.

An external library or component that a project relies on to function. Dependencies can introduce vulnerabilities if not properly maintained or updated.

The process of embedding security scanning into continuous integration and continuous delivery workflows. It enables automated detection of vulnerabilities early in the development lifecycle.

A software component that extends the functionality of an IDE or CI/CD tool to integrate Checkmarx scanning. Plugins allow developers to run scans and view results without leaving their environment.

A text-based interface used to interact with Checkmarx tools for automation. The CLI allows scripting of scans, result retrieval, and management tasks.

The incorporation of Checkmarx scanning capabilities into Integrated Development Environments (IDEs) like Visual Studio or Eclipse. It helps developers find and fix vulnerabilities while coding.

The process of fixing identified vulnerabilities in the code. It involves understanding the root cause, applying a fix, and verifying that the issue is resolved.

The generation of summaries and detailed reports on scan results, trends, and compliance. Reports help stakeholders understand security posture and track remediation progress.

The configuration of automatic scans at specified times or intervals. It ensures regular security assessments without manual intervention.

The use of scripts and tools to perform repetitive tasks without human intervention, such as triggering scans or processing results. It improves efficiency and consistency in security workflows.

The evaluation of vulnerabilities based on their severity and potential impact on the application. It helps prioritize remediation efforts and allocate resources effectively.