> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/checkmarx/terraform-workflow.md).

# Terraform workflow

The Terraform channel is recommended for drift-free management of multiple Checkmarx integrations and Infrastructure-as-Code workflows. 

The Cortex Cloud Terraform provider exposes the `cortexcloud_appsec_data_source_instance` resource for IaC management of Checkmarx integration instances. 

## Resource example

```
resource "cortexcloud_appsec_data_source_instance" "checkmarx_us" {
  vendor = "CHECKMARX"

  configuration {
    tenant_url = "https://ast.checkmarx.net"
    api_key    = var.checkmarx_api_key
  }

  scan_types = ["SAST", "SCA"]

  mappings {
    auto_map_future_projects = true
  }
}
```

## Common Terraform patterns

| Pattern                    | Description                                                                                                                                                                    |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Secret-managed API key** | Source the Checkmarx One API key from a secret manager (HashiCorp Vault, AWS Secrets Manager, Terraform Cloud variable sets) rather than committing the key to version control |
| **Multi-tenant fan-out**   | Use Terraform workspaces or modules with `for_each` over a tenant map to deploy the same Checkmarx integration configuration across multiple Cortex Cloud tenants              |
| **Drift detection**        | Run `terraform plan` on a schedule to detect manual UI edits to managed Checkmarx instances (for example, mapping changes or scan-type toggles)                                |
| **Module encapsulation**   | Encapsulate the Checkmarx instance, scan-type selections, and mapping configuration as a reusable Terraform module per Checkmarx One tenant                                    |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/application-security/application-security/onboard-data-sources/ingest-third-party-data-sources/checkmarx/terraform-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.