New Features
This release provides new features and improvements to DbProtect.- DbProtect 6.7.2
- Added a new DISA-STIG - CheckID mapping .csv report
- Added Job Comparison report
- Numerous report fixes and improvements
- The bundled Scan Engine component is upgraded to v3.26 and includes the following updates:
- Added support for Oracle26ai Database targets (this will require KB 6.66)
- Updated timeout settings for target connections, improving result accuracy
- Updated bundled .NET 8 redistributable and 3rd party libraries to latest versions
- Re-branded ScanEngine installer to LevelBlue and changed default install location to %ProgramFiles%\LevelBlue
Configuration Customizations
Any changes to service configuration files, like default logging levels, memory allocation settings, etc., are overwritten with default values during a system upgrade. If you edit any configuration files as part of your use, you will need to re-edit the corresponding configuration files following any DbProtect upgrade. Do not attempt to re-use a configuration file from an earlier version of the product as new features and fixes may have required additions to these files.Direct Upgrade Support
See Known issues for additional installation/upgrade considerations. The policy and features for the Gateway mode offering differ from the policy and features for the Integrated (M365 sending) mode. Integrated mode customers should refer to the document for that mode.
1
Uninstall Explorer
Uninstall Explorer using the Windows Programs and Features control panel. Right-click on the DbProtect Explorer component and select Uninstall. The uninstall process may prompt you to allow it to automatically close several applications. Permit this and then complete the uninstallation procedure.
2
Unregister Linux Scan Engines
Unregister all Linux Scan Engines prior to upgrading core.
3
Upgrade Scan Engines
Upgrade Windows Scan Engines and re-install Linux Scan Engines (see the Scan Engine Host section below).
4
Update the SHATTER KB
Update all Scan Engines with the latest SHATTER KB from the core console UI.
5
Upgrade core
Complete the core upgrade process using the DbProtect v6.7.1 installer. The Explorer installer wizard will appear once the core portion of the upgrade is complete.
6
Install Explorer
Proceed through the Explorer installation steps as usual. When the installation is complete, use the Windows Services manager to verify that all DbProtect services are running.
Supported Operating Systems
DbProtect v6.7.2 can be installed on the following operating systems:- Microsoft Windows Server 2016
- Microsoft Windows Server 2019
- Microsoft Windows Server 2022
- Microsoft Windows Server 2025
Supported Backend Databases
DbProtect v6.7.2 can use the following databases as its backend repository:- Microsoft SQL Server 2017 (Windows only)
- Microsoft SQL Server 2019 (Windows only)
- Microsoft SQL Server 2022 (Windows only)
- Microsoft SQL Server 2025 (Windows only)
The use of Extended Protection or Microsoft SQL Server Express is not supported.
Scan Engine Host
The DbProtect v6.7.2 release includes an updated Scan Engine Host v3.26 component. Installers for both Windows and Linux are available. Refer to the DbProtect v6.7.2 Installation and Upgrade Guide for specific details on deploying the new v3.26 Scan Engine Host.- As of Scan Engine Host v3.24, open inbound ports to the scan engine host are no longer required.
- This change enables a Scan Engine Host to be installed in a network isolated from the console as long as the hostname is resolvable. Hostname resolution is required in both directions for certificate-based authorization to be successful.
- Some database platforms may now require updated 64-bit Client Drivers for scans to function properly.
- Scan Engine Host v3.26 is only supported with DbProtect v6.7.2. It is not intended to be used with DbProtect v6.7.1 or earlier.
- Windows Scan Engine Host versions prior to v3.25 are not supported with DbProtect v6.7.2. Any such installations must be upgraded to v3.26 before using DbProtect v6.7.2. It is recommended to upgrade all Scan Engine Hosts to v3.26.
- Linux Scan Engine Host versions prior to v3.26 are not supported with DbProtect v6.7.2. Any installations must be unregistered and then replaced with v3.26 before using DbProtect v6.7.2.
- New installations of Scan Engine Host v3.26 will install the newer version of Nmap (v7.99) for Discovery-related functionality. Existing Nmap installations can update to a newer version of Nmap outside of the DbProtect application suite.
Scan Engine Manager
DbProtect v6.7.2 includes a component called Scan Engine Manager v3.26. It replaces previous versions of Scan Engine Manager, or the previously used Scan Engine Proxy that shipped with DbProtect v6.6.13. This new component has major benefits both in routing and performance. Below are some critical requirements for a successful deployment:- Scan Engine Manager, or the console host, now requires an inbound port from each Scan Engine Host (default is
28080). - Hostname resolution is required in both directions for registration to be successful.
- If installed, and upgrading from DbProtect 6.6.x, unregister all Linux Scan Engines before upgrading the console to DbProtect v6.7.2.
Future SHATTER Knowledgebase Updates
Subsequent SHATTER Knowledgebase versions are installed at the DbProtect application server and then pushed out to each scanner. This installation includes the most current version of the SHATTER Knowledgebase, and does not require additional updates at the time of publication of this document.Runtime Service Users
All runtime service users provided at the time of installation must be the same when provided to each component installer of the suite installation. In the case of an upgrade, the runtime service user must be the same as that which was used during the prior installation. This does not apply to scanners and sensors.Resolved Issues
The following issues were investigated and resolved in this release of DbProtect v6.7.2:- Resolved an issue whereby sometimes compliance benchmarks to asset mappings were not properly updated after ShatterKB updates.
- Resolved an issue causing deleted job reports to continue to appear.
- Asset name and details now properly included in DISA STIG reports.
- Resolved an issue causing generation of Finding Details or Check Results Details PDF Reports to sometimes fail.
- An issue causing text filtering in some Explorer search text box (e.g., Checks section) to not function has been fixed.
- An issue causing the Sensor Policy Severity field value to revert back to its default value if it had previously been modified but then unchecked has been resolved.
- An issue causing the Executive Summary report to show incorrect alert counts has been addressed.
- An issue causing some data to be missing from PDF or HTML versions of the License Utilization report has been fixed.
- Fixed an issue causing cloned policy report results to differ from those that are built-in.
- Resolved an issue causing Informational counts in the Risk Distribution report to be incorrect.
- Asset Detail reports may have sometimes been missing the ‘Last Scanned’ data. This has been addressed.
- Various included third-party libraries and frameworks have been updated to newer versions.
Known Issues
This section contains information about the known issues in DbProtect.General
- Integrated Windows Authentication is an insecure method of connectivity to targets and therefore is no longer supported.
- Scan Engine Manager defaults to
C:\Program Files. It is recommended to change the installation path to your current DbProtect root directory (ie.,d:\trustwave\dbprotect\scan engine manager). Installing it outside this path may result in file system permission issues. - Scan Engine Host defaults to
C:\Program Files(since it is now 64-bit) for a new installation on Windows. If you had a prior 32-bit version installed, an upgrade will place this in the prior location. If this location wasc:\Program Files (x86), that is where it will upgrade even though it is no longer 32-bit. - If the console host has two enabled network interfaces, Scan Engines may attempt to communicate on the wrong inbound interface. Contact Support if you have more than one network interface on your console for further instructions.
- When your explorer session times out you are not redirected to the login page. Cancel the pop-up auth if you get one and navigate back to the main Explorer page to login again.
- When IPv6 is enabled on a host and set as preferred there may be issues with connectivity between the Scan Engine Host and the Scan Engine Manager. If you experience this contact Support for further assistance.
- Previously created SAP Hana assets will remain unscannable after upgrading. If you wish to use these prior assets contact Support for instructions.
- Credential Tests from the Asset screen do not function for CyberArk Vault credentials. Use a Credential Test Job instead to validate these prior to Audits.
- In certain cases, the DbProtect uninstallation process may fail. Please contact support if you need assistance with this.
- If executed with incorrect credentials, the audit status icon for credential test results may display as a question mark rather than a red cross mark.
- When installing or launching DbProtect on a newer operating system such as Microsoft Windows Server 2022, you may receive a Microsoft Defender popup indicating that
DbProtect.exewas blocked from running due to having an Unknown publisher. You can choose Run anyway to proceed. - When trying to sort by Alert ID on the Monitoring Alerts tab, you may sometimes receive an error stating “the page you requested doesn’t exist”. For sorting and Searching capabilities, go to Explorer Management Alerts instead.
- Explorer policy lens filter for DISA-STIG and CIS policies may not display results properly. Instead, switch to the “None” filter.
- Deleting credentials from a Shared Credential Group may results in DbProtect generating an Error. Editing and Saving credentials are unaffected.
- In some cases, Oracle pen test checks may fail depending on the Oracle CPU patch set applied.
- SMB Current Content Authentication is not supported.
- After upgrading to DbProtect v6.7.2 you may be unable to register a Sensor. Contact LevelBlue Support for help with this issue.
Reports
- Knowledgebase report is showing incorrect risk values