> For the complete documentation index, see [llms.txt](https://docs.ox.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ox.security/ox-integrations/3rd-party-integrations/code-security-static-analysis/checkmarx-sast.md). # Checkmarx SAST ## Checkmarx SAST You can connect OX to Checkmarx SAST (CxSAST) to import the static analysis results that Checkmarx finds in your source code. Bringing those results into OX puts them next to every other finding you already track, under the same prioritization, workflows, and reporting. OX reads your Checkmarx projects and their open results through the Checkmarx API, maps each project to the matching OX application, and refreshes the findings on every scan. After the connection succeeds, OX imports Checkmarx SAST findings on the next scan and maps them to your OX applications. From there they follow the same policies, severity model, and ticketing that your other findings follow. User Name & Password is the only connection method for Checkmarx SAST. ### What OX imports from Checkmarx SAST The Checkmarx SAST connector belongs to the Code Security (Static Analysis) category. OX imports the static analysis issues that Checkmarx SAST finds in your source code. ### Prerequisites * Checkmarx SAST account: A user that can sign in to your CxSAST server and read scan results. A read-only service account is enough. * Checkmarx SAST host URL: The base URL of your CxSAST server, for example `https://checkmarx..com`. * OX permissions: Permission to configure connectors. ### Step 1: Prepare a Checkmarx SAST account \[Checkmarx SAST] OX authenticates to Checkmarx SAST with a user name and password. Create or pick an account that can read the projects you want to import. 1. Sign in to your Checkmarx SAST server as an administrator. 2. Create a service user, or choose an existing one, that has read access to the projects you want in OX. 3. Confirm the account can open the project list and see scan results. 4. Save the account user name, the password, and the server URL. ### Step 2: Connect Checkmarx SAST to OX 1. In the OX platform, go to the **Connectors** page. 2. In the search box, enter `Checkmarx SAST`. 3. Select the **Checkmarx SAST** card under **Code Security (Static Analysis)**.
| Field | What to use | | ----------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | Checkmarx SAST Host URL | The base URL of your CxSAST server, for example `https://checkmarx..com`. | | User Name | The Checkmarx SAST account that OX authenticates as. Use a dedicated read-only service account rather than a personal login. | | Password | The password for that account. OX stores it encrypted and never displays it again. | 4. Select **Verify Connectivity**. OX calls Checkmarx SAST with the values you entered and reports whether the call succeeds. 5. Select **Connect**. --- # 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.ox.security/ox-integrations/3rd-party-integrations/code-security-static-analysis/checkmarx-sast.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.