> 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-xpanse/inventory/asset-types/certificates.md).

# Certificates

The **Certificates** tab in the **Inventory** displays all certificates that Cortex Xpanse has attributed to your organization and whether Cortex Xpanse has seen each certificate advertised recently. The **Certificates** list view also indicates whether the advertisement is associated with an active service. If you have integrated cloud accounts, this tab will show you which certificates have associated managed cloud resources.

Cortex Xpanse tracks the following information for each certificate:

* Issuer, Issuer Country, Issuer Organization, Issuer State
* Public key, Public Key Algorithm
* Subject, Subject Alternative Names, Subject Organization, Subject Country, Subject State
* Serial Number
* Valid Not Before, Valid Not After
* Version
* Common Name

Additionally, Cortex Xpanse automatically tracks the following “cryptographic health” checks for certificates:

* Is Self-Signed?
* Is Wildcard?
* Is Domain Control Validated?
* Expired When Scanned?
* Public Key Bits
* Signature Algorithm

These health checks are referred to in Expander as **Certificate Classifications**.

Navigate to **Asset Inventory** → **Certificates** to view the complete list of certificates discovered by Cortex Xpanse. Certificates are also included in **All Assets** list view.

Click on a row in the **Certificates** or **All Assets** list view to display the certificate details in details pane on the right.

The table below describes the fields unique to the **Certificates** list view. The other fields are described in the [Unified Inventory](/cortex-xpanse/inventory/unified-inventory.md) section.

| Field                          | Description                                                                                                                                                                                                                                                |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Certificate Algorithm**      | Description of the cryptographic algorithms used for creating key pairs and performing digital signature operations for this certificate. Examples can include SHA1, SHA256, or SHA384 with either RSA or ECDSA.                                           |
| **Certificate Classification** | A set of cryptographic health checks that Cortex Xpanse performs for each certificate.                                                                                                                                                                     |
| **Date Added**                 | Date the asset was added to the inventory.                                                                                                                                                                                                                 |
| **Formatted Issuer Name**      | Represents an easier-to-read formatted version of the \`Issuer name\`. This is the organization that issued the certificate on behalf of your organization. In cases where the certificate is self-signed, the issuer will often be listed as **unknown**. |


---

# 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-xpanse/inventory/asset-types/certificates.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.