Ask Tom Office Hours: Database Security - Key Features
Why Stack Overflow recommends it
Stack Overflow users link it when explaining Oracle Native Network Encryption versus SSL/TLS wallets for securing database connections.
Recommended by 2 people across 2 different months, 2018 to 2021.
What it is
A 46-minute AskTOM Office Hours session from March 2018 in which Oracle's Russ Lowenthal, Director of Product Management for Security Products, walks through Oracle Database 12.2/18c security features. Topics include Audit Vault, Key Vault, Row Level Security, the Security Assessment Tool, Wallets and Native Network Encryption, with Q&A.
What people said
Recommends Dan McGhan · 2018-12 · Stack Overflow · on “Connecting to Oracle with SSL”
Listen to this conversation regarding Native Network Encryption vs SSL. [this video] Do you really need SSL? For almost everyone, the answer is no...
Recommends Vergil C. · 2021-06 · Stack Overflow · on “How to change protocol for Oracle database connection in ASP.NET Core?”
There are two ways of encrypting SQLNET traffic. Using Wallets/Certificates and network layer (SSL/TLS) Using native Oracle encryption which doesn’t encrypt the network layer, but does encrypt each packet sent along it In my case, we have chosen to go with option 2, as long as you see the ASE256 (which is what the DB server side is requesting) on your response to the query select NETWORK_SERVICE_BANNER from v$session_connect_info where SID = sys_context('USERENV','SID') then I would say you good. You could explicitly configure your connection as is, but in my case I didn't have to, as the oracle server has been configured to require it by default. OracleConfiguration.SqlNetEncryptionClient =
Cites Kankan-0 · 2020-01 · Stack Overflow · on “What's the difference between Oracle Encryption and SSL”
As per the general configuration setup of TLS/SSL, you will have to get a certificate issued for the database. Once you have the certificate, you need to put it into a wallet, and then configure your listener to use the wallet. Also, for all the client who wants to connect to the database you will have to give them the trusted certificate and client setup will have to configured to use the certificate for validation. For native network encryption, you need use a flag in sqlnet.ora to indicate whether you require/accept/reject encrypted connection. In case of server sqlnet.ora, the flag is SQLNET.ENCRYPTION_SERVER , and for client it's SQLNET.ENCRYPTION_CLIENT . Default value of the flag is a