...
| Note | ||
|---|---|---|
| ||
For each option, you can choose the applicable objects from the AVAILABLE table and move them to the SELECTED table using the |
- External Networks: Select this to add external networks to the network scope. For more information, see Configuring External Networks.
- DNS Forwarding Proxy: Select this to add DNS forwarding proxies to your network scope. For more information about DNS forwarding proxy, see DNS Forwarding Proxy.
- Endpoint Groups: Select this to add BloxOne Endpoint groups to your network scope. For information about BloxOne Endpoint groups, see BloxOne Endpoint Group Assignment.
- User Groups: Select this to add user groups to the network scope. The available user groups are those that have been synchronized through the third-party IdP (identify provider) that your admin has configured for access authentication. For more information, see Synchronizing User Groups. Tags
- IPAM: Select this to add user-defined tags to your network scope. When the network scope includes an object included in multiple policies, then the policy precedence order will determine which policy is enforced. Changes in policy tagging are updated by the system and may take up to 5 minutes to complete. When multiple tagging changes occur to a security policy, the policy will reflect the most recent change to the policy. For more information on tags, see applying tags. IPAM: Select this to add this to add internal networks to the network scope. When When adding tags to to IPAM scopes, any tag-based changes in an IPAM scope based on tags can take up to 5 minutes to take effect. To To associate a security policy with DDI IPAM objects in the DNS query, do the following:
1. Select an IP Space to add to your security policy (Manage > IPAM/DHCP).
2. Click the horizontal menu item to display the IP Address block(s) associated with the IP Space. From among the listed address blocks, choose an address block to add to your security policy. Make a note of your selected IP space and address block you want associated with your security policy.
Allowing Overlapping Internal and External Subnets When Defining Security Policy Scope
When defining a security policy scope for an internal network residing behind a DNS firewall, or for an external network, then overlapping subnets containing IP addresses, hosts, or subnets included in other security policies within an organization are allowed. In this case, security policy precedence is used to select the security policy possessing the highest precedence to which the IP addresses, hosts, or subnets should be added. Subnets not already added as part of another security policy within the organization can be added to a different security policy within the same account.
If a public IP address or subnet is mistakenly added to an organization's security policy that has previously been registered by another registered organization, then the public IP address or subnet will not be allowed. In this case, the organization attempting to add the IP address or subnet will be notified regarding the issue since no overlapping of public IP addresses or subnets between organizations is allowed.
- IPAM Hosts: Select this to add IPAM hosts and DHCP ranges to your network scope. IPAM hosts and DHCP ranges can also be added to a policy using tags. When adding tags to IPAM host or DHCP range, any tag-based changes in scope-based on tags can take up to 5 minutes to take effect. To associate a security policy with an IPAM host or DHCP range, do the
1. Select an available IPAM host from those listed under AVAILABLE HOSTS on the Manage IPAM Hosts panel to add to your security policy.
2. Click
to add the IPAM host to your security policy. Or, click 
to add all available IPAM Hosts to your policy. To remove a previously selected IPAM hosts, click
.
3. Click Save followed by clicking Finish to complete the configuration process, or click Next to proceed to the next step of the configuration process. - Tags: Select this to add user-defined tags to your network scope. When the network scope includes an object included in multiple policies, then the policy precedence order will determine which policy is enforced. Changes in policy tagging are updated by the system and may take up to 5 minutes to complete. When multiple tagging changes occur to a security policy, the policy will reflect the most recent change to the policy. Network scope can be defined using tags for DNS Forwarding Proxy, Endpoints, Endpoint Groups, IPAM networks, individual IPs, IPAM Host objects, and ranges. Policy rules can be defined using tags for custom lists as well as application and category filters. For more information on tags, see Applying Tags.
- Metadata: Select this to add Metadata to your network scope. Network scope for BloxOne Endpoint can be defined using metadata for operating systems and endpoint version. To configure metadata, do the following:
- ATTRIBUTE: Select an attribute from among the listed options in the drop-down list. Attributes supported include endpoint version and OS family.
- VALUE: Select a value from among the listed options in the drop-down list to associate with the attribute. YOu can use the search tool to find a specific value. Values supported include the following operating systems:
- Windows
- MacOS
- Linux
- ChromeOS
- iOS
- Android
2. For each source you have added, click Add. The source appears in the table. You can click the Add Source menu again to choose another source for your network scope.
3. After you define your network scope, you can proceed to add policy rules, set precedence order and bypass codes.
4. Click Next in the wizard to define policy rules. For more information, see Adding Policy Rules and Setting Policy Precedence.
...