Forcepoint ONE SSE Administrative Guide Document Subtitle

Home
Deployment Guides
M365 Deployment
This article will cover the steps that administrators must take to complete a successful M365 setup.

Admin Portal
Analyze
Protect
IAM
Settings
Support
Deployment Guides
- Building Complex Policies
  Customers sometime require the ability to control access to application with granularity. For example, a customer may want to allow usage of the standard mobile email client, but block usage of the Outlook mobile application.
- M365 Deployment
  This article will cover the steps that administrators must take to complete a successful M365 setup.
  - Importing Users
    Prior to an end user being able to use Forcepoint ONE SSE, the user must exist within the portal under the Users and Groups page.
  - Setting up External Authentication
    Once users have been added and configured in the Forcepoint ONE SSE portal, you will then need to configure Forcepoint ONE SSE to point to the external authentication.
  - Creating Policy
    Policy rules are used to match the context of a user's access to either a secure, allow, or deny action. Each rule operates in a similar manner to other common security appliances, e.g. NGFW (next-generation firewall), with match criteria and top down rule matching.
  - Recommended Default M365 Policy
    A good general policy when deploying M365 for the first time would be to setup two policies: One allowing Direct App Access through Client Apps for Any Group, Device, or Location. The second policy would be setup to restrict ActiveSync and Web access through Secure App Access (with applied DLP).
  - Application SSO
    Once the policy has been created, you will then need to setup Forcepoint ONE SSE as SSO inside of Microsoft 365.
  - Examples
    From the example policy above, let’s take a look at a few users and how they are accessing the cloud application. For the sake of this example let’s assume that you are using an external IdP such as Okta or Ping for authentication.
Other

M365 Deployment

This article will cover the steps that administrators must take to complete a successful M365 setup.

Importing Users
Prior to an end user being able to use Forcepoint ONE SSE, the user must exist within the portal under the Users and Groups page.
Setting up External Authentication
Once users have been added and configured in the Forcepoint ONE SSE portal, you will then need to configure Forcepoint ONE SSE to point to the external authentication.
Creating Policy
Policy rules are used to match the context of a user's access to either a secure, allow, or deny action. Each rule operates in a similar manner to other common security appliances, e.g. NGFW (next-generation firewall), with match criteria and top down rule matching.
Recommended Default M365 Policy
A good general policy when deploying M365 for the first time would be to setup two policies: One allowing Direct App Access through Client Apps for Any Group, Device, or Location. The second policy would be setup to restrict ActiveSync and Web access through Secure App Access (with applied DLP).
Application SSO
Once the policy has been created, you will then need to setup Forcepoint ONE SSE as SSO inside of Microsoft 365.
Examples
From the example policy above, let’s take a look at a few users and how they are accessing the cloud application. For the sake of this example let’s assume that you are using an external IdP such as Okta or Ping for authentication.

Copyright © 2024 Forcepoint LLC