Results for security


1 to 60 of 4163 results. Prev  Next
Results per page:   20  | 40 | 60


Database Security Guide, 11g Release 1 (11.1)

Database Security Guide - Contents

ContentsDocumentation Accessibility Related Documents Conventions What's New in Oracle Database Security … Network Services on the Database Change to AUDIT BY SESSION Oracle XML DB Security Enhancements … Directory Security Enhancements Oracle Call Interface Security Enhancements 1 Introducing Oracle Database … Security

Label Security Administrator's Guide, 11g Release 1 (11.1)

Label Security Administrator's Guide - Contents

ContentsAccessibility Related Documentation Conventions Part I 1 Introduction to Oracle Label Security 1.1 … Computer Security and Data Access Controls 1.1.1 Oracle Label Security and Security Standards 1.1.2 … Security Policies 1.1.3 Access Control 1.1.3.1 Discretionary Access Control 1.1.3.2 Oracle Label Security

Database Administrator's Guide, 11g Release 1 (11.1)

Types of Oracle Database Users

Security OfficersIn some cases, a site assigns one or more security officers to a database. A security officer … enrolls users, controls and monitors user access to the database, and maintains system security. As a DBA … , you might not be responsible for these duties if your site has a separate security officer. Please … refer

Database PL/SQL Language Reference, 11g Release 1 (11.1)

Overview of PL/SQL

Tight SecurityPL/SQL stored subprograms move application code from the client to the server, where you can protect it from tampering, hide the internal details, and restrict who has access. For example, you can grant users access to a subprogram that updates a table, but not grant them access to the table itself or to the text of the UPDATE statement. Triggers written in PL/SQL can control or record changes to

Database Concepts, 11g Release 1 (11.1)

Business Intelligence

Securityserver, load and rebuild the cube. The administrator must take responsibility for the security of the … intervals, and Oracle Database takes care of everything else. Security

Database Administrator's Guide, 11g Release 1 (11.1)

Considerations After Creating a Database

Some Security ConsiderationsIn this release of Oracle Database, several enhancements were made to ensure the security your … database. You can find security guidelines for this release in Oracle Database Security Guide. Oracle … how to do this, please refer to Oracle Database Enterprise User Security Administrator's Guide. A … accounts.

Database Administrator's Guide, 11g Release 1 (11.1)

Distributed Database Administration

Distributed Database SecurityThe database supports all of the security features that are available with a non-distributed … Management Data Encryption See Also: Oracle Database Advanced Security Administrator's Guide for more information about external authentication

Database Administrator's Guide, 11g Release 1 (11.1)

Monitoring and Managing the Scheduler

Managing Scheduler SecurityManaging Sched uler Security You should grant the CREATE JOB system privilege to regular users who … . A particularly important issue from a security point of view is handling external jobs. Only users … . Security for the Scheduler has no other special requirements. See Oracle Database Security Guide … for details

Database SQL Language Reference, 11g Release 1 (11.1)

Datatype Comparison Rules

Security Considerations for Data Conversioncan have a negative impact on database security when conversion without an explicit format model is … avoiding this security risk Note: This security risk also applies to middle-tier applications that

Database Installation Guide for Linux, 11g Release 1 (11.1)

Installing Oracle Database

3.4 Database Security OptionsDuring installation, you are prompted to select a database security configuration. The Secure … security controls, then you can check the Disable security settings box. Oracle Database is then … security settings by starting Database Configuration Assistant and modifying security settings. You can

Database Administrator's Guide, 11g Release 1 (11.1)

About Database Administrator Security and Privileges

About Database Administrator Security and PrivilegesTo perform the administrative tasks of an Oracle Database DBA, you need specific privileges within the database and possibly in the operating system of the server on which the database runs. Access to a database administrator's account should be tightly controlled. This section contains the following topics: The Database Administrator's Operating System Account Administrative User Accounts

OLAP User's Guide, 11g Release 1 (11.1)

Overview

SecurityWith Oracle OLAP, standard Oracle Database security features are used to secure your … multidimensional data. In contrast, with a stand-alone OLAP server, administrators must manage security twice … manage the security of data in transit from the relational system to the stand-alone OLAP system.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RESOURCE_MANAGER

Security ModelThe invoker must have the ADMINISTER_RESOURCE_MANAGER system privilege to execute these procedures. The procedures to grant and revoke this privilege are in the package Chapter 106, \"DBMS_RESOURCE_MANAGER_PRIVS\".

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOCK

