PROTECTING ORACLE PL/SQL SOURCE CODE FROM A DBA USER

PROTECTING ORACLE PL/SQL SOURCE CODE FROM A DBA USER

1. ORACLE SECURITY DATABASE

   • The intention of this section is to give a basic idea of the security features of Oracle relational database management system.
     • Oracle authentication allows the different types of authentication. Oracle allows authentication based on the accounts of the Oracle database with user IDs and passwords that are encrypted with an algorithm DES modified for each connection to the database. Oracle passwords are stored in a format that is encrypted in the data dictionary
     • Profiles of Oracle makes use of profiles to allow the database administrator to implement specific restrictions, rules and controls a number of system resources, use password life and various Oracle products. These profiles can be name, define and assign specific users or user groups
     • Privileges by default, Oracle relational database management system does not give any kind of privileges to new users. New users must have privileges before you have connection to the database and to accomplish any international Bases management systems magazine database
     • Functions are used to make easier the process of assignment of privileges to users. Functions is created first and then give different privileges for objects and system that can be assigned to users.
     • the protection of data integrity Oracle relational database management system provides several features to ensure the integrity of the data in different cases, failure of the system, human error, or attacks. These features include the redo, log files segments of reversion and LogMiner.

2. PL/SQL SOURCE CODE BLOCKS AND WRAPPING PROCESS

   • Language of procedure/SQL PL/SQL extends SQL by adding constructions in languages of procedure, resulting in a structural language that is more powerful than SQL. The basic unit in PL/SQL is a block
     • wrapping is the process of hiding PL/SQL source code. It helps developers of sheath to protect the source code for any user who can benefit or could abuse her. Wrap a package causes that code is has obfuscated, i.e. made illegible by programmers, what code do not can be easily stolen, or through the weaknesses of hackers to exploit, which protects the intellectual property of the programming.
       • The limitations of the wrapper wrapping process is not recommended for hiding passwords or table names because it is not a secure method. This process prevents the majority of users browse the source code of a PL/SQL, but could not stop all of them.
     • Process to develop the old versions of Oracle we can easily deduce the original source of the PL/SQL package of the wrapped code produced. The symbol table is visible, so that we can understand the purpose of the procedures (because we can see the names of the variables in the symbol table), we can find encryption algorithms used. Also you can modify the source code directly working with the code.

3. PROTECT ANY USER PL/SQL OBJECTS BY DISABLING DML/DDL

   • To protect a PL/SQL To PL/SQL protect objects is necessary to disable DDL statements like create, replace and someDML statements oriented to the static data dictionary views * _SOURCE. To prevent execution ofany DML/DDL statements on some object we must monitor every user session and analyze everySQL statements before their execution.