Technical Articles ID:
KB73919
Last Modified: 2024-05-09 08:07:25 Etc/GMT
Environment
Trellix Database Security (DBSec) 10.x
Database Activity Monitoring (DAM) Server 4.x
Vulnerability Manager for Databases (DVM) 4.x
NOTE: Trellix Database Activity Monitoring (DAM) has been rebranded to Trellix Database Security in version 10.x.
Summary
When Microsoft releases new operating systems or Service Packs, the original DBSec product guides might not reflect the current support policy for those platforms. Most of the following information is available in the product installation guides and release notes. But, some of the information is available only in Product Management statements published in the Knowledge Base.
Recent updates to this article
Date
Update
May 9, 2024
Updated the "Supported operating systems" table.
April 3, 2024
Updated Release Information.
March 28, 2024
Added support for Oracle MSSQL, MySQL, and PostgreSQL Databases on Windows and Linux OS.
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
DBSec
Our product software, upgrades, maintenance releases, and documentation are available on the Product Downloads site.
Type your Grant Number and Email Address, and then click Submit.
Go to McAfee Database Security – Standalone version 4.8
Download 4.8.x DAM supported databases.
DBSec supports running the DBSec server in clusters to provide high availability and performance.
The DBSec Sizing Guide for use with the Standalone Management Server provides some capacity and planning guidelines. See the DBSec - Sizing Guide - Standalone Version PDF available for download from the Product Downloads site:
Type your Grant Number and Email Address, and then click Submit.
Go to Trellix Database Security – Standalone version 10.0.
Download the Database Security - Sizing Guide - Standalone Version.
Oracle 18 and 19 support:
DBSec - Minimum Supported Version (Memory and Network monitoring)
Platform\Oracle version
Oracle 19c
Oracle 19c AMM
Oracle 18c
Oracle 18c AMM
Windows
4.7.0
4.8.0
4.6.6 Update 4
4.8.0
Linux
4.7.0
4.8.0
4.6.6 Update 4
4.8.0
AIX
4.7.0
4.8.0
4.6.6 Update 4
4.8.0
HP-UX
4.7.0
4.8.0
4.6.6 Update 4
4.8.0
Solaris Intel
4.8.0
4.8.0
4.6.6 Update 4
4.8.0
IMPORTANT: AMM is only supported for the platforms listed above. AMM is not supported on Solaris Sparc x86_64.
DBSec Oracle 18 and 19 support for Solaris SPARC:
Platform\Oracle version
Oracle 19c
Oracle 18c
Memory monitoring
Network monitoring
Memory monitoring
Network monitoring
Solaris SPARC 10 (pre-S7 architecture)
Not supported by Oracle
Not supported by Oracle
4.6.6 Update 4
4.6.6 Update 4
Solaris SPARC 11 (S7 and above)
Not supported
4.8.0
Not supported
4.8.0
Solaris SPARC 11 (pre-S7 architecture)
Not supported
Not supported
Not supported
Not supported
NOTE: Only network monitoring is supported for Oracle (all versions) on Oracle Solaris Sparc 11 with S7/M7 or later processors. Memory monitoring isn't supported in such an environment.
Database versions with support discontinued in 4.8.6 and later
Name
Discontinued support from 4.8.2 onward
Teradata
All versions of Teradata
Database versions with support discontinued in 4.8.2 and later
Name
Discontinued support from 4.8.2 onward
MSSQL
All versions of Microsoft SQL Server 2008
Postgres
Postgres 9.3.x
Postgres 9.2.x
Database versions with support discontinued in 4.8.1 and later
Name
Discontinued support from 4.8.1 onward
MSSQL
MSSQL 2005
Oracle
Oracle 11.1
Oracle 10.x
Oracle 9.x
Oracle 8.x
MySQL
MySQL 5.5
MySQL 5.1
Sybase
Sybase ASE 15.5
Sybase ASE 15.0.x
Sybase ASE 12.5.x
DB2
DB2 9.x
DB2 8.x
Browser requirements
10.x
4.7, 5.2, 5.3
4.8
Firefox
Chrome 123.0 or later
MS Edge 122.0 or later
Firefox 2.0 or later
Internet Explorer 7.0 and later
Chrome
Firefox 53 or later
Chrome 56 or later
Internet Explorer 11
Space and memory requirements
4.7, 5.2, 5.3
4.8, 10.x
DAM server space requirements:
Software binaries size: 160 MB
Initial empty Database size: 35 KB
Average Database size with 100,000 alerts: 300 MB
Archive file size for 100,000 alerts: 11 MB
NOTE: The internal database size doesn't shrink immediately after archive. It shrinks only when it hits an internal threshold.
Internal Database - Minimum recommended space to allocate for internal database: 2 GB
Server Logs - Minimum recommended space to allocate for server logs: 100 MB
Server Working Files - Recommended space for server working files (updates, archive, and temporary files): 2 GB
Overall minimum free space recommended to install DAM Server: 5 GB
DAM / DBSec server space requirements:
Software binaries size: 300 MB
Initial empty Database size: 1 MB
Average Database size with 100,000 alerts: 200 MB
Archive file size for 100,000 alerts: 5 MB
NOTE: The internal database size doesn't shrink immediately after archive. It shrinks only when it hits an internal threshold.
Internal Database - Minimum recommended space to allocate for internal database: 5 GB
Server Logs - Minimum recommended space to allocate for server logs: 100 MB
Server Working Files - Recommended space for server working files (updates, archive, and temporary files): 2 GB
Overall minimum free space recommended to install DAM Server: 1 GB
DAM server memory requirements:
Running in 32-bit mode:
Minimum free memory needed for DAM Server: 512 MB
Recommended free memory in production environment: 2 GB
Running in 64-bit mode:
Minimum free memory needed for DAM Server: 1.5 GB
Recommended free memory in production environment: 4 GB
DAM / DBSec server memory requirements:
Minimum free memory needed for DAM Server: 8 GB
Recommended free memory in production environment: 16 GB
DAM Content Releases (vPatch):
DBSec provides enhanced DBMS security based on vPatch monitoring rules. vPatch monitoring rules help prevent attacks against known vulnerabilities such as SQL injections.
Currently, vPatch monitoring rules released by the DBSec product help address many known vulnerabilities of CVE score 9.0 and greater wherever these CVEs are directly related to the DBMS. This fact excludes the system, operating system, Java, and other non-DBMS-specific CVEs.