The following are changes in the Oracle Security for Oracle Database Release 19c.

  • Signature-Based Security for LOB Locators
    Starting with this release, you can configure signature-based security for large object (LOB) locators.
  • Default User Accounts Now Schema Only
    Using the schema only account feature from Oracle Database release 18c, most of the Oracle Database supplied schemas (users) now have their passwords removed to prevent users from authenticating to these accounts.
  • Privilege Analysis Now Available in Oracle Database Enterprise Edition
    Privilege analysis is now available as part of Oracle Database Enterprise Edition.
  • Ability to Grant or Revoke Administrative Privileges to and from Schema-Only Accounts
    Administrative privileges such as SYSOPER and SYSBACKUP can now be granted to schema-only (passwordless) accounts.
  • Automatic Support for Both SASL and Non-SASL Active Directory Connections
    Starting with this release, both Simple Authentication and Security Layer (SASL) and Transport Layer Security (TLS) binds are supported for Microsoft Active Directory connections.
  • Support for Oracle Native Encryption and SSL Authentication for Different Users Concurrently
    In previous releases, Oracle Database prevented the use of both Oracle native encryption (also called Advanced Networking Option (ANO) encryption) and Secure Sockets Layer (SSL) authentication together.
  • Ability to Audit Only Top-Level SQL Statements
    The unified auditing top-level statements feature enables you to audit top-level user (or, direct user) activities in the database but without collecting indirect user activity audit data.
  • Improved Read Performance for the Unified Audit Trial
    The AUDSYS.AUD$UNIFIED system table, which stores the unified audit trail records, has been redesigned to use partition pruning to improve read performance.
  • PDB_GUID as Audit Record Field Name for SYSLOG and the Windows Event Viewer
    The audit record fields for SYSLOG and the Windows Event Viewer now have a new field, PDB_GUID, to identify the pluggable database associated with a unified audit trail record

Thank you for giving your valuable time to read the above information.

If you want to be updated with all our articles send us the Invitation or Follow us:

Telegram Channel:

Skant Gupta’s LinkedIn:

Joel Perez’s LinkedIn: Joel Perez’s Profile

LinkedIn Group: Oracle Cloud DBAAS

Facebook Page: OracleHelp

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.