> For the complete documentation index, see [llms.txt](https://docs.plextrac.com/plextrac-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/checkmarx.md). # Checkmarx PlexTrac supports importing XML files from **Checkmarx**. Checkmarx provides software security solutions for detecting and preventing security application vulnerabilities. The primary focus is static application security testing (SAST), which involves analyzing an application's source code to identify security vulnerabilities and coding errors before deployment. Below are the mappings of fields and any reference notes to provide context. If a field is not listed, PlexTrac does not currently import it.

## Finding Field Mappings

PlexTrac Field	Checkmarx Path	Notes
title	<Query Name=(attribute value for title)>	If the `name` attribute within the `query` element contains an underscore, PlexTrac replaces the underscore with a space
severity	<Query Severity=(attribute value for severity)>
references	<Query cweId=(attribute value for references)>
recommendations	<Result DeepLink=(attribute value for recommendations)>	PlexTrac joins all items in the DeepLink element in the Result element
description	Hard Coded w/ "This was identified via Checkmarx scanner, please view affected assets for more details."
tags	<Query categories=(attribute value for tags)> and <Query group=(attribute value for tags)>	To convert categories into a list using ";" as a delimiter, and to append the group attribute to categories to create comprehensive tags, follow these steps: Separate each category with a semicolon (;). If a category has an associated group attribute, append this attribute to the category. Ensure all tags are accurately represented.
source	Hard Coded "Checkmarx"

## Asset Field Mappings | PlexTrac Field | Checkmarx Path | Notes | | -------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------------- | | asset | \ and Path> | Ensure that both the attribute name and the element filename are present and identical. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.plextrac.com/plextrac-documentation/product-documentation-1/integrations-and-file-imports/checkmarx.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.