arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 1209.2794cs.DB
收藏

保护dba用户访问oracle pl/sql source code

Protecting oracle pl/sql source code from a dba user

Hakik Paci, Elinda Kajo Mece, Aleksander Xhuvani

摘要:

在本文中,我们提出了一种新的方法来禁用某些特定的PL/SQL过程的dba用户在Oracle数据库中的SQL语句。如今,dba用户可以访问大量的数据和源代码,即使他们没有查看或修改它们的合法权限。使用此方法,我们可以禁用每个Oracle数据库用户对某些特定pl/sql过程执行SQL和DML语句的能力,即使它具有dba角色。Oracle为开发人员提供了包装pl/sql过程、函数和包的可能性,但这些包装的脚本可以通过使用第三方工具来解包。我们开发的脚本会分析所有数据库会话,如果它们检测到来自未授权用户的DML或SQL语句,则会拒绝执行该语句。此外,这些脚本不允许dba用户删除或禁用脚本本身。换句话说,通过在执行来自dba用户的eventual语句之前管理会话,我们可以防止执行以我们的脚本为目标的eventual语句。

英文摘要:

In this paper we are presenting a new way to disable DDL statements on some specific PL/SQL procedures to a dba user in the Oracle database. Nowadays dba users have access to a lot of data and source code even if they do not have legal permissions to see or modify them. With this method we can disable the ability to execute DDL and DML statements on some specific pl/sql procedures from every Oracle database user even if it has a dba role. Oracle gives to developer the possibility to wrap the pl/sql procedures, functions and packages but those wrapped scripts can be unwrapped by using third party tools. The scripts that we have developed analyzes all database sessions, and if they detect a DML or a DDL statement from an unauthorized user to procedure, function or package which should be protected then the execution of the statement is denied. Furthermore, these scripts do not allow a dba user to drop or disable the scripts themselves. In other words by managing sessions prior to the execution of an eventual statement from a dba user, we can prevent the execution of eventual statements which target our scripts.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