Security ModelThere might be operating system-specific limits on the maximum number of total locks available. This must be considered when using locks or making this package available to other users. Consider granting the EXECUTE privilege only to specific users or roles. A better alternative would be to create a cover package limiting the number of locks used and grant EXECUTE privilege to specific users. An example

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_LMS

Security ModelThis package must be created as the user SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_TRACE

Security ModelThis package must be created under SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SQLTUNE

Security ModelThis package is available to PUBLIC and performs its own security checking: As the SQL Tuning

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SQLPA

Security ModelThis package is available to PUBLIC and performs its own security checking. All analysis task

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_TTS

Security ModelOnly users having the execute_catalog_role can execute this procedure. This role is initially only assigned to user SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_PIPE

Security ModelSecurity can be achieved by use of GRANT EXECUTE on the DBMS_PIPE package by creating a pipe using … particular features or pipenames to particular users or roles. Depending upon your security

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOGMNR

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOGMNR_D

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_LOGMNR_D package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_EPG

Security ModelThe XDBADMIN role is required to invoke the configuration interface. It may invoked by the database user \" XDB \". The authorization interface can be invoked by any user.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_XPLAN

Security ModelThis package runs with the privileges of the calling user, not the package owner ( SYS ). The table function DISPLAY_CURSOR requires to have select privileges on the following fixed views: V$SQL_PLAN, V$SESSION and V$SQL_PLAN_STATISTICS_ALL. Using the DISPLAY_AWR Function requires the user to have SELECT privileges on DBA_HIST_SQL_PLAN, DBA_HIST_SQLTEXT, and V$DATABASE. Using the DISPLAY_SQLSET Function

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DESCRIBE

Security ModelThis package is available to PUBLIC and performs its own security checking based on the schema object being described.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LOB

Security Modeland the Oracle Database SQL Language Reference. For information about the security model pertaining to temporary LOB s, see Operational Notes.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RULE_ADM

Security ModelUser group PUBLIC is granted EXECUTE privilege on this package. See Also: Oracle Database Security Guide for more information about user group PUBLIC

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_HM

Security ModelUsers must have EXECUTE privilege to run the procedures of DBMS_HM package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SPACE_ADMIN

Security ModelThis package runs with SYS privileges; therefore, any user who has privilege to execute the package can manipulate the bitmaps.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_REF

Security ModelThe procedural option is needed to use this package. This package must be created under SYS (connect/as sysdba). Operations provided by this package are performed under the current calling user, not under the package owner SYS. You can use the UTL_REF package from stored PL/SQL procedures/packages on the server, as well as from client/side PL/SQL code. When invoked from PL/SQL procedures/packages

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_OUTPUT

Security ModelThe dbmsotpt.sql script must be run as user SYS. This creates the public synonym DBMS_OUTPUT, and EXECUTE permission on this package is granted to public.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_OBFUSCATION_TOOLKIT

Security ModelOracle installs this package in the SYS schema. You can then grant package access to existing users and roles as needed. The package also grants access to the PUBLIC role so no explicit grant needs to be done.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CQ_NOTIFICATION

Security ModelThe DBMS_CQ_NOTIFICATION package requires that the user have the CHANGE NOTIFICATION system privilege in order to receive notifications, and be granted EXECUTE privilege on the DBMS_CQ_NOTIFICATION package. In addition the user is required to have SELECT privileges on all objects to be registered. Note that if the SELECT privilege on an object was granted at the time of registration creation but lost

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RANDOM

Security ModelThis package should be installed as SYS. By default, the package is initialized with the current user name, current time down to the second, and the current session.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_JOB

Security ModelNo specific system privileges are required to use DBMS_JOB. No system privileges are available to manage DBMS_JOB. Jobs cannot be altered or deleted other than jobs owned by the user. This is true for all users including those users granted DBA privileges. You can execute procedures that are owned by the user or for which the user is explicitly granted EXECUTE. However, procedures for which the user

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_MAIL

Security Modelthe security exposure this involves. In installing UTL_MAIL, you should take steps to prevent the … Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DATAPUMP

Security ModelSecurity for the DBMS_DATAPUMP package is implemented through roles. Roles The existing … Although the SYS schema does not have the EXP_FULL_DATABASE role assigned to it, all security checks … IMP_FULL_DATABASE role assigned to it, all security checks performed by Data Pump that require the IMP_FULL_DATABASE role will also grant access

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_REPORT

Security ModelThe subprograms in the DBMS_REPORT package operate under the current user's privileges. When reports are generated by means of the DBMS_REPORT interface, the component building the report will check to ensure the current user has all of the necessary privileges to see that report.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_MGWMSG

