How to Restrict Access to the Database With Specific Tools (e.g. TOAD) or Applications (Doc ID 281229.1)

Last updated on SEPTEMBER 22, 2023

Applies to:

Purpose

This bulletin explains how to prohibit users from connecting to a database when using predefined applications, thus accessing the application tables directly
with (third party) tools such as ODBC / JDBC clients, TOAD or even Sql*Plus.

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Scope

DBAs who have to secure access to the database data through different applications.

WARNING : You basically have no control over the client and hence everything
that comes from the client cannot be trusted. The methods described here may therefore
not be suitable to enforce a full security. Regard it as implementing business rules
rather than a fully secure method of enforcing them. Real security can and must be
enforced on the database only.

Basically the issue is that the database can authenticate users only, not client applications.

This article provides a specific example banning TOAD for NON DBA users.

Details