The Omega DB Scanner Standalone edition version 2.0.2 has been released
Introducing Omega DB Scanner Standalone
Omega DB Scanner is a security auditing tool and vulnerability assessment scanner. It has been designed to give the user the automated knowledge in performing the complex task of assessment, evaluation and improvement of the security posture of his mission critical Oracle database. Omega DB Scanner is not just a scanner, but also an inventory of your Oracle database’s security posture. Omega DB Scanner is an out-of-box, software-only solution. As the name implies, this Standalone Free Edition is a simple client-side solution that is deployed on the user’s PC within minutes. Omega DB Scanner is Agent-less and accesses the target database in read-only mode.
New Features/Enhancements in 2.0:
1. Splunk SIEM support highlighted
Delivery of scan records to Splunk is now supported!
This new feature enables user to send scan records to a Splunk system directly from the application! Inside Splunk you can further use our Splunk application Omega DB Scanner App for Splunk. New form “Splunk Upload” is added. New parameters are added in the initialization file and managed in the “System Settings” form.
2. Multiple operations on parameters highlighted
Multiple operations on parameter values and list values allow for quick authorization. New form “Parameter Multiple Operation” is added. This new feature enables user to manipulate the value (and list values) of a parameter in all (chosen) appearances of it through vulnerability controls.
3. List Authorization scan option highlighted
The new List Authorization checkbox option implemented in scan-related forms allows scanning of a single database with parameter configuration/authorization (default mode and edition limitation), but also multiple other databases without configuration/authorization.
4. More scan-related fields added to the scan comparison dataset
Scan-related fields “Control Find Run”, “Control Summary Run”, “Control Find BS” and “Control Summary BS” are added into the Scan Comparison Report dataset, available in the Scan Comparison form. The appearance of these fields casts more light into the item’s scan result decision (represented by existing field “Compare Code”).
5. New initialization parameters for Naming Schema of the Scan name and filename
New parameters added in the initialization file and managed in the “System Settings”, controlling saved scan filename format, previously hard-coded in application.
6. Changed access path to “Configurations Import” form
Form is now accessed from the “All Configurations” form, button on the top-right “Configuration Import”.
7. Use Case and demo highlighted
Use case added in this document to illustrate in practice the features of the software. Use case XML scans files provided as a demo and included in the distribution.
Bug fixes in 2.0:
The following bugs (present in 1.8.1) are fixed in 2.0:
Table “All Configurations” in the form with the same name allowed modification of field values and records. All fields set to read-only and grid disallows insert and delete.