Security ModelThe EXECUTE privilege is granted to PUBLIC on all types defined in the DBMS_MGWMSG package as well as the canonical types. The DBMS_MGWMSG packages and object types are owned by SYS. Note: You must run the catmgw.sql script to load the Messaging Gateway packages and object types into the database. Refer to the Oracle Streams Advanced Queuing User's Guide for information on loading database objects

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_WORKLOAD_CAPTURE

Security ModelThe following code describes the minimal set of privileges required to Create directory objects Operate the interface provided by the DBMS_WORKLOAD_CAPTURE and DBMS_WORKLOAD_REPLAY packages Act as a replay client user (wrc someuser / somepassword or wrc USER=someuser PASSWORD=somepassword ) DROP USER rom1 CASCADE; CREATE USER rom1 IDENTIFIED BY rom1; GRANT EXECUTE ON DBMS_WORKLOAD_CAPTURE TO rom1;

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_OUTLN

Security ModelDBMS_OUTLN contains management procedures that should be available to appropriate users only. EXECUTE privilege is not extended to the general user community unless the DBA explicitly does so. PL/SQL functions that are available for outline management purposes can be executed only by users with EXECUTE privilege on the procedure (or package).

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_DDL

Security ModelThis package runs with the privileges of the calling user, rather than the package owner SYS.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_LIBCACHE

Security Modelobjects with access granted though roles. This is a standard PL/SQL security limitation.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CRYPTO

Security ModelOracle Database installs this package in the SYS schema. You can then grant package access to existing users and roles as needed.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ADVISOR

Security ModelSecurity on this package can be controlled by granting EXECUTE on this package to selected users or

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_APPLICATION_INFO

Security ModelNote: The public synonym for DBMS_APPLICATION_INFO is not dropped before creation so that you can redirect the public synonym to point to your own package. No further privileges are required. The DBMSAPIN.SQL script is already run as a part of standard database creation.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_TCP

Security Modelconnect. Note: For more information, see Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ADVANCED_REWRITE

Security Modeladministrators. You can control security on this package by granting the EXECUTE privilege to

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_SESSION

Security ModelThis package runs with the privileges of the calling user, rather than the package owner SYS.

Database New Features Guide, 11g Release 1 (11.1)

Oracle 11g Database New Features

1.12 Securitycolumns as FLOAT ODBC applications will perform faster, with little or no code change. 1.12 Security … Features described in the following sections include security and compliance.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_RULE

Security ModelPUBLIC is granted EXECUTE privilege on this package.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_PROFILER

Security ModelThe profiler only gathers data for units for which a user has CREATE privilege; you cannot use the package to profile units for which EXECUTE ONLY access has been granted. In general, if a user can debug a unit, the same user can profile it. However, a unit can be profiled whether or not it has been compiled DEBUG. Oracle advises that modules that are being profiled should be compiled DEBUG, since

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_CDC_PUBLISH

Security ModelYou must have the EXECUTE_CATALOG_ROLE role to use the DBMS_CDC_PUBLISH package. Additional privileges and roles are required depending on the publishing mode and whether the publisher is on the source or staging database. See the section on Granting Privileges and Roles to the Publisher in Oracle Database Data Warehousing Guide for details.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_STREAMS_ADM

Security Modeluser is the user in whose security domain a capture process or synchronous capture captures changes … user in whose security domain an apply process dequeues messages that satisfy its rule sets, applies

Database Concepts, 11g Release 1 (11.1)

Schema Object Dependencies

Security AuthorizationOracle Database notices when a DML object or system privilege is granted to or revoked from a user or PUBLIC and automatically invalidates all the owner's dependent objects. Oracle Database invalidates the dependent objects to verify that an owner of a dependent object continues to have the necessary privileges for all referenced objects.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_TDB

Security ModelUse of this package requires the DBA privilege.

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_SMTP

Security Modelconnect. Note: For more information, see Managing Fine-grained Access to External Network Services in Oracle Database Security Guide

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

UTL_FILE

Security ModelThe set of files and directories that are accessible to the user through UTL_FILE is controlled by a number of factors and database parameters. Foremost of these is the set of directory objects that have been granted to the user. The nature of directory objects is discussed in [AWAITING XLINK TARGET]. Assuming the user has both READ and WRITE access to the directory object user_dir, the user can open

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DBMS_ALERT

Security ModelSecurity on this package can be controlled by granting EXECUTE on this package to selected users or

Database PL/SQL Packages and Types Reference, 11g Release 1 (11.1)

DEBUG_EXTPROC

Security ModelYour Oracle account must have EXECUTE privileges on the package and CREATE LIBRARY privileges.





Was this page helpful?

Integrated Cloud Applications & Platform Services