> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/governance/workload-protection-policies.md).
# Workload Protection Policies
Prisma Cloud includes system default policies for protecting hosts and containers from runtime incidents and for detecting vulnerabilities on these workloads.
## Enable Workload Policies
By default, the workload protection policies are disabled. You can enable these policies and use them in an alert rule for viewing alerts on runtime incidents and vulnerabilities.
1. Select **Governance** and filter on the Policy Type **Workload Incident** and **Workload Vulnerability**.
These policies are assigned as Cloud Type **Any**, and cannot be cloned.
2. Toggle the **Status** to enable the policies.
Click a policy to view the details. Each policy provides a read only view of the vulnerability management rules that power the protections.
Edit a policy and select **Manage Rules** to view the details on each rule in **Runtime Security**. You can use the system default rules or custom vulnerability [rules](/content-collections/runtime-security/vulnerability-management/vulnerability-management-policies.md).
For example, the **Hosts detected with known Vulnerabilities** policy has the corresponding rules on **Runtime Security > Defend > Vulnerabilities > Hosts**.
3. Use the workload policy in an alert rule.
See [Create an alert rule for Workload Protection](/content-collections/alerts/create-an-alert-rule-cloud-workloads.md).
---
# 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://docs.prismacloud.io/content-collections/governance/workload-protection-policies.md?ask=&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.
