Policies

The Policies page provides a unified space for administrators to define and manage the rules that govern how traffic flows through a site. A single policy can apply to more than one network, client, or application at the same time. Tasks such as firewall configuration, controlling application access, port forwarding, and scheduling network availability are all managed as policies.

A policy is defined by the rule it contains. Each rule combines an Action (such as Allow, Block, Restrict, Enable, Disable, or Forward) with a Source (for example a network, a client, or an IP address) and, when the action requires it, a Destination (for example the Internet, a domain, an IP address, another network, or an application category). Optional conditions — selected protocols, bandwidth limits, and traffic priority — and an optional schedule further refine the rule. The behavior of a policy is therefore determined entirely by the rule inside it.

An Instant On site supports a maximum of 64 policies. Policies are evaluated in priority order, from highest to lowest. When more than one policy applies to the same element, the policy with the higher priority takes effect and lower-priority policies that conflict with it are ignored.

Instant On supports policy creation using the following methods:

  • Manual policy creation—Build the rule manually by selecting the action, source, destination, and optional conditions. For more information, see Manual Policy Creation.
  • AI-Assisted policy creation—Describe the intended behavior in plain language, and the Assistant translates it into a concrete policy. For more information, see Creating a Policy.

Both creation methods are available on every site in Instant On. The available actions, sources, and destinations depend on the site topology and the Instant On devices present in the site. See Policy Capabilities by Topology.

Policy Deployment

In HPE Networking Instant On network, policies are applied dynamically based on the site’s topology, so that rules are enforced where they are most effective. Wherever possible, the system enforces policies on the Instant On edge devices — the devices at the periphery of the topology — which minimizes latency and reduces reliance on centralized devices. The system balances enforcement between edge and centralized devices using techniques such as tiered enforcement and lightweight processing, so that each site operates optimally within its environment.

The HPE Networking Instant On network applies the configured rules for a site in the following order:

  1. Configured Policies—The rules defined by administrators on the Policies page. They are applied first, in the priority order shown in the policy list.
  2. Network Access Controls—Access restrictions configured per network on the Access Control tab (Networks > Access Control), based on destination. When configured, these take precedence over the site’s default rules. For detailed instructions, refer to the Networks documentation.
  3. Default rules—Applied only on sites with a deployed secure gateway. These rules are not shown in the user interface and include the following:

    • All LAN ports are granted access to the internet by default.
    • Communication between LAN networks are blocked by default.
    • All application categories are permitted on all networks by default.

Overview

The Policies > Overview section displays the list of policies created for the site, in order of their highest to lowest priority. The policy details are categorized under the following fields:

Table 1: Policy List

Field

Description

Priority

The order in which policies are evaluated. The list is shown in decreasing order of priority, with 1 being the highest.

Policy

The name of the policy.

Action

The action performed by the policy’s rule: Enable, Disable, Allow, Block, Restrict, or Forward.

Denotes the action to be performed by the policy:

  • Enable—Makes an entity type available.
  • Disable—Makes an entity type unavailable.
  • Allow—Allows an entity type.
  • Block—Blocks an entity type.
  • Restrict—Restricts an entity type. Available on gateway and switch-only sites; on switch-only sites the destination is limited to a specific IP address or subnet.
  • Forward—Forward an entity type. This action is available only for gateway sites.

Rule

A summary of the rule, showing the source and, where applicable, the destination the action applies to (for example, a network, a client, an IP address, an application category, or a forwarded port).

State

The current state of the policy (see the state descriptions below).

Schedule

The schedule during which the policy is active. Displays None when the policy is always active.

A policy can be in one of the following states:

  • Active—The policy is enabled and being enforced.
  • Inactive—The policy is disabled and is not enforced.
  • Incomplete—The policy is missing required configuration and cannot be enforced until it is corrected. When a site contains one or more incomplete policies, a banner is displayed at the top of the page Some policies are incomplete and require adjustments.
  • No Target Devices—No device currently in the site can enforce the policy — for example, the networks or devices that the rule targets are not present.

The Policies page provides the following actions:

  • Create Policy—Build a policy manually. See Manual Policy Creation.
  • Assistant—Create a policy from a natural-language description of the intended behavior. See AI-Assisted Policy Creation.
  • Reorder—Change the priority order of the policies.

