Creating network zones in the UI

1. Go to Manage > Context-based restrictions in the IBM Cloud® console.

2. Select Network zones.

3. Click Create.

4. Name your network zone and provide a description.

5. Enter your Allowed IP addresses. You can enter a single IP address, a range of IP addresses, or a single CIDR.

   The Denied IP addresses field is optional and should include only exceptions that are contained within the IP ranges you provide in the allowed IP addresses field.

6. Choose your Allowed VPCs, selecting as many as you like.

7. Reference a service: You can select Hyper Protect Crypto Services as a source service for context-based restrictions, but not as a target service. For example, you can provision a Hyper Protect Crypto Services deployment using BYOK from IBM® Key Protect for IBM Cloud®. In this example, Hyper Protect Crypto Services is the source formation and IBM® Key Protect for IBM Cloud® is the target formation. Then, you would create a network zone with a Hyper Protect Crypto Services service reference and create a rule associated with the network zone that targets IBM® Key Protect for IBM Cloud®. To add a Hyper Protect Crypto Services service reference, for Service Type, IAM services is autoselected. In the Service dropdown, select a specific Hyper Protect Crypto Services service. If the zone you create is associated with a rule targeting Hyper Protect Crypto Services, then a service reference is not allowed.

Creating network zones in the CLI

To create network zones in the CLI, install the context-based restrictions CLI plug-in. Use the cbr-zone-create command to add resources to network zones. For more information, see the context-based restrictions CLI reference.

Create a zone by using a command like:

ibmcloud cbr zone-create --addresses=1.1.1.1,5.5.5.5 --name=<NAME>

Update a zone by using a command like:

ibmcloud cbr zone-update <ZONE-ID> --addresses=1.2.3.4 --name=<NAME>

Updating requires the ZONE-ID, not the zone name. Use the following command to list your zones and retrieve the relevant ZONE-ID:

ibmcloud cbr zones

The zone-update command is an overwrite. Include all of the fields that are required as if you are creating the rule from scratch. If you omit any required fields, the rule overwrites those missing fields as empty, and the rule might fail because some of those fields are required, regardless of whether they are changing the rule.

Delete a zone by using a command like:

ibmcloud cbr zone-delete <ZONE-ID>

Creating rules in the UI

1. Go to Manage > Context-based restrictions in the IBM Cloud® console.

2. Select Rules.

3. Click Create.

4. Select Hyper Protect Crypto Services.

5. Click Next.

6. Scope the rule to Specific resources. For more information, see Protecting Hyper Protect Crypto Services resources.

7. Click Continue.

8. Define the allowed endpoint types.

   • Keep the toggle set to No to allow all endpoint types.
   • Set the toggle to Yes to allow only specific endpoint types, then choose from the list.

9. Select a network zone or zones that you have already created, or create a new network zone by clicking Create.

   Contexts define from where your resources can be accessed, effectively linking your network zone to your rule.

10. Click Add to add your configuration to the summary.

11. Click Next.

12. Name your rule.

13. Select how you want to enforce the rule.

    Report-only is not available for Hyper Protect Crypto Services.

Creating rules in the CLI

To create rules in the CLI, install the context-based restrictions CLI plug-in.

To create a rule in the CLI, you need the appropriate Hyper Protect Crypto Services service_name:

• Hyper Protect Crypto Services

Create a rule by using a command like:

ibmcloud cbr rule-create --enforcement-mode enabled --context-attributes "networkZoneId=<ZONE-ID>" --resource-group-id <RESOURCE_GROUP_ID> --service-name <SERVICE-NAME> --service-instance <SERVICE-INSTANCE> --description <DESCRIPTION>

Hyper Protect Crypto Services does not currently support Control plane as an option.

Report-only is not available for Hyper Protect Crypto Services.

Update a rule by using a command like:

ibmcloud cbr rule-update <RULE-ID> --enforcement-mode disabled --context-attributes="networkZoneId=<ZONE-ID>" --resource-group-id  <RESOURCE_GROUP_ID> --service-name <SERVICE_NAME>  --description <DESCRIPTION>

The rule-update command is an overwrite. Include all of the fields that are required as if you are creating the rule from scratch. If you omit any required fields, the rule overwrites those missing fields as empty, and the rule might fail because some of those fields are required, regardless of whether they are changing the rule.

Updating requires the RULE-ID, not the rule name. Use the following command to list your rules and retrieve the relevant RULE-ID:

ibmcloud cbr rules

Delete a rule by using a command like:

ibmcloud cbr rule-delete <RULE-ID>

Use ibmcloud cbr <command> — help for a full list of options and parameters. For example, ibmcloud cbr rule-create — help outputs parameters for rule creation.

Creating rules in Terraform

To create rules using Terraform, see IBM Cloud Provider in the Terraform Registry.

To create a rule, you need the appropriate Hyper Protect Crypto Services service_name:

• Hyper Protect Crypto Services

The ibm_cbr_rule provides a resource for cbr_rule and allows a cbr_rule to be created, updated, and deleted.

Create a rule by using a command like:

resource "ibm_cbr_rule" "cbr_rule" {
  contexts {
        attributes {
            name = "networkZoneId"
            value = "559052eb8f43302824e7ae490c0281eb"
        }
        attributes {
               name = "endpointType"
               value = "private"
    }
  }
  description = "this is an example of a rule with one context one zone"
  enforcement_mode = "enabled"
  resources {
        attributes {
            name = "accountId"
            value = "12ab34cd56ef78ab90cd12ef34ab56cd"
        }
        attributes {
              name = "serviceName"
              value = "network-policy-enabled"
        }
        tags {
              name     = "tag_name"
              value    = "tag_value"
        }
  }
}

You can import the ibm_cbr_rule resource by using id, the globally unique ID of the rule.

terraform import ibm_cbr_rule.cbr_rule