Introduce el texto aquíPROTECTING ORACLE PL/SQL SOURCE CODE FROM A DBA USER

Introduce el texto aquíPROTECTING ORACLE PL/SQL SOURCE CODE FROM A DBA USER

1. ORACLE DATABASE SECURITY

   • Authentication
     • Through
       • Accounts
         • Whit
           • User-id
           • password
             • unique
   • Profiles
     • Have
       • Restrictions
       • Rules
     • These can be
       • Named
       • defined
       • Assigned
         • Groups of users
         • specific user
     • are two types of profiles
       • System resource profiles
         • used
           • put user limits on
             • certain system resources such as memory
             • CPU time
             • the number of data blocks
               • can be read per session
             • the number of concurrent active sessions
             • and the maximum connection time for a user
       • Product profiles
         • administrator
           • prevent
             • user access to the operating system
             • unauthorized copying of data from one table to another
   • Privileges
     • the new users
       • Don`t have this privileges
       • to have this priviliges
         • they must have before
           • create database conection
   • Roles
     • Used
       • to make easy
         • the management process
           • of assigning privileges
             • to users
   • Protecting Data Integrity
     • ensure
       • information
         • persist
           • despite damage

2. PL/SQL SOURCE CODE BLOCKS AND WRAPPING PROCESS

   • Benefits from pl/sql objects (procedure, function, trigger and package) stored in database
     • Overhead
       • stored statements
         • are stored directly in the database
           • they may remove all
       • compilation overhead
         • required in situations
           • where software applications
             • send inline SQL statements
               • to a database
     • Avoidance of network traffic
       • they can run directly within the database engine
       • In a production system
         • the procedures run entirely
           • on a specialized database server
             • which has
               • direct access to the data being accessed
     • Encapsulation of business logic
       • software developers
         • to embed business logic
           • in the database
     • Delegation of access-rights
       • can be granted access rights
         • to the database
     • Protection from SQL injection attacks
       • can be used to protect
         • against injection attacks
   • A Model of Data Warehousing Process Maturity
     • is the process
       • of hiding PL/SQL
         • source code

3. 4.PROTECTING PL/SQL OBJECTS BY DISABLING DML/DDL STATEMENTS TO ANY USER

   • is necessary
     • to disable DDL statements like
       • replace and some DML statements
         • oriented
           • to the static data dictionary views

4. CONCLUSIONS & FUTURE WORK

   • stop execution of DDL statements oriented to the static data dictionary views
     • modified in future to allow execution of DML statements oriented to the static data dictionary views