> 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-xsiam/cloud-security/rules-and-policies/base-images-rule/prerequisites.md).

# Find the base image for an asset

Find a container asset's base image in Cortex XSIAM to inspect registry image details and upstream or downstream lineage.

Container image assets include **Base Image** details that identify the foundational registry image they are derived from. If an asset is a base image, a **Base Image** property is displayed in the asset side panel.

When a Base Images Rule is created, a base image tag is assigned to matching container image assets. You can use this tag to create an **Asset Group** ( **Inventory** → **Assets** → **Groups**) by filtering on the **Image Is Base Image**. This allows you to group all base images and use the asset group for policies and issue management.

### How to find the base image for an asset

1. Navigate to **Inventory** → **Assets** → **All Assets** → **Compute** → **Container Images**.
2. Open a container image asset (**Registry Image** or **Runtime Image**).
3. In the **Overview** tab, under the **Properties** section, locate **Base Image** details to view the linked foundational registry image.
4. View the **Relationships** section to explore upstream and downstream image lineage.


---

# 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-xsiam/cloud-security/rules-and-policies/base-images-rule/prerequisites.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.