Forcepoint ONE SSE Deployment Guide Document Subtitle

Home
Integrate identity
You can configure user identity settings and synchronize user information from your directory in order to assign policies to users or groups.
Authenticating users
Forcepoint ONE SSE enables you to enforce user authentication using any one of the three methods.
Configuring ACS Proxy
This section describes how to configure ACS Proxy in Microsoft 365, Microsoft Entra ID and Okta.

Verify access and perform initial configuration
Describes about initial account configurations, such as creating and assigning administrator accounts and roles, and configuring portal access and timeout policies in Forcepoint ONE Security Service Edge.
Integrate identity
You can configure user identity settings and synchronize user information from your directory in order to assign policies to users or groups.
- Provisioning users
  Prior to an end user being able to use Forcepoint ONE SSE, the user must exist within the portal under the IAM > User and Groups page.
- Authenticating users
  Forcepoint ONE SSE enables you to enforce user authentication using any one of the three methods.
  - Adding external IdPs in Forcepoint ONE SSE
    You can configure various applications to support Forcepoint ONE SSE as a SAML Service Provider.
  - Using advanced IdP settings
    Use the additional information that may be needed during your IdP setup that is not covered in the primary setups, such as Default Relay State.
  - Configuring ACS Proxy
    This section describes how to configure ACS Proxy in Microsoft 365, Microsoft Entra ID and Okta.
    - Configuring ACS Proxy with PingFed for M365 and AD
      You can setup an ACS Proxy working with Forcepoint ONE SSE, PingFed, and Microsoft365 using Active Directory 2019 as the directory store.
    - Setting Okta ACS proxy
      Use the provided Forcepoint ONE SSE Python script which calls the Okta API to setup the ACS Proxy.
- Provisioning new domains
  You can provision as many email domains as you wish to add into the Forcepoint ONE SSE system. Every email domain that you wish to use within Forcepoint ONE SSE must be configured, along with a corresponding authentication type for users logging in with email addresses in that domain.
Configure common components
Describes how to configure common components such as login policies, various notifications, custom notification files and so on.
Setup traffic steering
Forcepoint ONE SSE supports SmartEdge Agent and Cloud SWG traffic steering methods. This chapter describes steps to deploy each of those so that traffic can be forwarded to Forcepoint ONE SSE.
Configure DLP
DLP is a data loss prevention capability that allows for pattern matching (via regular expressions and keywords) against data as it is either being downloaded, uploaded, or scanned via API at rest.
Configure Zero Trust Network Access
Forcepoint ONE SSE's Agentless and Agent-based Zero Trust Network Access (ZTNA) provides an alternative to VPNs allowing admins to provide inline protection to internal apps without the need for VPN service to be running on the user's local machine.
Protect cloud applications
This chapter describes how to setup various cloud applications in Forcepoint ONE SSE so that Admins can monitor the data at rest and data in motion.
Configure policies
Describes how to configure policies for your application in Forcepoint ONE SSE portal so that you can monitor the data at rest and data in motion.
Monitor and analyze traffic
You can perform steps to monitor and analyze the traffic. Forcepoint ONE SSE Log Export REST API allows customers to query and pull cloud and access Logs. Alternatively, customers with Splunk or QRadar can instead utilize the Forcepoint ONE SSE Splunk app or the Forcepoint ONE SSE QRadar App for easy integration with the Forcepoint ONE SSE REST API to extract Forcepoint ONE SSE logs.
Configure applications
Forcepoint ONE SSE supports various cloud applications so that Admins can monitor data which is in transit, in motion and at rest.

Configuring ACS Proxy

This section describes how to configure ACS Proxy in Microsoft 365, Microsoft Entra ID and Okta.

Configuring ACS Proxy with PingFed for M365 and AD
You can setup an ACS Proxy working with Forcepoint ONE SSE, PingFed, and Microsoft365 using Active Directory 2019 as the directory store.
Setting Okta ACS proxy
Use the provided Forcepoint ONE SSE Python script which calls the Okta API to setup the ACS Proxy.

Copyright © 2024 Forcepoint LLC