0% found this document useful (0 votes)
16 views

FP Web Security SQL Server

This document provides instructions for installing Forcepoint products with Microsoft SQL Server. It includes steps to install SQL Server, obtain login credentials, configure the SQL Server machine and client tools, and set permissions for the SQL user account.

Uploaded by

Mohamad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views

FP Web Security SQL Server

This document provides instructions for installing Forcepoint products with Microsoft SQL Server. It includes steps to install SQL Server, obtain login credentials, configure the SQL Server machine and client tools, and set permissions for the SQL user account.

Uploaded by

Mohamad
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Installing with SQL Server

Deployment and Installation Center | Forcepoint Web Security or Forcepoint URL Filtering

Applies to:

Forcepoint Web Security, v8.5.x


Forcepoint URL Filtering, v8.5.x
See System requirements for this version for which versions of SQL Server
are supported.
1.Install SQL Server according to Microsoft instructions, if needed.
2.Make sure SQL Server is running.
3.Make sure SQL Server Agent is running.

Note
If you are using SQL Server Express, SQL Service Broker is used

Obtain the SQL Server logon ID and password for a SQL Server
4.Administrator, or for an account that has the following permissions:
db_creator server role
SQLAgent role
db_datareader in msdb
For Forcepoint DLP, Forcepoint Email Security, or Forcepoint Web Security
with the Web DLP module, the account must have a sysadmin role.
You need this logon ID and password when you install Forcepoint reporting
components.
5.Restart the SQL Server machine after installation.

Note
You must restart the machine after installing Microsoft SQL Serve

Make sure the Security Manager machine and, if applicable, Log Server
6.machine or machines can recognize and communicate with SQL Server.
Install the SQL Server client tools on the Security Manager machine. Run
the SQL Server installation program, and select Connectivity Only when
7.asked what components to install.
If Log Server is installed on another machine, install the SQL Server client
tools on that machine instead.
Restart the machine after installing the connectivity option. See Microsoft
8.SQL Server documentation for details.
Configuring Microsoft SQL Server user roles
Microsoft SQL Server defines SQL Server Agent roles that govern
accessibility of the job framework. The SQL Server Agent jobs are stored in
the SQL Server msdb database.
To install Log Server successfully, the user account that owns the reporting
database must have one of the following membership roles in
the msdb database and db_datareader:
SQLAgentUserRole
SQLAgentReader Role
SQLAgentOperator Role
The SQL user account must also have dbcreator fixed server role privilege.
The Forcepoint Email Security user account must have sysadmin fixed
server role privilege.
Use Microsoft SQL Server Management Studio to grant the database user
account the necessary permissions to successfully install Log Server.
On the SQL Server machine, go to Start > Programs > Microsoft SQL
1.Server > Microsoft SQL Server Management Studio.
2.Log into SQL Server as a user with SQL sysadmin right.
Select the Object Explorer tree, and then go to select Security >
3.Logins.
4.Select the login account to be used during the installation.
5.Right-click the login account and select Properties for this user.
Select Server Roles, and then select dbcreator. For Forcepoint DLP,
Forcepoint Email Security, and Forcepoint Web Security with the Web DLP
6.module, also select sysadmin.
7.Select User Mapping and do the following:
a. Select msdb in database mapping.
b.Grant membership to one of these roles:
SQLAgentUserRole
SQLAgentReader Role
SQLAgentOperator Role
and also to:
db_datareader
Select wbsn-data-security in database
c. mapping and mark it as "db_owner".
Select wbsn-data-security-temp-archive in database mapping and
d.mark it as "db_owner".
e.Click OK to save your changes.
8.Click OK to save your changes.

You might also like