Softpedia >Windows >Internet >Servers >Database Utils >Omega Core Audit >  Changelog

Omega Core Audit Changelog

What's new in Omega Core Audit 3.3.5

May 7, 2023
  • New in 3.3.5:
  • Integration with Graylog highlighted.
  • This version introduces integration with Graylog in Push mode. It features the automated delivery of audited
  • events to Graylog SIEM through direct TCP connection and record input, using a JSON core-to-core (Oracle-
  • Graylog) solution with no need for any third party. Inside Graylog the support is further extended by our next
  • solution Omega Core Audit Content Pack for Graylog.
  • RTP-DML rule Copy.
  • Functionality to copy a RTP-DML Rule within the same RTP-DML policy is available.
  • Increased length of RTP-DDL Area Operand
  • Length of this field is increased to satisfy longer IN/NOT IN lists.
  • Limit introduced on list of form “Extra Options – App Schemas”
  • A maximum limit of 200 entries is introduced to safeguard from eventual errors of exceeding internal variables
  • length.
  • Fixes in 3.3.5:
  • Change of Password for all Omega Core Audit roles.
  • Ability to change its own password was limited only to members of Omega CA Administrator and Omega CA
  • Account Manager roles. It is added also to members of Omega CA Audit and Omega CA Security Analyst roles
  • Remaining value of Last Operand in (NOT IN) IN Lists
  • In case of an empty grid – compiling of a new list – the value of the last Operand was left on the Edit Box of the
  • Update part; fixed in this version, on respective forms of Access Control, RTP-DDL and RTP-DML policies.
  • Events on objects of Omega Core Audit repository not marked in SEO field SEO_SEC for RTP-DML events
  • RTP-DML events are now marked by SEO field SEO_SEC for actions on Omega Core Audit objects

New in Omega Core Audit 3.3.4 (Feb 17, 2023)

  • Spunk built-in interface fixes.

New in Omega Core Audit 3.3.3 (Jan 3, 2022)

  • New in 3.3.3:
  • New Oracle dictionary objects marked for SEO Security field highlighted. Important Oracle Dictionary objects have been added for marking the Search Extra Options Security field. These are the Oracle tables and views that contain and present audit, privileges, profiles, users, and roles information.
  • Oracle instant client OCI files 12c R2 used for connection highlighted. Oracle Connectivity (OCI client) libraries are upgraded to version 12c R2. Details are given on Omega Core Audit Deployment guide.
  • IN and NOT IN operators used for non-advanced search options IN and NOT IN operators are implemented in Search Options for fields Username to Return Code
  • Fixes in 3.3.3:
  • SEO function called in Access Control Trail insert:
  • A default 0 value was inserted in the prior version for Search Extra Option Error on Access Control trail. Calling the right function inside the engine package ensures right value in case of access deny from Access Control Module

New in Omega Core Audit 3.3.1 (Jun 21, 2021)

  • New Features/Enhancements/Changes in 3.3.1:
  • New Chart Events by Object Type added to Security Events Trail.
  • Issues and Fixes in 3.3.1:
  • Chart Events by Object Name removed from Security Events Trail form.
  • A possible big number(thousands)of values in the Events by Object Name chart will eventuallycause a program crash. The replacement with the chart above conforms to the summary presentation meant in these charts

New in Omega Core Audit 3.3.0 (Nov 13, 2020)

  • When a rule condition with an IN/NOT IN Operator used in Access Control, Real-Time Protection DDL and DML contains a long list Operands (behavior verified for 70+, but it depends on the length of each entry), the Omega Core Audit operations will internally fail with the error “ORA-06502: PL/SQL: numeric or value error: character string buffer too small”.Fixes in Omega Core Audit Engine Package have been made extending the necessary variable’s string length to the maximum available.Although this pushes the usage of list entries to a further limit, it cannot go unchecked, as at some point the new limit will be also reached.

New in Omega Core Audit 3.2.0 (Jun 12, 2020)

  • New Features/Enhancements/Changes:
  • Coexistence with SIEM for Dictionary Audit Trailshighlighted. So far the sole mode of collecting audit trails from Oracle dictionary tables SYS.AUD$ and SYS.FGA_LOG$ was of a Purge-like kind, in the sense that the record successfully collected is immediately cleaned from the Dictionary. This approach, while being best suited to Omega Core Audit itself, prevents other external log systems (ex SIEMs) from collecting audit records –as they do –from Oracle Dictionary tables. To fix this another Pull-only mode has been developed in collecting audit records, which will not delete the successfully transferred audit record from the Oracle dictionary –leaving it there for the third party system to collect
  • Saved Searches for Unified Trailhighlighted.It is now possible to persist and reuse Search configurations in form Unified Audit Trail.
  • Full ErrorStackhighlighted.Extra debug information (exact unit’s failing line) on eventual program errors.
  • Oracle Audit Default –restriction liftedCREATES SESSION allowed
  • Graphic –Layout improvedForms background common gray color softened. Excessive use of bold for labels and fields fixed.
  • Editions renaminghighlighted.Basic -> StandardFull -> Professional