> 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-posture-management/code-to-cloud/code-to-cloud/execute-remediation-workflows.md).

# Execute remediation workflows

To accomplish full traceability, close the gaps identified by the visibility surfaces using these workflows:

## Workflow 1: Close lineage gaps via the dashboard

1. Navigate to **Posture Management** → **Code-to-Cloud Coverage**.
2. Identify the SDLC stage whose **Untraced** color area is the largest (such as Deploy → Build).
3. Review the **Insights** region for the recommended action (such as Onboard CI/CD instances).
4. Select the action button to navigate to the Data Sources configuration page and complete the onboarding flow.

For more information about the Coverage dashboard, refer to [The Coverage dashboard](/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/the-coverage-dashboard.md).

## Workflow 2: Fix per-asset traceability

1. Navigate to **Inventory** → **All Assets** or a dedicated inventory, such as Kubernetes Resources or Software Packages.
2. Select and asset → open the asset side panel → click the **Code to Cloud** tab.
3. Review the display mode to understand what link is missing.
4. Select the call-to-action button (such as **Add Data Source** or **Onboard Pipeline** to execute the fix directly.

## Workflow 3: Enable infrastructure lineage via YOR tags

Without a YOR tag, an IaC resource cannot be traced to its running cloud resource.

1. Locate an IaC resource that lacks a YOR tag (indicated by a prompt in the Code-to-Cloud tab).
2. Select **Enable Tagging Bot** and complete the setup on the YOR website.
3. Ensure the matching cloud account is onboarded into Cortex Cloud so the deployed asset can be discovered and linked to the tag.


---

# 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/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/execute-remediation-workflows.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.