> 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/kubernetes-security/cloud-workload-policies-and-rules/cloud-workload-policies/cloud-workload-preventive-action.md). # Cloud workload preventive action Some Cloud Workload policies provide a Prevent and Create an Issue action that enforces compliance during deployments. ### Prevention action for Runtime stage Policies The Prevent action at Runtime applies only to Kubernetes Workload Images assets. When a Kubernetes Workload image violates a policy, the Kubernetes Admission Controller (on clusters where the KSPM Connector is deployed and Admission Control is enabled) can block it from being admitted to the cluster. For all other asset types within the policy scope, no runtime prevention will occur. Instead, the violation will result in an Issue being created. ### Prerequisites Deploy your cluster via the **Kubernetes connect** wizard. After your clusters are connected, you can manage and monitor your Kubernetes clusters for posture management and real-time protection. To access the **Kubernetes connect** page, navigate to the following URL in your tenant environment: `https://[TENANT-ADDRESS]/cwp/k8s-management.` ### Admission controller This option is enabled via the **Kubernetes connect** wizard in the **Posture management** solution option. **Policy enforcement by the admission controller** must be enabled for the admission controller to evaluate requests that help you set the right policy scope and avoid unexpected blocks. The admission controller manages the following: * Kubernetes object-level enforcement based on workload specs, including Deployments, StatefulSets, DaemonSets, ReplicaSets, Jobs, and CronJobs. * Create and update operations, re-evaluating the entire object for policy violations on every change, including simple scaling or replica updates. * Visibility for already-running workloads, surfacing existing policy violations as issues without disrupting or deleting the active resources. * Image-based blocking, relying on pre-existing scan results in the backend (such as CI, registry, or Agentless Disk Scanner results) to enforce policies without adding latency at admission time. * Trusted Images validation, blocking a workload that lacks a valid, up-to-date scan result in the backend when the policy uses the **Prevent** action on a cluster where the admission controller is enabled. ### Important considerations * **Recommended Approach**: Begin with the **Create an Issue** action to validate results before selecting **Prevent and Create an Issue**. This helps prevent potential disruptions to your applications or development workflows. * **Impact on New Deployments**: The **Prevent and Create an Issue** action affects only new or future deployments that meet the prevention criteria. It does not impact cloud workload assets that are already deployed. ### Prevention action for CI stage Policies Prevention actions in the CI stage triggers a pipeline failure by returning an exit code of 2 in the CI tool. --- # 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/kubernetes-security/cloud-workload-policies-and-rules/cloud-workload-policies/cloud-workload-preventive-action.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.