> 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/cortex-cloud-saas-security/provider-instances-security-check.md).
# Provider Instances Security Check
The **Provider Instances** page provides a high-level aggregation of tenant security scores and an interactive, list view for analyzing and remediating individual instances.
\
This page consolidates SaaS application security posture data across all onboarded instances:
* Overall Security Check Score: Displays the global average posture score across all integrated instances. Applications are further categorized into three security score-based buckets:
* Up to 50% (Red): Severe posture gaps
* Between 50%–75% (Yellow): Moderate posture alignment
* Over 75% (Green): High posture alignment
* Providers (Distribution Tiles): Lists onboarded SaaS Applications with active instance count for each provider.
**Instance Inventory List**
The table displays granular telemetry for each active SaaS application.
Provider Instances: The unique, user-defined identifier/name for the specific SaaS tenant. These are hyperlinked to route administrators to the deep-dive configuration and issues page for that specific instance.
* Provider Type: The underlying third-party SaaS vendor platform associated with the instance (e.g., Mural, Cisco Meraki).
* Application Tag: Custom metadata tags assigned to instances to categorize environments for scoped policies and reporting.
* Connector Status: The operational state of the API integration. A green Connected status indicates active, authorized data ingestion.
* Overall Security Check Score: The normalized security score (0–100%) computed for the individual instance.
Click on an instance to view Passed Checks and take action on Failed Checks.
---
# 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-xsiam/cloud-security/cortex-cloud-saas-security/provider-instances-security-check.md?ask=&goal=
```
`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.