Organization Policy Service gives you centralized, programmatic
control over your organization's resources. As the
[organization policy administrator](https://docs.cloud.google.com/resource-manager/docs/organization-policy/using-constraints#add-org-policy-admin), you can define an organization policy,
which is a set of restrictions called constraints that apply to
Google Cloud resources and descendants of those resources in the
[Google Cloud resource hierarchy](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy.md.txt). You can enforce organization policies at
the organization, folder, or project level.

Organization Policy provides [predefined constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints) for various
Google Cloud services. However, if you want more granular, customizable
control over the specific fields that are restricted in your organization
policies, you can also create *custom constraints* and enforce those custom
constraints in a custom organization policy.

For Cloud Next Generation Firewall (Cloud NGFW), you can create and enforce custom
constraints on the following firewall policies:

- [Hierarchical firewall policies](https://docs.cloud.google.com/firewall/docs/firewall-policies.md.txt)
- [Global network firewall policies](https://docs.cloud.google.com/firewall/docs/network-firewall-policies.md.txt)
- [Regional network firewall policies](https://docs.cloud.google.com/firewall/docs/regional-firewall-policies.md.txt)

The custom constraints apply to all the rules in the
firewall policy, including predefined rules that are added when a firewall policy
is created. For more information about predefined firewall policy rules, see
[Predefined rules for firewall policies](https://docs.cloud.google.com/firewall/docs/pre-defined-rules.md.txt).

## Policy inheritance

By default, organization policies are inherited by the descendants of the
resources on which you enforce the policy. For example, if you enforce a policy
on a folder, Google Cloud enforces the policy on all projects in the
folder. To learn more about this behavior and how to change it, see
[Hierarchy evaluation rules](https://docs.cloud.google.com/resource-manager/docs/organization-policy/understanding-hierarchy#hierarchy_evaluation_rules).

## Cloud NGFW supported resources

For firewall policies, you can set custom constraints on the following
resources and fields.

- [Firewall Policies](https://docs.cloud.google.com/compute/docs/reference/rest/v1/firewallPolicies.md.txt): `compute.googleapis.com/FirewallPolicy`
  - Rule name: `resource.rules[].ruleName`
  - Description: `resource.rules[].description`
  - Priority: `resource.rules[].priority`
  - Action: `resource.rules[].action`
  - Direction: `resource.rules[].direction`
  - Is logging enabled: `resource.rules[].enableLogging`
  - Is disabled: `resource.rules[].disabled`
  - Security profile group: `resource.rules[].securityProfileGroup`
  - Is TLS inspect enabled: `resource.rules[].tlsInspect`
  - Target service accounts: `resource.rules[].targetServiceAccounts[]`
  - Target secure tags: `resource.rules[].targetSecureTags[]`
    - Name: `resource.rules[].targetSecureTags[].name`
  - Target resources: `resource.rules[].targetResources`
  - Source IP ranges: `resource.rules[].match.srcIpRanges[]`
  - Destination IP ranges: `resource.rules[].match.destIpRanges[]`
  - Layer4Config: `resource.rules[].match.layer4Configs[]`
    - IP protocol: `match.layer4Configs[].ipProtocol`
    - Ports: `resource.rules[].match.layer4Configs[].ports[]`
  - Source secure tags: `resource.rules[].match.srcSecureTags[]`
    - Name: `resource.rules[].match.srcSecureTags[].name`
  - Source address groups: `resource.rules[].match.srcAddressGroups[]`
  - Destination address groups: `resource.rules[].match.destAddressGroups[]`
  - Source FQDNs: `resource.rules[].match.srcFqdns[]`
  - Destination FQDNs: `resource.rules[].match.destFqdns[]`
  - Source region codes: `resource.rules[].match.srcReigonCodes[]`
  - Destination region codes: `resource.rules[].match.destReigonCodes[]`
  - Source Network Threat Intelligence lists: `resource.rules[].match.srcThreatIntelligences[]`
  - Destination Network Threat Intelligence lists: `resource.rules[].match.destThreatIntelligences[]`

> [!NOTE]
> **Note:** To create custom constraints based on protocols or ports, we recommend using the custom CEL function `containsIpProtocolAndPort`. For example, `resource.rules.exists(rule, rule.priority < 100 &&
> (rule.match.layer4Configs.containsIpProtocolAndPort('tcp', '22')))`.

## Before you begin

- If you haven't already, set up [authentication](https://docs.cloud.google.com/compute/docs/authentication.md.txt). Authentication verifies your identity for access to Google Cloud services and APIs. To run code or samples from a local development environment, you can authenticate to Compute Engine by selecting one of the following options:

  Select the tab for how you plan to use the samples on this page:

  ### Console


  When you use the Google Cloud console to access Google Cloud services and
  APIs, you don't need to set up authentication.

  ### gcloud

  1.
     [Install](https://docs.cloud.google.com/sdk/docs/install) the Google Cloud CLI.

     After installation,
     [initialize](https://docs.cloud.google.com/sdk/docs/initializing) the Google Cloud CLI by running the following command:

     ```bash
     gcloud init
     ```


     If you're using an external identity provider (IdP), you must first
     [sign in to the gcloud CLI with your federated identity](https://docs.cloud.google.com/iam/docs/workforce-log-in-gcloud.md.txt).

     > [!NOTE]
     > **Note:** If you installed the gcloud CLI previously, make sure you have the latest version by running `gcloud components update`.

  2. [Set a default region and zone](https://docs.cloud.google.com/compute/docs/gcloud-compute.md.txt#set_default_zone_and_region_in_your_local_client).

  ### REST


  To use the REST API samples on this page in a local development environment, you use the
  credentials you provide to the gcloud CLI.
  1. [Install](https://docs.cloud.google.com/sdk/docs/install) the Google Cloud CLI.
  2. If you're using an external identity provider (IdP), you must first [sign in to the gcloud CLI with your federated identity](https://docs.cloud.google.com/iam/docs/workforce-log-in-gcloud.md.txt).


  For more information, see
  [Authenticate for using REST](https://docs.cloud.google.com/docs/authentication/rest.md.txt)
  in the Google Cloud authentication documentation.

<!-- -->

- Ensure that you know your [organization ID](https://docs.cloud.google.com/resource-manager/docs/creating-managing-organization.md.txt#retrieving_your_organization_id).

### Required roles


To get the permissions that
you need to manage organization policies for Cloud NGFW resources,

ask your administrator to grant you the
following IAM roles:

- [Organization policy administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/orgpolicy.md.txt#orgpolicy.policyAdmin) (`roles/orgpolicy.policyAdmin`) on the organization resource
- To test the constraints:
  - [Compute Network Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/compute.md.txt#compute.networkAdmin) (`roles/compute.networkAdmin`) on the project
  - [Service Account User](https://docs.cloud.google.com/iam/docs/roles-permissions/iam.md.txt#iam.serviceAccountUser) (`roles/iam.serviceAccountUser`) on the project


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).


These predefined roles contain

the permissions required to manage organization policies for Cloud NGFW resources. To see the exact permissions that are
required, expand the **Required permissions** section:


#### Required permissions

The following permissions are required to manage organization policies for Cloud NGFW resources:

- `orgpolicy.constraints.list`
- `orgpolicy.policies.create`
- `orgpolicy.policies.delete`
- `orgpolicy.policies.list`
- `orgpolicy.policies.update`
- `orgpolicy.policy.get`
- `orgpolicy.policy.set`


You might also be able to get
these permissions
with [custom roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt) or
other [predefined roles](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#predefined).

## Set up a custom constraint

You can create a custom constraint and set it up for use in organization
policies by using the Google Cloud console or Google Cloud CLI.

### Console

1. In the Google Cloud console, go to the **Organization policies** page.

   [Go to Organization policies](https://console.cloud.google.com/iam-admin/orgpolicies)
2. Select the **Project picker** at the top of the page.

3. From the **Project picker**, select the resource for which you want
   to set the organization policy.

4. Click **Custom constraint**.

5. In the **Display name** box, enter a human-friendly name for the
   constraint. This field has a maximum length of 200 characters.
   Don't use PII or sensitive data in constraint names, because they could be
   exposed in error messages.

6. In the **Constraint ID** box, enter the name you want for your new
   custom constraint. A custom constraint must start with `custom.`, and can
   only include uppercase letters, lowercase letters, or numbers, for
   example, `custom.createFirewallPolicy`. The maximum length of this field is 70
   characters, not counting the prefix, for example,
   `organizations/123456789/customConstraints/custom.`.

7. In the **Description** box, enter a human-friendly description of the
   constraint to display as an error message when the policy is violated.
   This field has a maximum length of 2,000 characters.

8. In the **Resource type** box, select the name of the Google Cloud
   REST resource containing the object and field you want to restrict. For
   example, `compute.googleapis.com/FirewallPolicy`.

9. Under **Enforcement method** , select whether to enforce the constraint
   on the REST `CREATE` method only or on both the REST `CREATE` and
   `UPDATE` methods.

10. To define a condition, click
    **Edit condition**.

    1. In the **Add condition** panel, create a CEL condition that refers to a
       supported service resource. This field has a maximum
       length of 1,500 characters.

    2. Click **Save**.

11. Under **Action**, select whether to allow or deny the evaluated method if
    the above condition is met.

12. Click **Create constraint**.

When you have entered a value into each field, the equivalent YAML
configuration for this custom constraint appears on the right.

### gcloud

To create a custom constraint using the Google Cloud CLI, create a YAML file
for the custom constraint:

```yaml
name: organizations/ORGANIZATION_ID/customConstraints/CONSTRAINT_NAME
resource_types: compute.googleapis.com/RESOURCE_NAME
method_types:
– METHOD1
– METHOD2
condition: "CONDITION"
action_type: ACTION
display_name: DISPLAY_NAME
description: DESCRIPTION
```

Replace the following:

- `ORGANIZATION_ID`: your organization ID, such as
  `123456789`.

- `CONSTRAINT_NAME`: the name you want for your new
  custom constraint. A custom constraint must start with `custom.`, and can
  only include uppercase letters, lowercase letters, or numbers, for
  example, `custom.createFirewallPolicy`. The maximum length of this field is 70
  characters, not counting the prefix, for example,
  `organizations/123456789/customConstraints/custom`.

- `RESOURCE_NAME`: the name (not the URI) of the
  Compute Engine API REST resource containing the object and field
  you want to restrict. For example, `FirewallPolicy`.

- `METHOD1,METHOD2,...`: a list of
  RESTful *methods* for which to enforce the constraint. Can be `CREATE`
  or `CREATE` and `UPDATE`.

- `CONDITION`: a [CEL condition](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language) that is written against
  a representation of a supported service resource. This field has a maximum
  length of 1,500 characters. See
  [Supported resources](https://docs.cloud.google.com/firewall/docs/custom-constraints-fw-policy.md.txt#supported-resources) for more information about the
  resources available to write conditions against.

- `ACTION`: the action to take if the `condition` is
  met. This can be either `ALLOW` or `DENY`.

- `DISPLAY_NAME`: a human-friendly name for the
  constraint. This field has a maximum length of 200 characters.

- `DESCRIPTION`: a human-friendly description of the
  constraint to display as an error message when the policy is violated.
  This field has a maximum length of 2,000 characters.

For more information about how to create a custom constraint, see
[Defining custom constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#defining_custom_constraints).

### Console


To create a custom constraint, do the following:

1. In the Google Cloud console, go to the **Organization policies** page.

   [Go to Organization policies](https://console.cloud.google.com/iam-admin/orgpolicies)
2. From the project picker, select the project that you want to set the organization policy for.
3. Click **Custom constraint**.
4. In the **Display name** box, enter a human-readable name for the constraint. This name is used in error messages and can be used for identification and debugging. Don't use personally identifiable information (PII) or sensitive data in display names because this name could be exposed in error messages. This field can contain up to 200 characters.
5. In the **Constraint ID** box, enter the ID that you want for your new custom constraint. A custom constraint can only contain letters (including upper and lowercase) or numbers, for example `` `custom.createFirewallPolicy` ``. This field can contain up to 70 characters, not counting the prefix (`custom.`), for example, `organizations/123456789/customConstraints/custom`. Don't include PII or sensitive data in your constraint ID, because it could be exposed in error messages.
6. In the **Description** box, enter a human-readable description of the constraint. This description is used as an error message when the policy is violated. Include details about why the policy violation occurred and how to resolve the policy violation. Don't include PII or sensitive data in your description, because it could be exposed in error messages. This field can contain up to 2000 characters.
7. In the **Resource type** box, select the name of the Google Cloud REST resource containing the object and field that you want to restrict---for example, `container.googleapis.com/Cluster`. Most resource types support up to 20 custom constraints. If you attempt to create more custom constraints, the operation fails.
8. This constraint can only be enforced on the REST `CREATE` method.
9. To see supported methods for each service, find the service in [Services that support custom constraints](https://docs.cloud.google.com/organization-policy/reference/custom-constraint-supported-services.md.txt).
10. To define a condition, click **Edit condition**.
    1. In the **Add condition** panel, create a CEL condition that refers to a supported service resource, for example, `resource.autopilot.enabled == false`. This field can contain up to 1,500 characters. For details about CEL usage, see [Common Expression Language](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language). For more information about the service resources you can use in your custom constraints, see [Custom constraint supported services](https://docs.cloud.google.com/resource-manager/docs/organization-policy/custom-constraint-supported-services).
    2. Click **Save**.
11. Under **Action**, select whether to allow or deny the evaluated method if the condition is met.
12. The deny action means that the operation to create or update the resource is blocked if the condition evaluates to true.
13. The allow action means that the operation to create or update the resource is permitted only if the condition evaluates to true. Every other case except those explicitly listed in the condition is blocked.
14. Click **Create constraint**.
15. When you have entered a value into each field, the equivalent YAML configuration for this custom constraint appears on the right.

### gcloud

1. To create a custom constraint, create a YAML file using the following format:

```yaml
name: organizations/ORGANIZATION_ID/customConstraints/CONSTRAINT_NAME
resourceTypes: RESOURCE_NAME
methodTypes:
  - CREATE
condition: "CONDITION"
actionType: ACTION
displayName: DISPLAY_NAME
description: DESCRIPTION
```
2. Replace the following:
   - `ORGANIZATION_ID`: your organization ID, such as `123456789`.
   - `CONSTRAINT_NAME`: the name that you want for your new custom constraint. A custom constraint can only contain letters (including upper and lowercase) or numbers, for example, `` `custom.createFirewallPolicy` ``. This field can contain up to 70 characters, not counting the prefix (`custom.`)--- for example, `organizations/123456789/customConstraints/custom`. Don't include PII or sensitive data in your constraint ID, because it could be exposed in error messages.
   - `RESOURCE_NAME`: the fully qualified name of the Google Cloud resource containing the object and field that you want to restrict. For example, `compute.googleapis.com/FirewallPolicy`. Most resource types support up to 20 custom constraints. If you attempt to create more custom constraints, the operation fails.
   - `methodTypes`: the REST methods that the constraint is enforced on. Can only be `CREATE`.
   - To see the supported methods for each service, find the service in [Services that support custom constraints](https://docs.cloud.google.com/organization-policy/reference/custom-constraint-supported-services.md.txt).
   - `CONDITION`: a [CEL condition](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language) that is written against a representation of a supported service resource. This field can contain up to 1,500 characters. For example, `` `"resource.rules.all(rule, rule.action == 'goto_next')"` ``.
   - For more information about the resources available to write conditions against, see [Supported resources](https://docs.cloud.google.com/firewall/docs/custom-constraints-fw-policy.md.txt#supported_resources).
   - `ACTION`: the action to take if the `condition` is met. Can only be `ALLOW`.
   - The allow action means that if the condition evaluates to true, the operation to create or update the resource is permitted. This also means that every other case except the one explicitly listed in the condition is blocked.
   - `DISPLAY_NAME`: a human-readable name for the constraint. This name is used in error messages and can be used for identification and debugging. Don't use PII or sensitive data in display names because this name could be exposed in error messages. This field can contain up to 200 characters.
   - `DESCRIPTION`: a human-friendly description of the constraint to display as an error message when the policy is violated. This field can contain up to 2000 characters.
3. After you have created the YAML file for a new custom constraint, you must set it up to make it available for organization policies in your organization. To set up a custom constraint, use the [`gcloud org-policies set-custom-constraint`](https://docs.cloud.google.com/sdk/gcloud/reference/org-policies/set-custom-constraint) command:

```bash
gcloud org-policies set-custom-constraint CONSTRAINT_PATH
```
4. Replace `CONSTRAINT_PATH` with the full path to your custom constraint file. For example, `/home/user/customconstraint.yaml`.
5. After this operation is complete, your custom constraints are available as organization policies in your list of Google Cloud organization policies.
6. To verify that the custom constraint exists, use the [`gcloud org-policies list-custom-constraints`](https://docs.cloud.google.com/sdk/gcloud/reference/org-policies/list-custom-constraints) command:

```bash
gcloud org-policies list-custom-constraints --organization=ORGANIZATION_ID
```
7. Replace `ORGANIZATION_ID` with the ID of your organization resource.
8. For more information, see [Viewing organization policies](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-policies#viewing_organization_policies).

## Enforce a custom constraint

You can enforce a constraint by creating an organization policy that references it, and then applying that organization policy to a Google Cloud resource.

### Console

1. In the Google Cloud console, go to the **Organization policies** page.

   [Go to Organization policies](https://console.cloud.google.com/iam-admin/orgpolicies)
2. From the project picker, select the project that you want to set the organization policy for.
3. From the list on the **Organization policies** page, select your constraint to view the **Policy details** page for that constraint.
4. To configure the organization policy for this resource, click **Manage policy**.
5. On the **Edit policy** page, select **Override parent's policy**.
6. Click **Add a rule**.
7. In the **Enforcement** section, select whether this organization policy is enforced or not.
8. Optional: To make the organization policy conditional on a tag, click **Add condition** . Note that if you add a conditional rule to an organization policy, you must add at least one unconditional rule or the policy cannot be saved. For more information, see [Scope organization policies with tags](https://docs.cloud.google.com/organization-policy/scope-policies.md.txt).
9. Click **Test changes** to simulate the effect of the organization policy. For more information, see [Test organization policy changes with Policy Simulator](https://docs.cloud.google.com/policy-intelligence/docs/test-organization-policies.md.txt).
10. To enforce the organization policy in dry-run mode, click **Set dry run policy** . For more information, see [Test organization policies](https://docs.cloud.google.com/organization-policy/test-policies.md.txt).
11. After you verify that the organization policy in dry-run mode works as intended, set the live policy by clicking **Set policy**.

### gcloud

1. To create an organization policy with boolean rules, create a policy YAML file that references the constraint:

```yaml
name: projects/PROJECT_ID/policies/CONSTRAINT_NAME
spec:
  rules:
  - enforce: true

dryRunSpec:
  rules:
  - enforce: true
```
2. Replace the following:
   - `PROJECT_ID`: the project that you want to enforce your constraint on.
   - `CONSTRAINT_NAME`: the name you defined for your custom constraint. For example, `` `custom.createFirewallPolicy` ``.
3. To enforce the organization policy in [dry-run mode](https://docs.cloud.google.com/organization-policy/test-policies.md.txt), run the following command with the `dryRunSpec` flag:

```bash
gcloud org-policies set-policy POLICY_PATH --update-mask=dryRunSpec
```
4. Replace `POLICY_PATH` with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.
5. After you verify that the organization policy in dry-run mode works as intended, set the live policy with the `org-policies set-policy` command and the `spec` flag:

```bash
gcloud org-policies set-policy POLICY_PATH --update-mask=spec
```
6. Replace `POLICY_PATH` with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.

## Example: Create a constraint that enforces all firewall rules to have logging enabled

The constraint that's described in this section prevents the creation of firewall policy rules without
logging enabled. Firewall policy rules with `goto_next` action are excluded
because they don't support logging.

### gcloud

1. Create an `enforceLoggingEnabled.yaml` constraint file with
   the following information.

   ```yaml
   name: organizations/ORGANIZATION_ID/customConstraints/custom.enforceLoggingEnabled
   resource_types: compute.googleapis.com/FirewallPolicy
   condition: "resource.rules.exists(rule, rule.action != 'goto_next' && rule.enableLogging == false)"
   action_type: DENY
   method_types: [CREATE, UPDATE]
   display_name: Enforce that all rules have logging enabled
   description: Firewall policy rules with action other than goto_next can only be created when firewall rules logging is enabled.
   ```

   Replace `ORGANIZATION_ID` with your organization ID.
2. Set the custom constraint.

   ```
   gcloud org-policies set-custom-constraint enforceLoggingEnabled.yaml
   ```
3. Create an `enforceLoggingEnabled-policy.yaml` policy file with the
   information provided in the following example and enforce this constraint
   at the project level. You can also set this at the organization or folder
   level.

   ```yaml
   name: projects/PROJECT_ID/policies/custom.enforceLoggingEnabled
   spec:
    rules:
    -- enforce: true
   ```

   Replace `PROJECT_ID` with your project ID.
4. Enforce the policy.

   ```
   gcloud org-policies set-policy enforceLoggingEnabled-policy.yaml
   ```
5. To test the constraint, create a firewall policy rule that allows
   ingress TCP traffic on port `22` with logging disabled.

   Use the following command to create a firewall policy:

   ```
    gcloud compute network-firewall-policies create test-fw-policy --global
   ```

   Then, create a rule in the policy that allows ingress TCP traffic:

   ```
    gcloud compute network-firewall-policies rules create 1000 \
        --action ALLOW \
        --direction INGRESS \
        --firewall-policy test-fw-policy \
        --src-ip-ranges 0.0.0.0/0 \
        --layer4-configs tcp:22 \
        --no-enable-logging \
        --global-firewall-policy
   ```

   The output is similar to the following:

   ```json
   ERROR: (gcloud.compute.network-firewall-policies.create) Could not fetch resource:
   - Operation denied by custom org policy: [customConstraints/custom.enforceLoggingEnabled] :Firewall policy rules with action other than goto_next can only be created when firewall rules logging is enabled.
   ```
6. Delete the firewall policy created in the previous step.

   ```
    gcloud compute network-firewall-policies delete test-fw-policy --global
   ```

   <br />

## Example: Create a constraint that enforces all ingress SSH firewall rules to have a specific source range

The constraint that's described in this section enforces that the firewall policy rules that allow ingress SSH
traffic must have source IP ranges starting with `192.168.` block.

### gcloud

1. Create a `restrictFirewallPolicyRulesSshRanges.yaml` constraint file with
   the following information.

   ```yaml
   name: organizations/$ORGANIZATION_ID/customConstraints/custom.restrictFirewallPolicyRulesSshRanges
   resource_types: compute.googleapis.com/FirewallPolicy
   condition: "resource.rules.exists(rule,
   rule.priority < 2147483644 &&
   (rule.direction == 'INGRESS') &&
   !rule.match.srcIpRanges.all(ipRange, ipRange.startsWith('192.168.')) &&
   rule.match.layer4Configs.all(l4config, l4config.ipProtocol == 'tcp' && l4config.ports.all(port, port == '22'))
   )"
   action_type: DENY
   method_types: [CREATE, UPDATE]
   display_name: Limit firewall policy rules that allow ingress SSH traffic
   description: Firewall Policy rules that allow ingress SSH traffic can only be created with allowed source ranges.
   ```

   Replace `ORGANIZATION_ID` with your organization ID.
2. Set the custom constraint.

   ```
   gcloud org-policies set-custom-constraint restrictFirewallPolicyRulesSshRanges.yaml
   ```
3. Create a `restrictFirewallPolicyRulesSshRanges-policy.yaml` policy file
   with the information provided in the following example and enforce the
   constraint at the project level. You can also set this constraint at the
   organization or folder level.

   ```yaml
   name: projects/PROJECT_ID/policies/custom.restrictFirewallPolicyRulesSshRanges
   spec:
   rules:
   – enforce: true
   ```

   Replace `PROJECT_ID` with your project ID.
4. Enforce the policy.

   ```
   gcloud org-policies set-policy restrictFirewallPolicyRulesSshRanges-policy.yaml
   ```
5. To test the constraint, create a firewall policy rule that allows
   SSH ingress TCP traffic on port `22` with source IP range `10.0.0.0/0`.

   Use the following command to create a firewall policy:

   ```
   gcloud compute network-firewall-policies create test-fw-policy --global
   ```

   Then, create a rule in the policy that allows SSH ingress traffic:

   ```
   gcloud compute network-firewall-policies rules create 1000 \
       --action ALLOW \
       --direction INGRESS \
       --firewall-policy test-fw-policy \
       --src-ip-ranges 10.0.0.0/8 \
       --layer4-configs tcp:22 \
       --global-firewall-policy
   ```

   The output is similar to the following:

   ```json
   ERROR: (gcloud.compute.network-firewall-policies.create) Could not fetch resource:
   - Operation denied by custom org policy: [customConstraints/custom.restrictFirewallPolicyRulesSshRanges]: Firewall Policy rules that allow ingress SSH traffic can only be created with allowed source ranges.
   ```
6. Delete the firewall policy created in the previous step.

   ```
   gcloud compute network-firewall-policies delete test-fw-policy --global
   ```

   <br />

## Example: Create a constraint that enforces all ingress SSH firewall rules to use specific address groups

The constraint that's described in this section requires firewall policy rules
that allow ingress SSH traffic to use only the specified organization-scoped
address groups. For more information about the address groups, see
[Address groups for firewall policies](https://docs.cloud.google.com/firewall/docs/address-groups-firewall-policies.md.txt).

### gcloud

1. Create a `restrictFirewallPolicyRulesSshAddressGroups.yaml` constraint file with
   the following information.

   ```yaml
   name: organizations/ORGANIZATION_ID/customConstraints/custom.restrictFirewallPolicyRulesSshAddressGroups
   resource_types: compute.googleapis.com/FirewallPolicy
   condition: "!resource.rules.all(rule, rule.priority >= 2147483644 || rule.match.srcAddressGroups.exists(group, ['ADDRESS_GROUP_1','ADDRESS_GROUP_2', ... , 'ADDRESS_GROUP_N'].exists(value, value == group) ) )"
   action_type: DENY
   method_types: [CREATE, UPDATE]
   display_name: Limit firewall policy rules that allow ingress SSH traffic
   description: Firewall policy rules that allow ingress SSH traffic can only be created with allowed address groups.
   ```

   Replace `ORGANIZATION_ID` with your organization ID.

   Replace `'<code><var>ADDRESS_GROUP_1</var></code>'`, `'<code><var>ADDRESS_GROUP_2</var></code>'`, ... , `'<code><var>ADDRESS_GROUP_N</var></code>'` with [unique URL identifiers](https://docs.cloud.google.com/firewall/docs/address-groups-firewall-policies.md.txt#address-group-specification)
   of the address groups that you want to allow, for example,
   `'organizations/my-org/locations/europe-west1/addressGroups/my-address-group'`.
2. Set the custom constraint.

   ```
   gcloud org-policies set-custom-constraint restrictFirewallPolicyRulesSshAddressGroups.yaml
   ```
3. Create a `restrictFirewallPolicyRulesSshAddressGroups-policy.yaml`
   policy file using the following example. Then,
   enforce the constraint at the project level. You can also
   set this constraint at the organization or folder level.

   ```yaml
   name: projects/PROJECT_ID/policies/custom.restrictFirewallPolicyRulesSshAddressGroups
   spec:
   rules:
   – enforce: true
   ```

   Replace `PROJECT_ID` with your project ID.
4. Enforce the policy.

   ```
   gcloud org-policies set-policy restrictFirewallPolicyRulesSshAddressGroups-policy.yaml
   ```
5. To test the constraint, create a firewall policy rule that allows
   SSH ingress TCP traffic on port `22` with source address group `test-address-group`.

   Use the following command to create a firewall policy:

   ```
   gcloud compute network-firewall-policies create test-fw-policy --global
   ```

   Then, create a rule in the policy that allows SSH ingress traffic:

   ```
   gcloud compute network-firewall-policies rules create 1000 \
       --action ALLOW \
       --direction INGRESS \
       --firewall-policy test-fw-policy \
       --src-address-groups organizations/my-org/locations/europe-west1/addressGroups/test-address-group \
       --layer4-configs tcp:22 \
       --global-firewall-policy
   ```

   The output is similar to the following:

   ```json
   ERROR: (gcloud.compute.network-firewall-policies.create) Could not fetch resource:
   - Operation denied by custom org policy: [customConstraints/custom.restrictFirewallPolicyRulesSshAddressGroups]: Firewall policy rules that allow ingress SSH traffic can only be created with allowed address groups.
   ```
6. Delete the firewall policy created in the previous step.

   ```
   gcloud compute network-firewall-policies delete test-fw-policy --global
   ```

   <br />

Similarly, you can enforce all ingress SSH firewall rules to use only specific
project-scoped address groups.

## What's next

- [Introduction to the Organization Policy Service](https://docs.cloud.google.com/resource-manager/docs/organization-policy/overview)
- [Create and manage organization policies](https://docs.cloud.google.com/resource-manager/docs/organization-policy/using-constraints)
- [Organization policy constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints)