DbProtect Console

installation
Rollout Strategy
Location of components
Console
Backend (MS SQL)
Scan Engine
Sensors

Logistic
Firewalls
SQL default ports
Types of database in-scope
Install Planning - Prerequisites
DbProtect Service Account

DbProtect Data DbProtect DbProtect

repository Console: Scan Engine:
MS SQL Server: Local Admin Local Admin
Sysadmin Log on as a Log on as a
Local Admin service service

Trusted Domain “Service Account”

e.g. \DOMAIN\DbProtect
Install Planning - Prerequisites (1 of 2)

Install as and run as accounts (console)

Install as – local administrator account
Run as – access to the OS, Backend SQL, Directory structure

Client Drivers (VA)

MySQL
IBM DB2 LUW
SAP (Sybase) ASE (Data Server)
PostgreSQL
Teradata
other
Install planning - Prerequisites (2 of 2)

User account (Scan engine)

Install as – local administrator account
Run as – access to the OS, Backend SQL, Directory structure
Client Drivers (VA)
– MySQL
– IBM DB2 LUW
– SAP (Sybase) ASE (Data Server)
– PostgreSQL
– Teradata

User accounts (sensor)

Run as – access to the target DB
Overview of the install

DbProtect console
Console requirements
– Consult manual
All Modules are installed
– Vulnerability Management
– Rights Management
– Activity Monitoring
– Shared components (Active Analytics)
Backend Repository (MS SQL) can be installed on the Same server or different server (production should be on
two different servers)
Verify which port the Backend SQL server is configure to access
– Default is 1433
Overview of the Install - Licenses

Licenses –
ARxxxxxxx.lic - Console and Activity Monitoring
ADxxxxxxx.lic - Vulnerability Management and Rights Management
Files contain licensed units and software and maintenance expiration date
Console Install

Installer
Will verify the if any additional software is required (.NetX.X, …)
If the additional software requires a reboot the install will continue after the server is restarted
Each component will prompt for required information
– Backend SQL Server
– Install credentials
– Run As credentials
– Ports for the console to connect to
Install will continue until all the console components are installed
Need to make sure you place both the licenses in the correct directory
Scan Engine installation
Overview of the Scan Engine installation

SCAN Engine
Need both the installs as and run as accounts
See Manual for specific OS and Database rights
Verify that there is a connection from the console to the SCAN Engine servers
Client Drivers (VA) installed on scan engine box
– MySQL
– IBM DB2 LUW
– SAP (Sybase) ASE (Data Server)
– PostgreSQL
– Teradata
Scan engine Target Server

Install the software

Does not store data locally

Component Minimum Requirement Recommendation

Processor • 2 GHz multiple cores 8 cores

Memory • 8 GB 16 GB

Operating System • Windows Server 2008 SP2, 2008 R2 SP1, or Windows 2012 64-bit

Disk Drive Space • 50 GB of free space available.

Default Port • 20001