> 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/cortex-cloud-runtime-security/code-to-cloud/code-to-cloud/investigate-issues-with-c2c.md).

# Investigate issues with C2C

**Vulnerabilities** and **IaC Misconfiguration** issues include a **Code to Cloud** tab in the issue side panel. The tab traces the specific defect from the code file to the impacted runtime resource, helping the investigator verify whether a vulnerability is actively deployed before prioritizing remediation.

When to investigate issues: Because the trace originates from the specific issue rather than from the asset as a whole, issue investigation is the surface to use when the question is **is this specific vulnerability live in production**, as distinct from i**s this asset fully traced** (the Code-to-Cloud tab) or **how many assets like this one are untraced** (the Coverage dashboard).

For information on CVE vulnerabilities, refer to [Investigate and remediate CVE vulnerability issues](/application-security/code-security/code-security-scanners/software-composition-analysis-sca-scanners/software-composition-analysis-sca-vulnerability-issues/investigate-and-remediate-cve-vulnerability-issues.md).

For information on IaC misconfiguration issues, refer to [Investigate and remediate IaC misconfiguration issues](/application-security/code-security/code-security-scanners/infrastructure-as-code-iac-misconfiguration-scanner/investigate-and-remediate-iac-misconfiguration-issues.md).


---

# 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://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/code-to-cloud/code-to-cloud/investigate-issues-with-c2c.md?ask=<question>&goal=<user_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.