Features / Network controls
Apply allow and deny rules to the network context of roles, identity categories, tenants, provisioning integrations and API keys.
Explore the design intent, review practical decisions and validate exact behavior against your deployed configuration.
Why it matters
Network restrictions applied only at the perimeter can miss sensitive operations that run through the same identity platform. Conversely, simple IP blocks can disrupt legitimate users behind shared proxies.
Design intent
Define the scope of each network rule, maintain approved proxy/CIDR ranges, and test the rule at the actual enforcement point. Combine network restrictions with identity and session controls rather than relying on IP address alone.
Worked scenario
A provisioning endpoint accepts requests only from approved integration networks, while a tenant’s member rules remain separate from another tenant’s configuration.
Boundary to verify
Confirm enforcement at the relevant server, API, resource or operational decision point. A hidden button or an informative dashboard is not, by itself, an authorization control.
Practical path
Use these stages as a review guide. Exact settings and enforcement points depend on the configured deployment and connected systems.
Identify the actor, target resource and operation that advanced network / ip rules is meant to govern.
Define the scope of each network rule, maintain approved proxy/CIDR ranges, and test the rule at the actual enforcement point. Combine network restrictions with identity and session controls rather than relying on IP address alone.
A provisioning endpoint accepts requests only from approved integration networks, while a tenant’s member rules remain separate from another tenant’s configuration. Also test the path that should be denied, deferred or sent for review.
Check that the resulting state is understandable and that the decision can be investigated later. For audit-enabled operations, confirm the relevant actor and context are captured.
Before rollout
A capability is easier to operate when ownership, failure behavior and verification are defined upfront.
This page describes a design approach based on WebFrolic’s documented product model. Verify feature availability and exact behavior in your environment before relying on it for a control requirement.
Related capabilities
Follow the related areas to understand how this capability fits within identity, access, lifecycle and operations.
Evaluate with your scenario
Share the identities, resource boundary and decision you want to test. The walkthrough can focus on the relevant behavior rather than a generic feature tour.