To manage an existing policy, hover the cursor over the policy, click the button, and select View Details to open the policy, or Delete to remove it.

Reordering Priority

The policies are listed from highest to lowest priority. To change the order:

  1. Under Policies > Overview, click Reorder.
  2. Use the and icons to move each policy to the required priority.
  3. Click Update.

Deleting a Policy

  1. Click the Policies tile on the Instant On web application home page, or click Policies from the navigation pane on the left.
  2. Under Policies > Overview, hover the cursor over the network you want to delete, click the button, and select Delete from the drop-down list.
  3. Click Delete Policy from the pop-up window.

Policy Capabilities by Topology

Policies can be created on any site, but the available rules depend on the devices deployed in the site. As the topology gains capabilities — for example when a switch or an Instant On secure gateway is added — additional actions, sources, and destinations become available.

A gateway topology is any site that includes an Instant On secure gateway (for example, gateway only, switch and gateway, access point and gateway, or access point, switch, and gateway). Gateway topologies support the complete set of policy capabilities, including client sources, network and application destinations, port forwarding, bandwidth limits, and traffic priority.

The following table summarizes the source-to-destination combinations supported for each action, and the topologies in which they are available.

Table 2: Policy List

Action

Source

Destination

Available In

Enable / Disable

Wireless, wired, or VPN network

Not applicable (controls network availability)

Not applicable (controls network availability)

Allow / Block

Wireless network

Application category

Topologies with an access point.

Allow / Block / Restrict

Wired network

Application category

Gateway topologies

Allow / Block / Restrict

 

IP subnet or IP address

IP subnet or IP address

All topologies

Allow / Block / Restrict

 

Wired network

IP subnet or IP address

Switch only, access point + switch, and gateway topologies

Allow / Block / Restrict

 

Wired or VPN network

Internet, domain, same network, IP subnet or address, or a Wired / VPN network

Gateway topologies

Allow / Block / Restrict

 

Client

Internet, domain, or a Wired / VPN network

Gateway topologies

Allow / Block / Restrict

IP subnet or IP address

Internet, domain, or a wired/VPN network

Gateway topologies

Forward(Port Forwarding)

WAN: Internet, IP subnet, or IP address

LAN IP address and port

Gateway topologies

Enabling or disabling a VPN network requires an Instant On secure gateway.

The HPE Networking Instant On 1830 switch series does not support Allow, Block, or Restrict policies. These actions are unavailable on sites where only 1830 switches are present

AI-Assisted Policy Creation

AI-Assisted policy creation simplifies the process of setting up policies by allowing you to generate them through natural language prompts. Instead of manually configuring each setting, you can describe your requirements in plain text, and the system will automatically generate a policy based on your input.

AI-assistance is limited to policy creation only. Other Instant On configurations or any information beyond the scope of policy creation is not supported by the AI-assistance.

Policies can be created using the AI assistant (Assistant) or manual policy creation on any site topology. The categories of policies the assistant can create depend on the devices present in the site. A site with a secured gateway supports the following categories of policies:

  • Site Policy—Allow or block port forwarding.
  • Client Policy—Control destinations that can be accessed by clients on the network.
  • Network Policy—There are three types of network policies:
    • Network Activation—Activate or deactivate the network during specific times.
    • Network Firewall—Allow or block incoming and outgoing traffic to protect against unauthorized access and threats.
    • Network Access—Control destinations that can be reached from the network.
  • Application Policy—Allow or block specific applications from being used on the network.

On a Switch-only site, the assistant creates network firewall policies (Allow, Block, Restrict) between IP/subnet or wired-network sources and IP or subnet destinations.

Limitation of AI-Assistance

  • The Assistant creates policies only; it cannot modify an existing policy. To edit a policy, open it from the list (… > View Details).
  • The Assistant can assign an existing schedule to a policy, but it does not create new schedules.
  • For rules that match traffic by domain, site clients must use the secure gateway as their DNS server.

Manual Policy Creation

Manual policy creation builds a rule by choosing an action and then the source, destination, and conditions that the action allows. The options presented adapt automatically to the site topology and the devices present, so that only combinations that can be enforced are offered.

Actions

