Service architecture
Forcepoint Dynamic Edge Protection provides a global service that is logically segmented by geographical jurisdiction. The core platform is hosted in three main geographical jurisdictions: US, EMEA, and APAC. During service onboarding, you must select the most appropriate jurisdiction for your account. All data and log storage for your account is hosted within this jurisdiction.
The management portal is hosted within the core platform for your chosen geographical jurisdiction. When configuration changes are deployed, the service distributes your configuration settings to leaf nodes in multiple regions, which process the traffic from your sites before routing it to the Internet.
Overview of logical architecture for Forcepoint Dynamic Edge Protection
- 1
- Dynamic Edge Protection is accessed via a secure management portal that connects you to your service instance. Administrators can configure sites, policies, resources, and run reports.
- 2
- The core service platform for your account is hosted in a single geographical jurisdiction that acts a continental hub (US, EMEA, or APAC). All log and data storage for your account is hosted
at data centers within this jurisdiction. Core platform services communicate with data centers in multiple regions.Note: After initial account setup, the geographical jurisdiction for your account cannot be changed.
- 3
- Regions act as leaf nodes that host the service engines to which your sites connect. Your account has dedicated engines that run your services within the region. Regional nodes process traffic from your sites before routing it to the Internet. When you deploy configuration changes for your account, your changes are deployed to all affected service engines within the regions that service your sites.
- 4
- Your sites forward traffic to Dynamic Edge Protection data centers via IPsec or GRE tunneling. You can connect each site to multiple data centers for connection redundancy.