Firewall rules are only as maintainable as the objects they reference. Peplink’s grouped networks and grouped MAC addresses turn “that list of servers” and “the corporate laptops” into named, reusable, API-updatable objects that both the firewall and outbound policy understand.
Grouped networks: IP and URL lists with an API
A grouped network is a named list of IP ranges and URLs. Reference it from firewall rules and outbound policies, then manage the list in one place — including via API. Your ticketing system, CMDB, or threat-intel feed can push updates to the list and every device enforcing a policy against it follows automatically. No per-device rule edits, no drift.
Grouped MAC addresses: identity for devices
The same pattern for endpoints: a grouped MAC address list is an API-capable roster of devices usable in firewall rules and outbound policy. Corporate laptops, payment terminals, cameras, badge readers — each becomes a named group with membership you can automate from your asset system.
The pattern in one rule
Example: the Corporate PCs MAC group may reach the Corporate Servers network group — and nothing else may. One internal firewall rule expresses it. When IT images a new laptop, the asset system adds its MAC to the group via API and the policy applies everywhere, instantly. When a server moves, the network group is updated once.
This is micro-segmentation without a forklift: identity-based policy, centrally managed, enforced at every branch by hardware you already own. It pairs naturally with 802.1X on the access layer and shows up in your SIEM logs by group name, not bare addresses.
Deep dives: Grouped Networks guide · group firewall policies · group outbound policies.