Select the action that the rule performs:

  • Enable—Makes a network available. Used with a schedule to control when a network is active.
  • Disable—Makes a network unavailable.
  • Allow—Permits the traffic that matches the rule.
  • Block—Denies the traffic that matches the rule.
  • Restrict—Limits which sources can reach a destination, permitting only the specified sources.
  • Forward—Forwards traffic arriving on a WAN port to a device on the LAN (port forwarding). Requires a secure gateway.

Source

Depending on the action and topology, the source can be one of the following:

  • Networks (LAN)—One or more of the site’s wireless, wired, or VPN networks (All Networks or Selected Networks).
  • Clients—All clients or specific clients. Requires a secure gateway
  • IP Sources—One or more IP subnets or IP addresses.
  • WAN Sources—For the Forward action: the Internet, or specific WAN IP subnets or IP addresses.

Destination

When the action requires a destination (To Access), choose from:

  • Applications—One or more application categories.
  • IP Destinations—The Internet, one or more domains, the same network, or specific IP subnets or IP addresses.
  • Networks—One or more wired or VPN networks.
  • LAN IP address and port—For the Forward action: the LAN device and port that receive the forwarded traffic.

The Same Network destination and destinations such as the Internet, domains, and other networks require a secure gateway. On sites without a gateway, network and IP sources can target IP subnets and IP addresses, and wireless networks can target application categories.

Policy Options

For rules that carry traffic, the following options refine how the traffic is treated:

  • Selected Protocols—Restrict the rule to specific protocols and ports (for example, TCP 443, or UDP 123–456). Available for IP-based destinations and for port forwarding.
  • Bandwidth Limits—Limit the download and upload bandwidth available to the matching traffic. Select Download, Upload, or both, and set the rate with the corresponding slider (maximum 1 Gbps):

    • Download—Sets the maximum download rate for the matching traffic.
    • Upload—Sets the maximum upload rate for the matching traffic.
  • Traffic Priority—Assign a priority to the matching traffic, so that it is favored or deprioritized relative to other traffic when the connection is congested. Select one of the following priority levels:
    • Low—The lowest priority, for bulk transfers and other non-critical traffic that can tolerate delay.
    • Medium (default)—The default priority, for traffic that is not time-sensitive, such as most standard applications (best effort).
    • High—A higher priority for latency-sensitive traffic, such as video streaming and video conferencing.
    • Very High—The highest priority, for traffic that is highly sensitive to delay and jitter, such as voice (VoIP).

Bandwidth limits and traffic priority are not supported on the HPE Networking Instant On 1830, 1930, and 1960 switch series, so these options do not apply to traffic enforced by these switches. Bandwidth limits also do not apply to traffic between sources and destinations within the same network.

Creating a Policy Manually

Instant On supports the manual policy creation process for sites, serving as a simplified alternative for users.

The following procedure describes how to create a policy:

  1. Under Policies > Overview, click Create Policy.
  2. The Set Rule and Conditions page, select Action.
  3. Select the Source for the rule and choose the specific networks, clients, or IP addresses it applies to
  4. If the action requires a destination, under To Access, select the destination and its specific values.
  5. (Optional) Under Policy Options, enable Selected Protocols, Bandwidth Limits, or Traffic Priority and configure them.
  6. Click Next.

    The Set Policy Applicability page is displayed.

  7. On the Set Policy Applicability page, enter a Name for the policy and set its priority by positioning it lower or higher relative to an existing policy.
  8. Under Schedule, select Always Active, choose an existing schedule, or create a new schedule. See Schedules.
  9. Click Create Policy.

Examples

The following examples illustrate a few of the many possible policies. The selected action determines the available sources, destinations, and options.

Make a network available only during business hours — Choose the Enable action, select the wireless networks to control, and assign a business-hours schedule. The networks are broadcast only while the schedule is active. Use Disable to make networks unavailable during a schedule.

Block an application category on selected networks — Choose the Block action, select the wireless networks as the source, and choose one or more application categories as the destination.

Forward an external port to an internal server — Choose the Forward action, select the WAN source (Internet or a specific WAN IP), the protocol and WAN port, and the LAN IP address and port that receive the traffic.

Allow only specific sources to reach a destination — Choose the Restrict action, select the source IP subnets or addresses (or networks), and the destination they are permitted to reach.