---
title: "Policies"
description: "Create custom compliance policies and assign them to CI groups."
product: "Guardian"
edition: "Essentials"
type: "workflow"
url: "https://docs.cloudhouse.com/guardian/essentials/compliance/policies/"
---
# Policies

A policy is a set of checks your CIs are assessed against on every scan. **Policies** lists the custom policies your CIs are assessed against.

## Create a policy

1. On **Policies**, select **Create New Policy**.
2. Name it (for example, *Endpoint Protection Policy*), describe what it enforces and why, and add tags if you use them.
3. Choose how to start:
    - **Build a policy from scratch** with your own checks.
    - **Based on Compliance Policy:** start from an industry-standard template, then adjust it.
4. Select **Next: Add Checks** and add the checks.

## Assign a policy

1. Open the policy and choose to assign it.
2. Select the CI groups to assess against it. Every member of a selected group is checked on each scan.
3. Save. The assignment summary shows which groups it covers.

If you have no CI groups yet, create one on **Scan Configuration** first. See [Groups and environments](https://docs.cloudhouse.com/guardian/essentials/cis/groups-and-environments/index.md).

## See the results

- **On a policy:** each CI's result, and each check's result by CI.
- **On a CI:** how it fared against each policy on its most recent scan.
- **On a scan:** the **Compliance Policy Results**, with **How to fix this** for failed checks.