> 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/software-supply-chain-security/trustchain-center.md).

# Trustchain Center

Trustchain Center is the Supply Chain Security dashboard that scores how trustworthy the container images your organization builds and ships are, shows where in the delivery lifecycle the risk is concentrated, and ranks the fixes that raise the score most.

**Trustchain Center answers one question on one page**: how trustworthy is the software we ship, and which single fix improves that most? Without Trustchain Center, answering that question means reading artifact trust, pipeline risk, compliance standing, and supply chain attack exposure in separate tables.

**Scope**: Trustchain Center measures and prioritizes. It reads the results of Supply Chain Security scanning and links to the finding tables and asset panels where remediation happens. It does not scan, block, or alert on its own.

#### What you use Trustchain Center for

**Routine posture review**

* Image trust and estate coverage Score
* Risk source breakdown and team ownership Trust Factors
* SDLC bottleneck / risk concentration Risk Hotspots Across the Supply Chain

**Remediation prioritization**

* Highest-ROI fixes by Trust Score point gain Recommended High-Impact Actions

**Incident and threat response**

* Exposure to newly announced supply chain attacks Latest Supply Chain Attacks

**Compliance and benchmark tracking**

* Assessed coverage for OWASP CI/CD, CIS GitHub/GitLab Compliance Coverage

### Prerequisites

| Prerequisite                | Requirement                                                                                                                                                                                                             |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| License                     | An active Cortex Cloud license                                                                                                                                                                                          |
| Permissions                 | Same permissions needed to view the asset inventory (View)                                                                                                                                                              |
| Data                        | At least one data source onboarded and at least one Supply Chain Security scan completed                                                                                                                                |
| Data visibility             | Data scope does not apply. Every user who opens Trustchain Center sees the same tenant-wide figures, even when the user's data scope is restricted elsewhere                                                            |
| Destination access controls | <p>When you pivot from the dashboard, destination permissions require specific access controls for the target page (such as Issues, Findings, or Asset Inventory) to view its details or act on its data</p><p><br></p> |

#### Who uses Trustchain Center

* **AppSec manager**. Assess environment-wide trust posture, track compliance coverage, and identify which delivery phase warrants investment
* **AppSec practitioner**. Identify the highest-impact remediation actions, pivot into the finding tables that hold them, and confirm exposure to named attacks


---

# 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/application-security/software-supply-chain-security/trustchain-center.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.
