Oracle® Label Security

Administrator's Guide

12c Release 1 (12.1)

E48437-04

June 2014

Oracle Label Security Administrator's Guide, 12c Release 1 (12.1)

E48437-04

Copyright © 2006, 2014, Oracle and/or its affiliates. All rights reserved.

Contributor:  The Oracle Database 12c documentation is dedicated to Mark Townsend, who was an inspiration to all who worked on this release.

Contributors: Chi Ching Chui, Rishabh Gupta, John Kati, Lakshmi Kethana, Gopal Mulagund, Paul Needham, Hozefa Palitanawala, Vikram Pesati, Amoghavarsha Ramappa, Digvijay Sirmukaddam, Srividya Tata, Kamal Tbeileh, Peter Wahl

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

List of Examples

5-1 Creating a Policy Using SA_SYSDBA.CREATE_POLICY

5-2 Creating a Policy Level Using SA_COMPONENTS.CREATE_LEVEL

5-3 Creating a Compartment Using SA_COMPONENTS.CREATE_COMPARTMENT

5-4 Creating a Group Using SA_COMPONENTS.CREATE_GROUP

5-5 Creating a Data Label Using SA_LABEL_ADMIN.CREATE_LABEL

5-6 Authorizing a User Level with SA_USER_ADMIN.SET_LEVELS

5-7 Authorizing a User Compartment with SA_USER_ADMIN.SET_COMPARTMENTS

5-8 Authorizing a User Group with SA_USER_ADMIN.SET_GROUPS

5-9 Granting a Privileges to a User with SA_USER_ADMIN.SET_USER_PRIVS

5-10 Granting Privileges to a Program Unit with SA_USER_ADMIN.SET_PROG_PRIVS

5-11 Applying a Policy with SA_POLICY_ADMIN.APPLY_TABLE_POLICY

5-12 Applying a Schema Policy with SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY

5-13 Configuring Auditing with SA_AUDIT_ADMIN.AUDIT

B-1 Using OCI to Externalize SYS_CONTEXT with OLS

List of Figures

1-1 Oracle Label Security Label-Based Security

1-2 Oracle Label Security Architecture

1-3 Using Enterprise Manager to Configure Oracle Label Security Policies

2-1 Data Categorization with Levels, Compartments and Groups

2-2 Label Matrix

2-3 Group Example

2-4 Example: Data Labels and User Labels

2-5 How Label Components Interrelate

3-1 Relationships Between Users, Data, and Labels

3-2 User Session Label

3-3 Setting Up Authorized Compartments In Enterprise Manager

3-4 Setting Up Authorized Groups in Enterprise Manager

3-5 Subgroup Inheritance of Read/Write Access

3-6 Label Evaluation Process for Read Access

3-7 Label Evaluation Process for Write Access

3-8 Label Evaluation Process for Read Access with COMPACCESS Privilege

3-9 Label Evaluation Process for Write Access with COMPACCESS Privilege

3-10 Stored Program Unit Execution

5-1 Compartments in a Label

5-2 Group Example

7-1 Diagram of Oracle Label Security Metadata Storage in Oracle Internet Directory

7-2 Oracle Label Security Policies Applied through Oracle Internet Directory

8-1 Label Evaluation Process for LABEL_UPDATE

11-1 Using Oracle Label Security with a Distributed Database

11-2 Label Tags in a Distributed Database

11-3 Label Components in a Distributed Database

11-4 Use of Materialized Views for Replication

13-1 Read Access Label Evaluation with Inverse Groups

13-2 Write Access Label Evaluation with Inverse Groups

13-3 Read Access Label Evaluation: COMPACCESS Privilege and Inverse Groups

13-4 Write Access Label Evaluation: COMPACCESS Privilege and Inverse Groups

List of Tables

1-1 Oracle Label Security Administrative Packages

2-1 Data Dimensions for Controlling Access to Data

2-2 Sensitivity Label Components

2-3 Level Example

2-4 Forms of Specifying Levels

2-5 Compartment Example

2-6 Forms of Specifying Compartments

2-7 Group Example

2-8 Forms of Specifying Groups

2-9 Typical Levels, Compartments, and Groups, by Industry

3-1 Authorized Levels Set by the Administrator

3-2 Computed Session Labels

3-3 Oracle Label Security Privileges

3-4 Types of Privilege

5-1 Sensitivity Data Label Components

5-2 Policy Level Example

5-3 Forms of Specifying Levels

5-4 Policy Compartment Example

5-5 Forms of Specifying Compartments

5-6 Group Example

5-7 Forms of Specifying Groups

5-8 Authorized Levels Set by the Administrator

5-9 Oracle Label Security Privileges

5-10 Auditing Options for Oracle Label Security

6-1 Administratively Defined Label Tags (Example)

6-2 Generated Label Tags (Example)

6-3 Data Returned from Sample SQL Statements re Hidden Column

6-4 Data Returned from Sample SQL Statements re Least_UBound

6-5 MERGE_LABEL Format Constants

7-1 Contents of Each Policy

7-2 Elements in a DIP Provisioning Profile

7-3 Tasks That Certain Entities Can Perform

7-4 Access Levels Allowed by Users in OID

7-5 Procedures Superseded by olsadmintool When Using Oracle Internet Directory

8-1 When Policy Enforcement Options Take Effect

8-2 Policy Enforcement Options

8-3 What Policy Enforcement Options Control

8-4 Suggested Policy Enforcement Option Combinations

10-1 AUDIT_TRAIL Parameter Settings

12-1 Input Choices for Oracle Label Security Input to SQL*Loader

12-2 Label Tag Performance Example: Correct Values

12-3 Label Tag Performance Example: Incorrect Values

13-1 Access to Standard Groups and Inverse Groups

13-2 Policy Example

13-3 Computed Session Labels with Inverse Groups

13-4 Sets of Groups for Evaluating Read and Write Access

13-5 Read and Write Authorizations for Standard Groups and Inverse Groups

13-6 Labels for Inverse Groups Example 1

13-7 Labels for Inverse Groups Example 2

13-8 Access Authorized by Values of access_mode Parameter

13-9 Assigning Groups to a User

13-10 Inverse Group Label Definitions

B-1 Dominance in the Comparison of Labels

B-2 Functions to Determine Dominance

B-3 OLS_DOMINATES Parameters

B-4 OLS_LABEL_DOMINATES Parameters

B-5 OLS_STRICTLY_DOMINATES Parameters

B-6 OLS_STRICTLY_DOMINATES Parameters

B-7 OLS_DOMINATES Parameters

B-8 SA_UTL.DOMINATES Parameters

B-9 SA_UTL.STRICTLY_DOMINATES Parameters

B-10 SA_UTL.DOMINATED_BY Parameters

B-11 SA_UTL.STRICTLY_DOMINATED_BY Parameters

B-12 ORA_GET_AUDITED_LABEL Parameters

C-1 Oracle Label Security Commands in Categories

C-2 olsadmintool Commands Linked to Their Explanations

C-3 Summary: olsadmintool Command Parameters

C-4 Summary of Profile and Default Command Parameters

C-5 Label Component Definitions from Using olsadmintool Commands

C-6 Contents of Profile1 from Using olsadmintool Commands

D-1 Policy Functions Preserving Status in an Oracle RAC Environment

D-2 Session Functions Preserving Status in an Oracle RAC Environment

E-1 SA_AUDIT_ADMIN PL/SQL Package Contents

E-2 SA_AUDIT_ADMIN.AUDIT Parameters

E-3 SA_AUDIT_ADMIN.AUDIT_LABEL Parameter

E-4 SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED Parameter

E-5 SA_AUDIT_ADMIN.CREATE_VIEW Parameters

E-6 SA_AUDIT_ADMIN.DROP_VIEW Parameters

E-7 SA_AUDIT_ADMIN.NO_AUDIT Parameters

E-8 SA_AUDIT_ADMIN.NO_AUDIT_LABEL Parameter

E-9 SA_COMPONENTS PL/SQL Package Contents

E-10 SA_COMPONENTS.ALTER_COMPARTMENT Parameters

E-11 SA_COMPONENTS.ALTER_GROUP Parameters

E-12 SA_COMPONENTS.ALTER_GROUP_PARENT Parameters

E-13 SA_COMPONENTS.ALTER_LEVEL Parameters

E-14 SA_COMPONENTS.CREATE_COMPARTMENT Parameters

E-15 SA_COMPONENTS.CREATE_GROUP Parameters

E-16 SA_COMPONENTS.CREATE_LEVEL Parameters

E-17 SA_COMPONENTS.DROP_COMPARTMENT Parameters

E-18 SA_COMPONENTS.DROP_GROUP Parameters

E-19 SA_COMPONENTS.DROP_LEVEL Parameters

E-20 SA_LABEL_ADMIN PL/SQL Package Contents

E-21 SA_LABEL_ADMIN.ALTER_LABEL Parameters

E-22 SA_LABEL_ADMIN.CREATE_LABEL Parameters

E-23 SA_LABEL_ADMIN.DROP_LABEL Parameters

E-24 SA_POLICY_ADMIN PL/SQL Package Contents

E-25 SA_POLICY_ADMIN.ALTER_SCHEMA Parameters

E-26 SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Parameters

E-27 SA_POLICY_ADMIN.APPLY_TABLE_POLICY Parameters

E-28 SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY Parameters

E-29 SA_POLICY_ADMIN.DISABLE_TABLE_POLICY Parameters

E-30 SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY Parameters

E-31 SA_POLICY_ADMIN.ENABLE_TABLE_POLICY Parameters

E-32 SA_POLICY_ADMIN.POLICY_SUBSCRIBE Parameter

E-33 SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE Parameters

E-34 SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY Parameters

E-35 SA_POLICY_ADMIN.REMOVE_TABLE_POLICY Parameters

E-36 SA_SESSSION PL/SQL Package Contents

E-37 SA_SESSION.COMP_READ Parameter

E-38 SA_SESSION.COMP_WRITE Parameter

E-39 SA_SESSION.GROUP_READ Parameter

E-40 SA_SESSION.GROUP_WRITE Parameter

E-41 SA_SESSION.LABEL Parameter

E-42 SA_SESSION.MAX_LEVEL Parameter

E-43 SA_SESSION.MAX_READ_LABEL Parameter

E-44 SA_SESSION.MAX_WRITE_LABEL Parameter

E-45 SA_SESSION.MIN_LEVEL Parameter

E-46 SA_SESSION.MIN_WRITE_LABEL Parameter

E-47 SA_SESSION.Privs Parameter

E-48 SA_SESSION.RESTORE_DEFAULT_LABEL Parameter

E-49 SA_SESSION.ROW_LABEL Parameters

E-50 SA_SESSION.SET_LABEL Parameters

E-51 SA_SESSION.SA_USER_NAME Parameters

E-52 SA_SESSION.SAVE_DEFAULT_LABELS Parameter

E-53 SA_SESSION.SET_ACCESS_PROFILE Parameters

E-54 SA_SESSION.SET_ROW_LABEL Parameters

E-55 SA_SYSDBA PL/SQL Package Contents

E-56 SA_SYSDBA.ALTER_POLICY Parameters

E-57 SA_SYSDBA.CREATE_POLICY Parameters

E-58 SA_SYSDBA.DISABLE_POLICY Parameters

E-59 SA_SYSDBA.DROP_POLICY Parameters

E-60 SA_SYSDBA.ENABLE_POLICY Parameters

E-61 SA_USER_ADMIN PL/SQL Package Contents

E-62 SA_USER_ADMIN.ADD_COMPARTMENTS Parameters

E-63 SA_USER_ADMIN.ADD_GROUPS Parameters

E-64 SA_USER_ADMIN.ALTER_COMPARTMENTS Parameters

E-65 SA_USER_ADMIN.ALTER_GROUPS Parameters

E-66 SA_USER_ADMIN.DROP_ALL_COMPARTMENTS Parameters

E-67 SA_USER_ADMIN.DROP_ALL_GROUPS Parameters

E-68 SA_USER_ADMIN.DROP_COMPARTMENTS Parameters

E-69 SA_USER_ADMIN.DROP_GROUPS Parameters

E-70 SA_USER_ADMIN.DROP_USER_ACCESS Parameters

E-71 SA_USER_ADMIN.SET_COMPARTMENTS Parameters

E-72 SA_USER_ADMIN.SET_DEFAULT_LABEL Parameters

E-73 SA_USER_ADMIN.SET_GROUPS Parameters

E-74 SA_USER_ADMIN.SET_LEVELS Parameters

E-75 SA_SESSION.SET_LABEL Parameters

E-76 SA_USER_ADMIN.SET_ROW_LABEL Parameters

E-77 SA_USER_ADMIN.SET_USER_LABELS Parameters

E-78 SA_USER_ADMIN.SET_USER_PRIVS Parameters

E-79 SA_UTL PL/SQL PL/SQL Package Contents

E-80 SA_UTL.CHECK_LABEL_CHANGE Parameters

E-81 SA_UTL.CHECK_READ Parameters

E-82 SA_UTL.CHECK_WRITE Parameters

E-83 SA_UTL.DATA_LABEL Parameter

E-84 SA_UTL.GREATEST_LBOUND Parameters

E-85 SA_UTL.LEAST_UBOUND Parameters

E-86 SA_UTL.NUMERIC_LABEL Parameter

E-87 SA_UTL.NUMERIC_ROW_LABEL Parameters

E-88 SA_UTL.SET_LABEL Parameters

E-89 SA_UTL.SET_ROW_LABEL Parameters

Preface

Oracle Label Security enables access control to reach specific (labeled) rows of a database. With Oracle Label Security in place, users with varying privilege levels automatically have (or are excluded from) the right to see or alter labeled rows of data.

The Oracle Label Security Administrator's Guide describes how to use Oracle Label Security to protect sensitive data. It explains the basic concepts behind label-based security and provides examples to show how it is used.

This preface contains these topics:

Audience

Documentation Accessibility

Related Documentation

Conventions

Audience

The Oracle Label Security Administrator's Guide is intended for database administrators (DBAs), application programmers, security administrators, system operators, and other Oracle users who perform the following tasks:

Analyze application security requirements

Create label-based security policies

Administer label-based security policies

Use label-based security policies

To use this document, you need a working knowledge of SQL and Oracle fundamentals. You should also be familiar with Oracle security features described in "Related Documentation". To use SQL*Loader, you must know how to use the file management facilities of your operating system.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documentation

For more information, see these Oracle resources:

Oracle Database Concepts

Oracle Database Security Guide

Oracle Database 2 Day + Security Guide

Oracle Database Enterprise User Security Administrator's Guide

Oracle Database Development Guide

Oracle Database Administrator's Guide

Oracle Database SQL Language Reference

Oracle Database Reference

Oracle Database Advanced Replication

Oracle Database Utilities

Oracle Database Performance Tuning Guide

Oracle Internet Directory Administrator's Guide

Oracle Identity Management Integration Guide

Many of the examples in this book use the sample schemas, which are installed by default when you select the Basic Installation option with an Oracle Database installation. See Oracle Database Sample Schemas for information on how these schemas were created and how you can use them yourself.

To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN) at

http://www.oracle.com/technetwork/index.html

For the latest version of the Oracle documentation, including this guide, visit

http://www.oracle.com/technetwork/documentation/index.html

Conventions

The following text conventions are used in this document:

Convention | Meaning
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Changes in This Release for Oracle Label Security Administrator's Guide

This preface contains:

Changes in Oracle Database 12c Release 1 (12.1.0.2)

Changes in Oracle Database 12c Release 1 (12.1.0.1)

Changes in Oracle Database 12c Release 1 (12.1.0.2)

The following are changes in Oracle Label Security Administrator's Guide for Oracle Database 12c Release 1 (12.1.0.2).

This section contains:

New Features

Deprecated Features

New Features

This section contains:

OLS_LABEL_DOMINATES Function

OLS_LABEL_DOMINATES Function

New for this release is the standalone OLS_LABEL_DOMINATES function, which replaces the SA_UTL.DOMINATES function.

See "OLS_LABEL_DOMINATES Standalone Function" for more information.

Deprecated Features

This section contains:

SA_UTL.DOMINATES Function

SA_UTL.DOMINATES Function

The following standalone function is deprecated in this release, and may be desupported in a future release:

SA_UTL.DOMINATES, using the following syntax:

FUNCTION DOMINATES (
  ols_policy_name  IN VARCHAR2,
  label            IN VARCHAR2)
RETURN BOOLEAN

The SA_UTL.DOMINATES function that uses the NUMBER datatype is not deprecated.

Changes in Oracle Database 12c Release 1 (12.1.0.1)

The following are changes in Oracle Label Security Administrator's Guide for Oracle Database 12c Release 1 (12.1.0.1).

This section contains:

New Features

Deprecated Features

Other Changes

New Features

The following features are new in this release:

Upgrade and Downgrade Requirements for Oracle Database Release 12c (12.1)

Oracle Label Security and the Oracle Multitenant Option

Simplified Oracle Label Security Installation

Unified Audit Trail and Oracle Label Security

Simplified Oracle Label Security Metadata Export and Import

Upgrade and Downgrade Requirements for Oracle Database Release 12c (12.1)

Oracle Label Security has specific requirements for upgrades and downgrades from or to Oracle Database 12c Release 1 (12.1).

See "Oracle Label Security Upgrades and Downgrades" for more information.

Oracle Label Security and the Oracle Multitenant Option

Oracle Database Release 12.1 introduces the Oracle Multitenant option, which enables you to plug one or more pluggable databases (PDBs) into a multitenant container database (CDB).

You can use Oracle Label Security with a CDB. Each PDB has its own Label Security metadata, such as policies, labels, and user authorizations. In addition, the objects within the LBACSYS schema are automatically available to any child PDB. LBACSYS schema is a common user schema.

See "Oracle Label Security Integration in a Multitenant Environment" for more information.

Simplified Oracle Label Security Installation

Oracle Label Security is installed by default in Oracle Database 12c Release 1 (12.1), making the installation process simpler. You do not need to perform an advanced installation and select the Oracle Label Security check box.

See "When You Must Disable Oracle Label Security" for more information.

Unified Audit Trail and Oracle Label Security

Oracle Database 12c Release 1 (12.1) uses a unified audit trail to capture information from various audit sources, including Oracle Label Security. OLS auditing is configured using audit policies. OLS auditing in 12c Release 1 (12.1) enables you to audit additional events such as enabling and disabling OLS policies.

See Also:

Oracle Database Upgrade Guide for instructions on configuring your upgraded database to use unified auditing. After migration, you can create unified audit policies. See Oracle Database Security Guide

If you have upgraded your database to 12c Release 1 (12.1), but have not configured it to use unified auditing, then you must use pre-12c OLS auditing.

See Chapter 10, "Auditing Under Oracle Label Security" for more information.

Simplified Oracle Label Security Metadata Export and Import

Starting with Oracle Database 12c Release 1 (12.1), Oracle Label Security metadata in the LBACSYS schema can be included when doing a full database export and import operation. The source database can be Oracle Database 11g Release 2 (11.2.0.3), or higher, but the target database must be Oracle Database 12c Release 1 (12.1) or higher.

See Chapter 12, "Performing DBA Functions Under Oracle Label Security" for more information.

Deprecated Features

The following standalone functions are deprecated in this release, and may be desupported in a future release:

LEAST_UBOUND

You can use OLS_GREATEST_LBOUND instead.

See "Finding Greatest Lower Bound with GREATEST_LBOUND" for information about alternatives.

LUBD

You can use OLS_GLBD instead.

See "Finding Greatest Lower Bound with GREATEST_LBOUND" for information about alternatives.

DOMINATES

See "OLS_DOMINATES Standalone Function" for information about alternatives.

DOM

See "OLS_STRICTLY_DOMINATES Standalone Function" for information about alternatives.

STRICTLY_DOMINATES

See "OLS_STRICTLY_DOMINATES Standalone Function" for information about alternatives.

S_DOM

See "OLS_DOMINATES Standalone Function" for information about alternatives.

DOMINATED_BY

See "OLS_DOMINATED_BY Standalone Function" for information about alternatives.

DOM_BY

See "OLS_DOMINATED_BY Standalone Function" for information about alternatives.

STRICTLY_DOMINATED_BY

See "OLS_STRICTLY_DOMINATED_BY Standalone Function" for information about alternatives.

S_DOM_BY

See "OLS_STRICTLY_DOMINATED_BY Standalone Function" for information about alternatives.

Other Changes

The following are additional changes in the release:

There has been some reorganization of chapters and appendixes.

A new appendix, Oracle Label Security PL/SQL Packages, has been added. Most packages previously described in chapters, have been moved to this appendix.

See Appendix E, "Oracle Label Security PL/SQL Packages"

Part I

Part I introduces the terms, concepts, and relationships that constitute the basic elements of Oracle Label Security. It contains the following chapters:

Chapter 1, "Introduction to Oracle Label Security"

Chapter 2, "Understanding Data Labels and User Labels"

Chapter 3, "Understanding Access Controls and Privileges"

1 Introduction to Oracle Label Security

This chapter contains:

About Oracle Label Security

Benefits of Oracle Label Security

Who Has Privileges to Use Oracle Label Security?

Organizing the Duties of Oracle Label Security Administrators

Components of Oracle Label Security

Oracle Label Security Architecture

Choosing an Oracle Label Security Administrative Interface

How Oracle Label Security Works with Other Oracle Products

About Oracle Label Security

Oracle Label Security enables you to control the display of individual table rows using labels that are assigned to individual table rows and application users. Oracle Label Security is based on multi-level security (MLS) requirements that are found in government and defense organizations. You can easily restrict sensitive information to only authorized users. Oracle Label Security is based on Oracle Virtual Private Database (VPD). However, unlike VPD, Oracle Label Security provides the access mediation functions, data dictionary tables, and policy based architecture out of the box, eliminating customized coding and providing a consistent label based access control model that can be used by multiple applications. Oracle Label Security policies can be applied to one or more application tables. Oracle Label Security works by comparing the row label with a user's label authorizations. Oracle Label Security software is installed by default, but not automatically enabled. You can easily enable Oracle Label Security in either SQL*Plus or by using the Oracle Database Configuration Assistant (DBCA). To manage Oracle Label Security, you can use either Oracle Enterprise Manager Cloud Control or a set of PL/SQL packages and standalone functions at the command line level. The default administrator for Oracle Label Security is the user LBACSYS. To find information about Oracle Label Security policies, you can query ALL_SA_*, DBA_SA_*, or USER_SA_* data dictionary views.

Benefits of Oracle Label Security

Oracle Label Security provides the following benefits:

It enables row level data classification and provides out of the box access mediation based on the data classification and the user label authorization or security clearance.

It enables you to assign label authorizations or security clearances to both database users and application users.

It provides both a graphical user interface and APIs for defining and storing data classification labels and user label authorizations.

It integrates with Oracle Database Vault and Oracle Advanced Security Data Redaction, enabling security clearances to be use in both Database Vault command rules and Data Redaction policy definitions.

Who Has Privileges to Use Oracle Label Security?

When you register Oracle Label Security with a database, the registration process creates an administrative user named LBACSYS, who has the LBAC_DBA database role. You can grant this role to any database user who will be responsible for managing Oracle Label Security policies. In addition, you can grant Oracle Label Security administrators the EXECUTE privilege for the Oracle Label Security packages, and privileges to manage individual Oracle Label Security policies.

Organizing the Duties of Oracle Label Security Administrators

You can manage the administration of an Oracle Label Security policy by using the following privileges:

Package-specific privileges: Most of the Oracle Label Security PL/SQL packages, except for the public SA_SESSION and SA_UTL packages, require the EXECUTE privilege.

Role-based privileges: The Oracle Label Security-specific roles are:

The policy_DBA role, which is created and granted to the user when he or she creates a policy. For example, for a policy named ols_hr_pol, the role created is named ols_hr_pol_DBA. This role adds a layer of granularity for access control for your site's Oracle Label Security policies.

The LBAC_DBA role, which provides the EXECUTE privilege for the LBAC_SYSDBA package. This role is owned by the LBACSYS user account. The LBAC_SYSDBA package enables the user to create, alter, enable, disable, and drop Oracle Label Security policies. This package is a wrapper for the SA_SYSDBA package.

You can use the Oracle Label Security package EXECUTE privilege grants along with grants of the policy_DBA role to achieve additional separation of duty. The packages are categorized based on different tasks. For example, you could grant the EXECUTE privilege on the SA_COMPONENTS and SA_LABEL_ADMIN packages to one user or role to manage label definitions, and then grant EXECUTE on SA_USER_ADMIN to a different user or role to manage user labels and privileges. Both of these users or roles must also be granted the policy_DBA role for the policies for which they are responsible. In this way, different users can be responsible for the management of different aspects of the policies for which they are responsible. For example, user psmith could be responsible for the label definitions of the ols_hr_pol policy, and user tjones could be responsible for the label definitions of the ols_oe_pol policy. However, user psmith cannot modify label definitions for the ols_oe_pol policy, nor can tjones modify the ols_hr_pol policy label definitions.

See Also:

"Oracle Label Security Packages"

Components of Oracle Label Security

An Oracle Label Security has the following components:

Labels. Labels for data and users, along with authorizations for users and program units, govern access to specified protected objects. Labels are composed of the following:

Levels. Levels indicate the type of sensitivity that you want to assign to the row, for example, SENSITIVE or HIGHLY SENSITIVE.

Compartments. (Optional) Data can have the same level (Public, Confidential and Secret), but can belong to different projects inside a company, for example ACME Merger and IT Security. Compartments represent the projects in this example, that help define more precise access controls. They are most often used in government environments.

Groups. (Optional) Groups identify organizations owning or accessing the data, for example, UK, US, Asia, Europe. Groups are used both in commercial and government environments, and frequently used in place of compartments due to their flexibility.

Policy. A policy is a name associated with these labels, rules, authorizations, and protected tables.

For example, assume that a user has the SELECT privilege on an application table. As illustrated in Figure 1-1, when the user runs a SELECT statement, Oracle Label Security evaluates each row selected to determine whether the user can access using the privileges and labels assigned to the user and the label on the row. You can configure Oracle Label Security to perform security checks on UPDATE, DELETE, and INSERT statements as well.

Figure 1-1 Oracle Label Security Label-Based Security

Oracle Label Security Architecture

Figure 1-2 shows how data is accessed under Oracle Label Security and the sequence of label security checks.

Figure 1-2 Oracle Label Security Architecture

In this scenario, the following actions take place:

An application user in an Oracle Database session sends a SQL request to query a table.

Oracle Database checks the user's data access control (DAC) privileges for performing a SELECT statement on the table.

If the user does have the appropriate privileges, then Oracle Database checks if there are any Oracle Virtual Private Database (VPD) policies attached to the table.

Oracle Database then checks if there are any Oracle Label Security policies that are assigned to the table.

Oracle Label Security then compares the labels that are assigned to individual rows with the users' label authorizations, allowing or denying access. The session label is based on label authorizations that are assigned to the user.

Choosing an Oracle Label Security Administrative Interface

You can perform Oracle Label Security development and administrative tasks using either of two interfaces:

Oracle Label Security Packages

Oracle Enterprise Manager Cloud Control

Oracle Label Security Packages

Oracle Label Security packages provide a direct, command-line interface for ease of administration. These include:

Table 1-1 Oracle Label Security Administrative Packages

Package
Purpose

SA_SYSDBA

To create, alter, and drop Oracle Label Security policies

See "SA_SYSDBA Policy Management PL/SQL Package"

SA_COMPONENTS

To define the levels, compartments, and groups for the policy

See "SA_COMPONENTS Label Components PL/SQL Package"

SA_LABEL_ADMIN

To perform standard label policy administrative functions, such as creating labels

See "SA_LABEL_ADMIN Label Management PL/SQL Package"

SA_POLICY_ADMIN

To apply policies to schemas and tables

See "SA_POLICY_ADMIN Policy Administration PL/SQL Package"

SA_USER_ADMIN

To manage user authorizations for levels, compartments, and groups, as well as program unit privileges. Also to administer user privileges.

See "SA_USER_ADMIN.SET_USER_PRIVS Procedure" and "SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

SA_AUDIT_ADMIN

To set options to audit administrative tasks and use of privileges

See "SA_AUDIT_ADMIN Oracle Label Security Auditing PL/SQL Package"

SA_SESSION

To change labels during a during a session within the authorizations set by the administrator

See "SA_SESSION Session Management PL/SQL Package"

SA_UTL

A set of utility functions designed for use within PL/SQL programs to return information about the current values of the session security attributes, as numeric label values

See "SA_UTL PL/SQL Utility Functions and Procedures"

Oracle Label Security Demonstration File

For a demonstration showing how to create and develop an Oracle Label Security policy using the supplied packages, refer to the olsdemo.sql file. You can install this script from the Companion CD. By default, it resides in the ORACLE_HOME/rdbms/demo directory.

Oracle Enterprise Manager Cloud Control

You can use the Web interface provided by Oracle Enterprise Manager Cloud Control to administer Oracle Label Security. Figure 1-3 illustrates the Oracle Enterprise Manager interface.

Figure 1-3 Using Enterprise Manager to Configure Oracle Label Security Policies

See Also:

"Logging into Cloud Control or SQL*Plus for Oracle Label Security" more information about logging into either Cloud Control or SQL*Plus to administer Oracle Label Security policies

Chapter 4, "Getting Started with Oracle Label Security" for details on using Enterprise Manager to administer Oracle Label Security

How Oracle Label Security Works with Other Oracle Products

This section contains:

Oracle Label Security Integration with Oracle Internet Directory

Oracle Label Security Integration in a Multitenant Environment

Oracle Label Security Integration with Oracle Internet Directory

Sites that integrate their use of Oracle Label Security with Oracle Internet Directory gain significant efficiencies of label security operation and administration. Policies and user authorization profiles are created and managed directly in the directory by means of the commands described in Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory". Changes are automatically propagated to the associated directories.

A complete introduction to this integration is presented in Chapter 7, "Oracle Label Security Using Oracle Internet Directory."

Oracle Label Security Integration in a Multitenant Environment

You can use Oracle Label Security in a multitenant environment, in which pluggable databases (PDBs) can be plugged in and out of a multitenent container database (CDB). Each PDB has its own Oracle Label Security metadata, such as policies, labels, and user authorizations. The LBACSYS schema is a common user schema. See "Enabling the LBACSYS Oracle Label Security User Account" for more information about the LBACSYS account.

Before you plug a PDB into a CDB, if the database does not have Oracle Label Security installed, then ensure that you have run the $ORACLE_HOME/rdbms/admin/catols.sql script on the database. See Oracle Database Administrator's Guide for more information about creating CDBs.

Because Oracle Label Security policies are scoped to individual PDBs, you can create individual policies for each PDB. A policy defined for a PDB can be enforced on the local tables and schema objects contained in the PDB.

You cannot create Oracle Label Security policies in the root. In a single CDB, there can be multiple PDBs, each configured with Oracle Label Security.

If you are configuring Oracle Label Security with Oracle Internet Directory, be aware that the same configuration must be used throughout with all PDBs contained in the CDB. You can determine if your database is configured for Oracle Internet Directory by querying the DBA_OLS_STATUS data dictionary view as follows from within any PDB:

SELECT STATUS FROM DBA_OLS_STATUS WHERE NAME = 'OLS_DIRECTORY_STATUS';

If it returns TRUE, then Oracle Label Security is Internet Directory-enabled. Otherwise, it returns FALSE.

See Also:

Oracle Database Security Guide for information on how the multitenant architecture affects privileges

"Oracle Label Security Integration with Oracle Internet Directory" for information about Internet Directory-enabled Oracle Label Security

2 Understanding Data Labels and User Labels

This chapter discusses the fundamental concepts of data labels and user labels, and introduces the terminology that will help you understand Oracle Label Security.

The chapter includes:

About to Label-Based Security

Label Components

Label Syntax and Type

How Data Labels and User Labels Work Together

Administering Labels

About to Label-Based Security

Label-based security provides a flexible way of controlling access to sensitive data. Oracle Label Security controls data access based on the identity and label of the user, and the sensitivity and label of the data. Label security adds protections beyond the discretionary access controls that determine the operations users can perform upon data in an object, such as a table or view.

Table 2-1 shows the three dimensions with which an Oracle Label Security policy controls access to data.

Table 2-1 Data Dimensions for Controlling Access to Data

Data Dimension
Explanation

Data Labels

A data row label indicates the level and nature of the row's sensitivity and specifies the additional criteria that a user must meet to gain access to that row.

User Labels

A user label specifies that user's sensitivity level plus any compartments and groups that constrain the user's access to labeled data. Each user is assigned a range of levels, compartments, and groups, and each session can operate within that authorized range to access labeled data within that range.

Policy Privileges

Users can be given specific rights (privileges) to perform special operations or to access data beyond their label authorizations.

Note that the discussion here concerns access to data. The particular type of access, such as reading or writing the data, is covered in Chapter 3, "Understanding Access Controls and Privileges".

When an Oracle Label Security policy is applied to a database table, a column is added to the table to contain each row's label. The administrator can choose to display or hide this column.

About User Label and Privilege Management

To manage user labels and privileges, you must have the EXECUTE privilege for the SA_USER_ADMIN package, and must have been granted the policy_DBA role.

The SA_USER_ADMIN package provides the functions to manage the Oracle Label Security user security attributes. It contains several procedures to manage user labels by component: that is, specifying user levels, compartments, and groups. For convenience, there are additional procedures that accept character string representations of full labels, rather than components. Note that the level, compartment and group parameters use the short name defined for each component.

All of the label and privilege information is stored in Oracle Label Security data dictionary tables. When a user connects to the database, his session labels are established based on the information stored in the Oracle Label Security data dictionary.

Note that a user can be authorized under multiple policies.

See Also:

"SA_USER_ADMIN User, Levels, Groups, and Compartments PL/SQL Package"

"SA_USER_ADMIN.SET_USER_PRIVS Procedure"

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

Label Components

This section describes the elements defined for use in labels.

Label Component Definitions and Valid Characters

Level Sensitivity Components

Compartment Components

Group Components

Industry Examples of Levels, Compartments, and Groups

Label Component Definitions and Valid Characters

A sensitivity label is a single attribute with multiple components.

All data labels must contain a level component, but the compartment and group components are optional. An administrator must define the label components before creating labels.

Note:

Although the administrator defines both long and short names for the label components, only the short form of the name is displayed upon retrieval. When users manipulate the labels, they use only the short form of the component names. Examples of short forms are illustrated in component-specific example tables below.

Table 2-2 Sensitivity Label Components

Component
Description
Examples

Level

A single specification of the sensitivity of labeled data within the ordered ranks established

CONFIDENTIAL (1), SENSITIVE (2), HIGHLY_SENSITIVE (3)

Compartments

Zero or more categories associated with the labeled data

FINANCIAL, STRATEGIC, NUCLEAR

Groups

Zero or more identifiers for organizations owning or accessing the data

EASTERN_REGION, WESTERN_REGION

Valid characters for specifying all label components include alphanumeric characters, underscores, and spaces. (Leading and trailing spaces are ignored.)

The following figure illustrates the three dimensions in which data can be logically classified, using levels, compartments, and groups.

Figure 2-1 Data Categorization with Levels, Compartments and Groups

Level Sensitivity Components

A level is a ranking that denotes the sensitivity of the information it labels. The more sensitive the information, the higher its level. The less sensitive the information, the lower its level.

Every label must include one level. Oracle Label Security permits defining up to 10,000 levels in a policy. For each level, the Oracle Label Security administrator defines a numeric form, a long character form, and the required short character form.

For example, you can define a set of levels such as the following:

Table 2-3 Level Example

Numeric Form
Long Form
Short Form

40

HIGHLY_SENSITIVE

HS

30

SENSITIVE

S

20

CONFIDENTIAL

C

10

PUBLIC

P

Table 2-4 Forms of Specifying Levels

Form
Explanation

Numeric form, also called "tag"

The numeric form of the level can range from 0 to 9999. Sensitivity is ranked by this numeric value, so you must assign higher numbers to levels that are more sensitive, and lower numbers to levels that are less sensitive. In Table 2-3, 40 (HIGHLY_SENSITIVE) is a higher level than 30, 20, and 10.

Administrators should avoid using sequential numbers for the numeric form of levels. A good strategy is to use even increments (such as 50 or 100) between levels. You can then insert additional levels between two preexisting levels, at a later date.

Long form

The long form of the level name can contain up to 80 characters.

Short form

The short form can contain up to 30 characters.

Although the administrator defines both long and short names for the level (and for each of the other label components), only the short form of the name is displayed upon retrieval. When users manipulate the labels, they use only the short form of the component names.

Other sets of levels that users commonly define include TOP_SECRET, SECRET, CONFIDENTIAL, and UNCLASSIFIED or TRADE_SECRET, PROPRIETARY, COMPANY_CONFIDENTIAL, PUBLIC_DOMAIN.

If only levels are used, a level 40 user (in this example) can access or alter any data row whose level is 40 or less.

Note:

All levels and labels (including TOP_SECRET, SECRET, CONFIDENTIAL, and so on) in this guide, are used as illustrations only.

Compartment Components

Compartments identify areas that describe the sensitivity of the labeled data, providing a finer level of granularity within a level.

Compartments associate the data with one or more security areas. All data related to a particular project can be labeled with the same compartment. For example, you can define a set of compartments like the following:

Table 2-5 Compartment Example

Numeric Form
Long Form
Short Form

85

FINANCIAL

FINCL

65

CHEMICAL

CHEM

45

OPERATIONAL

OP

Table 2-6 Forms of Specifying Compartments

Form
Explanation

Numeric form

The numeric form can range from 0 to 9999. It is unrelated to the numbers used for the levels. The numeric form of the compartment does not indicate greater or less sensitivity. Instead, it controls the display order of the short form compartment name in the label character string. For example, assume a label is created that has all three compartments listed in Table 2-5, and a level of SENSITIVE. When this label is displayed in string format, it looks like this:

S:OP,CHEM,FINCL

meaning SENSITIVE: OPERATIONAL, CHEMICAL, FINANCIAL

The display order follows the order of the numbers assigned to the compartments: 45 is lower than 65, and 65 is lower than 85. By contrast, if the number assigned to the FINCL compartment were 5, the character string format of the label would look like this:

S:FINCL,OP,CHEM

Long form

The long form of the compartment name scan have up to 80 characters.

Short form

The short form can contain up to 30 characters.

Compartments are optional. A label can contain zero or more compartments. Oracle Label Security permits defining up to 10,000 compartments.

Not all labels need to have compartments. For example, you can specify HIGHLY_SENSITIVE and CONFIDENTIAL levels with no compartments, and a SENSITIVE level that does contain compartments.

When you analyze the sensitivity of data, you may find that some compartments are only useful at specific levels. Figure 2-2, "Label Matrix" shows how compartments can be used to categorize data.

Figure 2-2 Label Matrix

Here, compartments FINCL, CHEM, and OP are used with the level HIGHLY_SENSITIVE (40). The label HIGHLY_SENSITIVE:FINCL, CHEM indicates a level of 40 with the two named compartments. Compartment FINCL is not more sensitive than CHEM, nor is CHEM more sensitive than FINCL. Note also that some data in the protected table may not belong to any compartment.

If compartments are specified, then a user whose level would normally permit access to a row's data will nevertheless be prevented from such access unless the user's label also contains all the compartments appearing in that row's label.

Group Components

Groups identify organizations owning or accessing the data, such as EASTERN_REGION, WESTERN_REGION, WR_SALES. All data pertaining to a certain department can have that department's group in the label. Groups are useful for the controlled dissemination of data and for timely reaction to organizational change. When a company reorganizes, data access can change right along with the reorganization.

Groups are hierarchical. You can label data based upon your organizational infrastructure. A group can thus be associated with a parent group. For example, you can define a set of groups corresponding to the following organizational hierarchy:

Figure 2-3 Group Example

The WESTERN_REGION group includes three subgroups: WR_SALES, WR_HUMAN_RESOURCES, and WR_FINANCE. The WR_FINANCE subgroup is subdivided into WR_ACCOUNTS_RECEIVABLE and WR_ACCOUNTS_PAYABLE.

Table 2-7 shows how the organizational structure in this example can be expressed in the form of Oracle Label Security groups. Notice that the numeric form assigned to the groups affects display order only. The administrator specifies the hierarchy (that is, the parent/child relationships) separately.

Table 2-7 Group Example

Numeric Form
Long Form
Short Form
Parent Group

1000

WESTERN_REGION

WR

1100

WR_SALES

WR_SAL

WR

1200

WR_HUMAN_RESOURCES

WR_HR

WR

1300

WR_FINANCE

WR_FIN

WR

1310

WR_ACCOUNTS_PAYABLE

WR_AP

WR_FIN

1320

WR_ACCOUNTS_RECEIVABLE

WR_AR

WR_FIN

Table 2-8 Forms of Specifying Groups

Form
Explanation

Numeric form

The numeric form of the group can range from 0 to 9999, and it must be unique for each policy.

The numeric form does not indicate any kind of ranking. It does not indicate a parent-child relationship, or greater or less sensitivity. It only controls the display order of the short form group name in the label character string.

For example, assume that a label is created that has the level SENSITIVE, the compartment CHEMICAL, and the groups WESTERN_REGION and WR_HUMAN_RESOURCES as listed in . When displayed in string format, the label looks like this:

S:CHEM:WR,WR_HR

WR is displayed before WR_HR because 1000 comes before 1200.

Long form

The long form of the group name can contain up to 80 characters.

Short form

The short form can contain up to 30 characters.

Groups are optional; a label can contain zero or more groups. Oracle Label Security permits defining up to 10,000 groups.

All labels need not have groups. When you analyze the sensitivity of data, you may find that some groups are only used at specific levels. For example, you can specify HIGHLY_SENSITIVE and CONFIDENTIAL labels with no groups, and a SENSITIVE label that does contain groups.

See Also:

Chapter 13, "Releasability Using Inverse Groups"

Industry Examples of Levels, Compartments, and Groups

Table 2-9 illustrates the flexibility of Oracle Label Security levels, compartments, and groups, by listing typical ways in which they can be implemented in various industries.

Table 2-9 Typical Levels, Compartments, and Groups, by Industry

Industry
Levels
Compartments
Groups

Business to Business

TRADE_SECRET

PROPRIETARY

COMPANY_CONFIDENTIAL

PUBLIC

MARKETING

FINANCIAL

SALES

PERSONNEL

AJAX_CORP

BILTWELL_CO

ACME_INC

ERSATZ_LTD

Financial Services

ACQUISITIONS

CORPORATE

CLIENT

OPERATIONS

INSURANCE

EQUITIES

TRUSTS

COMMERCIAL_LOANS

CONSUMER_LOANS

CLIENT

TRUSTEE

BENEFICIARY

MANAGEMENT

STAFF

Judicial

NATIONAL_SECURITY

SENSITIVE

PUBLIC

CIVIL

CRIMINAL

ADMINISTRATION

DEFENSE

PROSECUTION

COURT

Health Care

PRIMARY_PHYSICIAN

PATIENT_CONFIDENTIAL

PATIENT_RELEASE

PHARMACEUTICAL

INFECTIOUS_DISEASES

CDC

RESEARCH

NURSING_STAFF

HOSPITAL_STAFF

Defense

TOP_SECRET

SECRET

CONFIDENTIAL

UNCLASSIFIED

ALPHA

DELTA

SIGMA

UK

NATO

SPAIN

Label Syntax and Type

After defining the label components, you, as the administrator create data labels by combining particular sets of level, compartments, and groups.

You can use the Oracle Enterprise Manager graphical user interface or a command line procedure. Character string representations of labels use the following syntax:

LEVEL:COMPARTMENT1,...,COMPARTMENTn:GROUP1,...,GROUPn

The text string specifying the label can have a maximum of 4,000 characters, including alphanumeric characters, spaces, and underscores. The labels are case-insensitive. You can enter them in uppercase, lowercase, or mixed case, but the string is stored in the data dictionary and displayed in uppercase. A colon is used as the delimiter between components. It is not necessary to enter trailing delimiters in this syntax.

For example, you can create valid labels such as these:

SENSITIVE:FINANCIAL,CHEMICAL:EASTERN_REGION,WESTERN_REGION
CONFIDENTIAL:FINANCIAL:VP_GRP
SENSITIVE
HIGHLY_SENSITIVE:FINANCIAL
SENSITIVE::WESTERN_REGION

When a valid data label is created, two additional things occur:

The label is automatically designated as a valid data label. This functionality limits the labels that can be assigned to data. Oracle Label Security can also create valid data labels dynamically at run time, from those that are predefined in Oracle Internet Directory. Most users, however, prefer to create the labels manually in order to limit data label proliferation.

A numeric label tag is associated with the text string representing the label. It is this label tag, rather than the text string, that is stored in the policy label column of the protected table.

Note:

For Oracle Label Security installations that do not use Oracle Internet Directory, dynamic creation of valid data labels uses the TO_DATA_LABEL function. Its usage should be tightly controlled. Refer to "Inserting Labels Using TO_DATA_LABEL".

See Also:

"The Policy Label Column and Label Tags"

"Label Tags"

How Data Labels and User Labels Work Together

A user can access data only within the range of his or her own label authorizations. A user has:

Maximum and minimum levels

A set of authorized compartments

A set of authorized groups (and, implicitly, authorization for any subgroups)

For example, if a user is assigned a maximum level of SENSITIVE, then the user potentially has access to SENSITIVE, CONFIDENTIAL, and UNCLASSIFIED data. The user has no access to HIGHLY_SENSITIVE data.

Figure 2-4, "Example: Data Labels and User Labels" shows how data labels and user labels work together to provide access control in Oracle Label Security. While data labels are discrete, user labels are inclusive. Depending upon authorized compartments and groups, a user can potentially access data corresponding to all levels within his or her range.

Figure 2-4 Example: Data Labels and User Labels

As shown in the figure, User 1 can access the rows 2, 3, and 4 because her maximum level is HS. She has access to the FIN compartment, and her access to group WR hierarchically includes group WR_SAL. She cannot access row 1 because she does not have the CHEM compartment. (A user must have authorization for all compartments in a row's data label to be able to access that row.)

User 2 can access rows 3 and 4. His maximum level is S, which is less than HS in row 2. Although he has access to the FIN compartment, he only has authorization for group WR_SAL. So, he cannot access row 1.

Figure 2-5, "How Label Components Interrelate" shows how data pertaining to an organizational hierarchy fits into data levels and compartments.

Figure 2-5 How Label Components Interrelate

For example, the UNITED_STATES group includes three subgroups: EASTERN_REGION, CENTRAL_REGION, and WESTERN_REGION. The WESTERN_REGION subgroup is further subdivided into CALIFORNIA and NEVADA. For each group and subgroup, there may be data belonging to some of the valid compartments and levels within the database. So, there may be SENSITIVE data that is FINANCIAL, within the CALIFORNIA subgroup.

Note that data is generally labeled with a single group whereas users' labels form a hierarchy. If users have a particular group, then that group may implicitly include child groups. This way a user associated with the UNITED_STATES group has access to all data, but a user associated with CALIFORNIA would have access to data pertaining to only that subgroup.

Administering Labels

Oracle Label Security provides administrative interfaces to define and manage the labels used in a database. You define labels in Oracle Database using Oracle Label Security packages or by using Oracle Enterprise Manager. Initially, an administrator must define the levels, compartments, and groups that compose the labels, and then, the user can define the set of valid data labels for the contents of the database.

The administrator can apply a policy to individual tables in the database or to entire application schemas. Finally, the administrator assigns to each database user the label components (and privileges, if needed) required for the user's job function.

3 Understanding Access Controls and Privileges

This chapter examines the access controls and privileges that determine the type of access users can have to labeled rows.

See Chapter 2, "Understanding Data Labels and User Labels" for an introductions to the concept of labels (with their levels, compartments, and groups) and the basic notion of access control based on the row data label and the user label.

This chapter contains these sections:

Introducing Access Mediation

Understanding Session Label and Row Label

Understanding User Authorizations

Evaluating Labels for Access Mediation

Using Oracle Label Security Privileges

Working with Multiple Oracle Label Security Policies

Introducing Access Mediation

To access data protected by an Oracle Label Security policy, a user must have authorizations based on the labels defined for the policy. Figure 3-1, "Relationships Between Users, Data, and Labels" illustrates the relationships between users, data, and labels.

Data labels specify the sensitivity of data rows.

User labels provide the appropriate authorizations to users.

Access mediation between users and rows of data depends on users' labels.

Figure 3-1 Relationships Between Users, Data, and Labels

Note:

Oracle Label Security enforcement options affect how access controls apply to tables and schemas. This chapter assumes that all policy enforcement options are in effect.

See Also:

For more information, Refer to "Choosing Policy Options"

Understanding Session Label and Row Label

This section introduces the basic user labels.

The Session Label

The Row Label

Session Label Example

The Session Label

Each Oracle Label Security user has a set of authorizations that include:

A maximum and minimum level

A set of authorized compartments

A set of authorized groups

For each compartment and group, a specification of read-only access, or read/write access

The administrator also specifies the user's initial session label when setting up these authorizations for the user.

The session label is the particular combination of level, compartments, and groups at which a user works at any given time. The user can change the session label to any combination of components for which the user is authorized.

See Also:

"SA_SESSION Session Management PL/SQL Package"

The Row Label

When a user writes data without specifying its label, a row label is assigned automatically, using the user's session label. However, the user can set the label for the written row, within certain restrictions on the components of the label he specifies.

The level of this label can be set to any level within the range specified by the administrator. For example, it can be set to the level of the user's current session label down to the user's minimum level. However, the compartments and groups for this row's new label are more restricted. The new label can include only those compartments and groups contained in the current session label and, among those, only the ones for which the user has write access.

When the administrator sets up the user authorizations, he or she also specifies an initial default row label.

See Also:

"SA_USER_ADMIN User, Levels, Groups, and Compartments PL/SQL Package"

"SA_SESSION Session Management PL/SQL Package"

Session Label Example

The session label and the row label can fall anywhere within the range of the user's level, compartment, and group authorizations. In Figure 3-2, "User Session Label", the user's maximum level is SENSITIVE and the minimum level is UNCLASSIFIED. However, his default session label is C:FIN,OP:WR. In this example, the administrator has set the user's session label so that the user connects to the database at the CONFIDENTIAL level.

Similarly, although the user is authorized for compartments FIN and OP, and group WR, the administrator could set the session label so that the user connects with only compartment FIN and group WR.

See Also:

"SA_USER_ADMIN.SET_COMPARTMENTS Procedure"

"SA_USER_ADMIN.ALTER_COMPARTMENTS Procedure"

Figure 3-2 User Session Label

Understanding User Authorizations

There are two types of user authorizations:

Authorizations Set by the Administrator

Computed Session Labels

Authorizations Set by the Administrator

The administrator explicitly sets a number of user authorizations:

Authorized Levels

Authorized Compartments

Authorized Groups

Authorized Levels

The administrator explicitly sets the following level authorizations:

Table 3-1 Authorized Levels Set by the Administrator

Authorization
Meaning

User Max Level

The maximum ranking of sensitivity that a user can access during read and write operations

User Min Level

The minimum ranking of sensitivity that a user can access during write operations. The User Max Level must be equal to or greater than the User Min Level.

User Default Level

The level that is assumed by default when connecting to Oracle Database

User Default Row Level

The level that is used by default when inserting data into Oracle Database

For example, in Oracle Enterprise Manager, the administrator might set the following level authorizations for user Joe:

Type | Short Name | Long Name | Description
Maximum | HS | HIGHLY_SENSITIVE | User's highest level
Minimum | P | PUBLIC | User's lowest level
Default | C | CONFIDENTIAL | User's default level
Row | C | CONFIDENTIAL | Row level on INSERT

Authorized Compartments

The administrator specifies the list of compartments that a user can place in their session label. Write access must be explicitly given for each compartment. A user cannot directly insert, update, or delete a row that contains a compartment that she does not have authorization to write.

For example, in Oracle Enterprise Manager, the administrator might set the following compartment authorizations for user Joe:

Short Name | Long Name | WRITE | DEFAULT | ROW
CHEM | CHEMICAL | YES | YES | NO
FINCL | FINANCIAL | YES | YES | NO
OP | OPERATIONAL | YES | YES | YES

Figure 3-3 Setting Up Authorized Compartments In Enterprise Manager

In Figure 3-3, "Setting Up Authorized Compartments In Enterprise Manager", the row designation indicates whether the compartment should be used as part of the default row label for newly inserted data. Note also that the policy option must be in effect for this setting to be valid.

Authorized Groups

The administrator specifies the list of groups that a user can place in session label. Write access must be explicitly given for each group listed.

For example, in Oracle Enterprise Manager, the administrator might set the following group authorizations:

Short Name | Long Name | WRITE | DEFAULT | ROW | Parent
WR_HR | WR_HUMAN_RESOURCES | YES | YES | YES | WR
WR_AP | WR_ACCOUNTS_PAYABLE | YES | YES | NO | WR_FIN
WR_AR | WR_ACCOUNTS_RECEIVABLE | YES | YES | NO | WR_FIN

Figure 3-4 Setting Up Authorized Groups in Enterprise Manager

In Figure 3-4, "Setting Up Authorized Groups in Enterprise Manager", the row designation indicates whether the group should be used as part of the default row label for newly inserted data. Note also that the LABEL_DEFAULT policy option must be in effect for this setting to be valid.

See Also:

"LABEL_DEFAULT: Using the Session's Default Row Label"

Computed Session Labels

Oracle Label Security automatically computes a number of labels based on the value of the session label. These include:

Table 3-2 Computed Session Labels

Computed Label
Definition

Maximum Read Label

The user's maximum level combined with any combination of compartments and groups for which the user is authorized.

Maximum Write Label

The user's maximum level combined with the compartments and groups for which the user has been granted write access.

Minimum Write Label

The user's minimum level.

Default Read Label

The single default level combined with compartments and groups that have been designated as default for the user.

Default Write Label

A subset of the default read label, containing the compartments and groups to which the user has been granted write access. The level component is equal to the level default in the read label. This label is automatically derived from the read label based on the user's write authorizations.

Default Row Label

The combination of components between the user's minimum write label and the maximum write label, which has been designated as the default value for the data label for inserted data.

See Also:

"Computed Labels with Inverse Groups"

Evaluating Labels for Access Mediation

When a table is protected by an Oracle Label Security policy, the user's label components are compared to the row's label components to determine whether the user can access the data. In this way, Oracle Label Security evaluates whether the user is authorized to perform the requested operation on the data in the row. This section explains the rules and options by which user access is mediated. It contains these topics:

Introducing Read/Write Access

The Oracle Label Security Algorithm for Read Access

The Oracle Label Security Algorithm for Write Access

Introducing Read/Write Access

Although data labels are stored in a column within data records, information about user authorizations is stored in relational tables. When a user logs on, the tables are used to dynamically generate user labels for use during the session.

Difference Between Read and Write Operations

Two fundamental types of access mediation on Data Manipulation language (DML) operations exist, within protected tables:

Read access

Write access

The user has a maximum authorization for the data he or she can read; the user's write authorization is a subset of that. The minimum write level controls the user's ability to disseminate data by lowering its sensitivity. The user cannot write data with a level lower than the minimum level the administrator assigned to this user.

In addition, there are separate lists of compartments and groups for which the user is authorized; that is, for which the user has at least read access. An access flag indicates whether the user can also write to individual compartments or groups.

Propagation of Read/Write Authorizations on Groups

When groups are organized hierarchically, a user's assigned groups include all subgroups that are subordinate to the group to which she belongs. In this case, the user's read/write authorizations on a parent group flow down to all the subgroups.

Consider the parent group WESTERN_REGION, with three subgroups as illustrated in Figure 3-5, "Subgroup Inheritance of Read/Write Access". If the user has read access to WESTERN_REGION, then the read access is also granted to the three subgroups. The administrator can give the user write access to subgroup WR_FINANCE, without granting write access to the WESTERN_REGION parent group (or to the other subgroups). On the other hand, if the user has read/write access on WESTERN_REGION, then read/write access is also granted on all of the subgroups subordinate to it in the tree.

Write authorization on a group does not give a user write authorization on the parent group. If a user has read-only access to WESTERN_REGION and WR_FINANCE, then the administrator can grant write access to WR_ACCOUNTS_RECEIVABLE, without affecting the read-only access to the higher-level groups.

Figure 3-5 Subgroup Inheritance of Read/Write Access

See Also:

"How Inverse Groups Work"

The Oracle Label Security Algorithm for Read Access

The READ_CONTROL enforcement determines the ability to read data in a row. The following rules are used, in the sequence listed, to determine a user's read access to a row of data:

The user's level must be greater than or equal to the level of the data.

The user's label must include at least one of the groups that belong to the data (or the parent group of one such subgroup).

The user's label must include all the compartments that belong to the data.

If the user's label passes these tests, then it is said to dominate the row's label.

Note that there is no notion of read or write access connected with levels. This is because the administrator specifies a range of levels (minimum to maximum) within which a user can potentially read and write. At any time, the user can read all data equal to or less than the current session level. No privileges (other than FULL) allow the user to write below the minimum authorized level.

The label evaluation process proceeds from levels to groups to compartments, as illustrated in Figure 3-6, "Label Evaluation Process for Read Access". Note that if the data label is null or invalid, then the user is denied access.

Figure 3-6 Label Evaluation Process for Read Access

As a read access request comes in, Oracle Label Security evaluates each row to determine the following:

Is the user's level equal to, or greater than, the level of the data?

If so, does the user have access to at least one of the groups present in the data label?

If so, does the user have access to all the compartments present in the data label? (That is, are the data's compartments a subset of the user's compartments?)

If the answer is no at any stage in this evaluation process, then Oracle Label Security denies access to the row and moves on to evaluate the next row of data.

Oracle Label Security policies allow user sessions to read rows at their label and below, which is called reading down. Sessions cannot read rows at labels that they do not dominate.

For example, if you are logged in at SENSITIVE:ALPHA,BETA, you can read a row labeled SENSITIVE:ALPHA because your label dominates that of the row. However, you cannot read a row labeled SENSITIVE:ALPHA,GAMMA because your label does not dominate that of the row.

Note that the user can gain access to the rows otherwise denied, if she or he has special Oracle Label Security privileges.

See Also:

"Privileges Defined by Oracle Label Security Policies"

"The Access Control Enforcement Options"

"Algorithm for Read Access with Inverse Groups"

The Oracle Label Security Algorithm for Write Access

In the context of Oracle Label Security, WRITE_CONTROL enforcement determines the ability to insert, update, or delete data in a row.

WRITE_CONTROL enables you to control data access with ever finer granularity. Granularity increases when compartments are added to levels. It increases again when groups are added to compartments. Access control becomes even more fine grained when you can manage the user's ability to write the data that he can read.

To determine whether a user can write a particular row of data, Oracle Label Security evaluates the following rules, in the order given:

The level in the data label must be greater than or equal to the user's minimum level and less than or equal to the user's session level.

When groups are present, the user's label must include at least one of the groups with write access that appear in the data label (or the parent of one such subgroup). In addition, the user's label must include all the compartments in the data label.

When no groups are present, the user's label must have write access on all of the compartments in the data label.

To state tests 2 and 3 another way:

If the label has no groups, then the user must have write access on all the compartments in the label in order to write the data.

If the label does have groups and the user has write access to one of the groups, she only needs read access to the compartments in order to write the data.

Just as with read operations, the label evaluation process proceeds from levels to groups to compartments. Note that the user cannot write any data below the authorized minimum level, nor above the current session level. The user can always read below the minimum level.

The following figure illustrates how the process works with INSERT, UPDATE, and DELETE operations. Note that if the data label is null or invalid, then the user is denied access.

Figure 3-7 Label Evaluation Process for Write Access

As an access request comes in, Oracle Label Security evaluates each row to determine the following:

Is the data's level equal to, or less than the level of the user?

Is the data's level equal to, or greater than the user's minimum level?

If the data's level falls within the foregoing bounds, then does the user have write access to at least one of the groups present in the data label?

If so, does the user have access to all the compartments with at least read access that are present in the data label?

If there are no groups but there are compartments, then does the user have write access to all of the compartments?

If the answer is no at any stage in this evaluation process, then Oracle Label Security denies access to the row, and moves on to evaluate the next row of data.

Consider a situation in which your session label is S:ALPHA,BETA but you have write access to only compartment ALPHA. In this case, you can read a row with the label S:ALPHA,BETA but you cannot update it.

In summary, write access is enforced on INSERT, UPDATE and DELETE operations upon the data in the row.

In addition, each user may have an associated minimum level below which the user cannot write. The user cannot update or delete any rows labeled with levels below the minimum, and cannot insert a row with a row label containing a level less than the minimum.

See Also:

"The Access Control Enforcement Options"

"Algorithm for Write Access with Inverse Groups"

Using Oracle Label Security Privileges

This section introduces the Oracle Label Security database and row label privileges:

Privileges Defined by Oracle Label Security Policies

Special Access Privileges

Special Row Label Privileges

System Privileges, Object Privileges, and Policy Privileges

Privileges Defined by Oracle Label Security Policies

Oracle Label Security supports special privileges that allow authorized users to bypass certain parts of the policy.

Table 3-3 summarizes the full set of privileges that can be granted to users or trusted stored program units. Each privilege is more fully discussed after the table.

Table 3-3 Oracle Label Security Privileges

Security Privilege
Explanation

READ

Allows read access to all data protected by the policy

FULL

Allows full read and write access to all data protected by the policy

COMPACCESS

Allows a session access to data authorized by the row's compartments, independent of the row's groups

PROFILE_ACCESS

Allows a session to change its labels and privileges to those of a different user

WRITEUP

Allows users to set or raise only the level, within a row label, up to the maximum level authorized for the user. (Active only if LABEL_UPDATE is active.)

WRITEDOWN

Allows users to set or lower the level, within a row label, to any level equal to or greater than the minimum level authorized for the user. (Active only if LABEL_UPDATE is active.)

WRITEACROSS

Allows a user to set or change groups and compartments of a row label, but does not allow changes to the level. (Active only if LABEL_UPDATE is active.)

Special Access Privileges

A user's authorizations can be modified with any of four privileges:

READ Privilege

FULL Privilege

COMPACCESS Privilege

PROFILE_ACCESS Privilege

READ Privilege

A user with the READ privilege can read all data protected by the policy, regardless of the authorizations or session label. The user does not even need to have label authorizations. Note, in addition, that a user with READ privilege can write to any data rows for which he or she has write access, based on any label authorizations.

Note:

Access mediation is still enforced on UPDATE, INSERT, and DELETE operations.

This privilege is useful for system administrators who need to export data but who should not be allowed to change data. It is also useful for people who must run reports and compile information but not change data. The READ privilege enables optimal performance on SELECT statements, because the system behaves as though the Oracle Label Security policy were not even present.

FULL Privilege

The FULL privilege has the same effect and benefits as the READ privilege, with one difference. A user with the FULL privilege can also write to all the data. For a user with the FULL privilege, the READ and WRITE algorithms are not enforced.

Note that Oracle system and object authorizations are still enforced. For example, a user must still have SELECT on the application table. The FULL authorization turns off the access mediation check at the individual row level.

COMPACCESS Privilege

The COMPACCESS privilege allows a user to access data based on the row label's compartments, independent of the row label's groups. If a row label has no compartments, then access is determined by the group authorizations. However, when compartments do exist and access to them is authorized, then the group authorization is bypassed. This allows a privileged user whose label matches all the compartments of the data to access any data in any particular compartment, independent of what groups may own or otherwise be allowed access to the data.

Figure 3-8, "Label Evaluation Process for Read Access with COMPACCESS Privilege" shows the label evaluation process for read access with the COMPACCESS privilege. Note that if the data label is null or invalid, then the user is denied access.

Figure 3-8 Label Evaluation Process for Read Access with COMPACCESS Privilege

Figure 3-9, "Label Evaluation Process for Write Access with COMPACCESS Privilege" shows the label evaluation process for write access with COMPACCESS privilege. Note that if the data label is null or invalid, then the user is denied access.

Figure 3-9 Label Evaluation Process for Write Access with COMPACCESS Privilege

PROFILE_ACCESS Privilege

The PROFILE_ACCESS privilege allows a session to change its session labels and session privileges to those of a different user. This is a very powerful privilege, because the user can potentially become a user with FULL privileges. This privilege cannot be granted to a trusted stored program unit.

Special Row Label Privileges

Once the label on a row has been set, Oracle Label Security privileges are required to modify the label.

Note that the LABEL_UPDATE enforcement option must be on for these label modification privileges to be enforced. When a user updates a row label, the new label and old label are compared, and the required privileges are determined.

The special row label privileges include:

WRITEUP Privilege

WRITEDOWN Privilege

WRITEACROSS Privilege

WRITEUP Privilege

The WRITEUP privilege enables the user to raise the level of data within a row, without compromising the compartments or groups. The user can raise the level up to his or her maximum authorized level.

For example, an authorized user can raise the level of a data row that has a level lower than his own minimum level. If a row is UNCLASSIFIED and the user's maximum level is SENSITIVE, then the row's level can be raised to SENSITIVE. It can be raised above the current session level, but it cannot change the compartments.

WRITEDOWN Privilege

The WRITEDOWN privilege enables the user to lower the level of data within a row, without compromising the compartments or groups. The user can lower the level to any level equal to or greater than his or her minimum authorized level.

WRITEACROSS Privilege

The WRITEACROSS privilege allows the user to change the compartments and groups of data, without altering its sensitivity level. This guarantees, for example, that SENSITIVE data remains at the SENSITIVE level, but at the same time enables the data's dissemination to be managed.

It lets the user change compartments and groups to anything that is currently defined as a valid compartment or group within the policy, while maintaining the level. With the WRITEACROSS privilege, a user with read access to one group (or more) can write to a different group without explicitly being given access to it.

System Privileges, Object Privileges, and Policy Privileges

Remember that Oracle Label Security privileges are different from the standard Oracle Database system and object privileges.

Table 3-4 Types of Privilege

Source
Privileges
Definition

Oracle Database

System Privileges

The right to run a particular type of SQL statement

Object Privileges

The right to access another user's object

Oracle Label Security

Policy Privileges

The ability to bypass certain parts of the label security policy

Oracle Database enforces the discretionary access control privileges that a user has been granted. By default, a user has no privileges except those granted to the PUBLIC user group. A user must explicitly be granted the appropriate privilege to perform an operation.

For example, to read an object in Oracle Database, you must either be the object's owner, or be granted the SELECT privilege on the object, or be granted the SELECT ANY TABLE system privilege. Similarly, to update an object, you must either be the object's owner, or be granted the UPDATE privilege on the object, or be granted the UPDATE ANY TABLE privilege.

See Also:

Oracle Database Security Guide for more information about managing system privileges and object privileges

Access Mediation and Views

Prior to accessing data through a view, the users must have the appropriate system and object privileges on the view. If the underlying table (on which the view is based) is protected by Oracle Label Security, then the user of the view must have authorization from Oracle Label Security to access specific rows of labeled data.

Access Mediation and Program Unit Execution

In Oracle Database, if User1 executes a procedure that belongs to User2, the procedure runs with User2's system and object privileges. However, any procedure executed by User1 runs with User1's own Oracle Label Security labels and privileges. This is true even when User1 executes stored program units owned by other users.

Figure 3-10, "Stored Program Unit Execution" illustrates this process:

Stored program units run with the DAC privileges of the procedure's owner (User2).

In addition, stored program units accessing tables protected by Oracle Label Security mediate access to data rows based on the label attached to the row, and the Oracle Label Security labels and privileges of the invoker of the procedure (User1).

Figure 3-10 Stored Program Unit Execution

Stored program units can become trusted when an administrator assigns them Oracle Label Security privileges. A stored program unit can be run with its own autonomous Oracle Label Security privileges rather than those of the user who calls it. For example, if you possess no Oracle Label Security privileges in your own right but run a stored program unit that has the WRITEDOWN privilege, then you can update labels. In this case, the privileges used are those of the stored program unit, and not your own.

Trusted program units can encapsulate privileged operations in a controlled manner. By using procedures, packages, and functions with assigned privileges, you may be able to access data that your own labels and privileges would not authorize. For example, to perform aggregate functions over all data in a table, not just the data visible to you, you might use a trusted program set up by an administrator. This way program units can thus perform operations on behalf of users, without the need to grant privileges directly to users.

See Also:

Chapter 9, "Administering and Using Trusted Stored Program Units"

Access Mediation and Policy Enforcement Options

An administrator can choose from among a set of policy enforcement options when applying an Oracle Label Security policy to individual tables. These options enable enforcement to be tailored differently for each database table. In addition to the access controls based on the labels, a SQL predicate can also be associated with each table. The predicate can further define which rows in the table are accessible to the user. Policy enforcement options and predicates are discussed in Chapter 8, "Implementing Policy Enforcement Options and Labeling Functions".

In cases where the label to be associated with a new or updated row should be automatically computed, an administrator can specify a labeling function when applying the policy. That function will thereafter always be invoked to provide the data labels written under that policy, because active labeling functions take precedence over any alternative means of supplying a label.

Except where noted, this guide assumes that all enforcement options are in effect.

See Also:

"Using a Labeling Function"

"SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure"

Working with Multiple Oracle Label Security Policies

This section describes aspects of using multiple policies.

Multiple Oracle Label Security Policies in a Single Database

Several Oracle Label Security policies may be protecting data in a single database. Each defined policy is associated with a set of labels used only by that policy. Data labels are constrained by the set of defined labels for each policy.

Each policy may protect a different table, but multiple policies can also apply to a single table. To access data, you must have label authorizations for all policies protecting that data. To access any particular row, you must be authorized by all policies protecting the table containing your desired rows. If you require privileges, then you may need privileges for all of the policies affecting your work.

Multiple Oracle Label Security Policies in a Distributed Environment

If you work in a distributed environment, where multiple databases may be protected by the same or different Oracle Label Security policies, your remote connections will also be controlled by Oracle Label Security.

See Also:

Chapter 11, "Using Oracle Label Security with a Distributed Database"

Part II

Using Oracle Label Security Functionality

This part presents the following chapters, each discussing the indicated contents:

Chapter 5, "Creating an Oracle Label Security Policy"

Chapter 6, "Working with Labeled Data"

Chapter 7, "Oracle Label Security Using Oracle Internet Directory"

4 Getting Started with Oracle Label Security

This chapter contains:

Registering Oracle Label Security with an Oracle Database

Enabling the LBACSYS Oracle Label Security User Account

Logging into Cloud Control or SQL*Plus for Oracle Label Security

Registering Oracle Label Security with an Oracle Database

This section contains:

About Registering Oracle Label Security

Checking if Oracle Label Security Has Been Registered and Enabled

Registering and Enabling Oracle Label Security from SQL*Plus

Registering and Enabling Oracle Label Security Using DBCA

About Registering Oracle Label Security

When you install Oracle Database, by default Oracle Label Security is not enabled. You must register it with the database. Afterwards, you must enable the default Oracle Label Security user account, LBACSYS.

After you register Oracle Label Security, you can disable and re-enable it when necessary.

If you are using a multitenant environment, then only register Oracle Label Security in the pluggable databases (PDBs) in which you plan to create Oracle Label Security policies. Because Oracle Label Security is not designed to protect data dictionary objects, you cannot create policies in the root.

Checking if Oracle Label Security Has Been Registered and Enabled

Log into the database instance as user SYS with the SYSDBA administrative privilege.

sqlplus sys as sysdba
Enter password: password

If you are using a multitenant environment, then connect to the appropriate PDB.

For example, to connect to the PDB hrpdb:

CONNECT SYS@hrpdb AS SYSDBA
Enter password: password

To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

Run the following query to find if Oracle Label Security has been registered:

SELECT STATUS FROM DBA_OLS_STATUS WHERE NAME = 'OLS_CONFIGURE_STATUS';

If the output is TRUE, then Oracle Label Security is registered. If the output is FALSE, then you must register Oracle Label Security.

If Oracle Label Security has been registered, then check if it is enabled. The PARAMETER column is case sensitive, so use the case shown here.

SELECT VALUE FROM V$OPTION WHERE PARAMETER = 'Oracle Label Security';

If it returns TRUE, then Oracle Label Security is enabled. Go to "Enabling the LBACSYS Oracle Label Security User Account". If the output is FALSE, then you must enable Oracle Label Security.

Note:

If Oracle Label Security is registered, it may or may not be enabled. You can query the V$OPTION dynamic view to find if it is enabled. See "Checking if Oracle Label Security Is Enabled or Disabled" for more information.

Registering and Enabling Oracle Label Security from SQL*Plus

Log into the database instance as user SYS with the SYSDBA administrative privilege.

For example:

sqlplus sys as sysdba
Enter password: password

If you are using a multitenant environment, then connect to the appropriate PDB.

For example, to connect to the PDB hrpdb:

CONNECT SYS@hrpdb AS SYSDBA
Enter password: password

To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

Register and enable Oracle Label Security as follows.

EXEC LBACSYS.CONFIGURE_OLS; -- This procedure registers Oracle Label Security.
EXEC LBACSYS.OLS_ENFORCEMENT.ENABLE_OLS; -- This procedure enables it.

Connect as user SYS with the SYSOPER privilege.

CONNECT SYS AS SYSOPER -- Or, CONNECT SYS@hrpdb AS SYSOPER
Enter password: password

Restart the database.

For example:

SHUTDOWN IMMEDIATE
STARTUP

Registering and Enabling Oracle Label Security Using DBCA

You can both register and enable Oracle Label Security using Database Configuration Assistant.

Start Database Configuration Assistant (DBCA).

UNIX: Run the following command:

$ORACLE_HOME/bin/dbca

Windows: From the Start menu, click All Programs. Then click Oracle - ORACLE_HOME, then Configuration and Migration Tools, and then Database Configuration Assistant.

The Welcome screen appears.

Click Next.

The Operations screen appears.

Select Configure Database Options. Click Next.

The Database screen appears.

From the list, select the database where you need to configure and enable OLS. Click Next.

The Database Content screen appears.

Select Oracle Label Security. Click Next.

The Connection Mode screen appears.

Select either Dedicated Server Mode or Shared Server Mode. Click Finish.

A dialog box is displayed informing you that the operation will require the database to be restarted.

Click OK.

A confirmation dialog box is displayed.

Click OK.

The DBCA progress screen is displayed.

After the operation is complete, you are prompted to perform another operation. Click No to exit DBCA.

Enabling the LBACSYS Oracle Label Security User Account

After you complete the registration process, the default user account, LBACSYS, is granted the LBAC_DBA database role, which provides the privileges necessary to manage Oracle Label Security. By default, LBACSYS is created as a locked account with its password expired.

Log into the database instance as a user who has been granted the ALTER USER system privilege (for example, the SYSTEM user).

For example:

sqlplus system -- Or, sqlplus system@hrpdb for the hrpdb pluggable database (PDB)
Enter password: password

If Oracle Database Vault is enabled, then log in as a user who has been granted the DV_ACCTMGR role.

Enter this statement:

ALTER USER LBACSYS ACCOUNT UNLOCK IDENTIFIED BY password;

Replace password with a password that is secure. See Oracle Database Security Guide for the minimum requirements for creating passwords.

After you unlock user LBACSYS and provide a password, as a good practice, you may want to reserve this account as a back-up user account. For day-to-day use, consider granting the LBAC_DBA database role to trusted users who you want to administer Oracle Label Security.

If you plan to use Enterprise Manager Cloud Control to administer Oracle Label Security, then ensure that any users to whom you have granted the LBAC_DBA role also have the SELECT ANY DICTIONARY privilege. By default, the LBACSYS user already has this privilege.

Logging into Cloud Control or SQL*Plus for Oracle Label Security

This section contains:

Logging into Oracle Label Security from Enterprise Manager Cloud Control

Logging into Oracle Label Security from SQL*Plus

Logging into Oracle Label Security from Enterprise Manager Cloud Control

From Enterprise Manager Cloud Control, you use the Oracle Label Security pages to create and manage Oracle Label Security policies.

To access the Oracle Label Security pages from Cloud Control:

Ensure that you have configured the Cloud Control target databases that you plan to use with Oracle Label Security.

See the Oracle Enterprise Manager online help and Oracle Enterprise Manager Advanced Configuration for more information about configuring target databases.

Point your browser to the Cloud Control login page.

For example:

https://myserver.example.com:7799/em

Log into Cloud Control as user SYSMAN.

In the Cloud Control home page, from the Targets menu, select Databases.

In the Databases page, select the link for the database to which you want to connect.

The Database home page appears.

From the Security menu, select Label Security.

The Database Login page appears.

Enter the following information:

Username: Enter the user name of a user who has been granted the LBAC_DBA database role, or enter LBACSYS.

Password: Enter the password.

Role: Select NORMAL from the list.

Save As: Select this check box if you want these credentials to be automatically filled in for you the next time that this page appears. The credentials are stored in Enterprise Manager in a secured manner. Access to these credentials depends on the user who is currently logged in.

Logging into Oracle Label Security from SQL*Plus

To use Oracle Label Security from SQL*Plus, connect as user LBACSYS or as a user who has been granted the LBAC_DBA database role. To find if a user has been granted this role, query the GRANTEE and GRANTED_ROLE columns of the DBA_ROLE_PRIVS data dictionary view.

For example:

sqlplus psmith_ols -- Or, sqlplus psmith_ols@hrpdb for a PDB named hrpdb
Enter password: password

To find the available PDBs, query the DBA_PDBS data dictionary view. To check the current PDB, run the show con_name command.

5 Creating an Oracle Label Security Policy

This chapter contains:

About Creating Oracle Label Security Policies

Step 1: Create the Label Security Policy Container

Step 2: Create Data Labels for the Label Security Policy

Step 3: Authorize Users for the Label Security Policy

Step 4: Grant Privileges to Users and Trusted Stored Program Units

Step 5: Apply the Policy to a Database Table or Schema

Step 6: Add Policy Labels to Table Rows

Step 7: (Optional) Configure Auditing

Using Enterprise Manager Cloud Control to Create an OLS Policy

About Creating Oracle Label Security Policies

When you create an Oracle Label Security policy, you must follow these general steps:

Create a policy container that defines the policy name, the name of a column that Oracle Label Security will add to the tables to be protected, whether to hide this column, whether to enable the policy, and default enforcement options for the policy.

See "Step 1: Create the Label Security Policy Container" for more information.

Define the following attributes for the label: level of sensitivity, and optionally, compartments and groups to further filter the label sensitivity. Once you have the attributes defined, create the label itself and then associate these attributes with the label.

See "Step 2: Create Data Labels for the Label Security Policy".

Authorize users for the policy.

See "Step 3: Authorize Users for the Label Security Policy" for more information.

Grant privileges to these users or to trusted program units.

See "Step 4: Grant Privileges to Users and Trusted Stored Program Units" for more information.

Apply the policy to a database table. Alternatively, you can apply the policy to an entire schema.

See "Step 5: Apply the Policy to a Database Table or Schema" for more information.

Add the policy labels to the table rows. You must update the table that is being used for the policy.

See "Step 6: Add Policy Labels to Table Rows" for more information.

Optionally, configure audit settings for users.

See "Step 7: (Optional) Configure Auditing" for more information.

Step 1: Create the Label Security Policy Container

This section contains:

About the Label Security Policy Container

Creating a Label Policy Container

About the Label Security Policy Container

The Oracle Label Security policy container defines the policy name, the name of a column that Oracle Label Security will add to the tables to be protected, whether to hide this column, whether to enable the policy, and default enforcement options for the policy. The column that you add to the tables that you want to protect will include data labels (which you create later on) that are assigned to specific rows in a the table, based on values in a specific column.

You can create the policy container in Oracle Enterprise Manager Cloud Control, or use the SA_SYSDBA.CREATE_POLICY procedure.

Creating a Label Policy Container

Example 5-1 shows how to create a Label Security policy container using the SA_SYSDBA.CREATE_POLICY procedure. After you create the policy label container, a special role for this policy is created and granted to you. The role name is in the format policy_DBA. In this example, the role name is EMP_OLS_POL_DBA.

Example 5-1 Creating a Policy Using SA_SYSDBA.CREATE_POLICY

BEGIN
 SA_SYSDBA.CREATE_POLICY (
  policy_name      => 'emp_ols_pol',
  column_name      => 'ols_col',
  default_options  => 'read_control, update_control');
END;
/

See Also:

"Categories of Policy Enforcement Options" for a listing of the available policy options

"SA_SYSDBA.CREATE_POLICY Procedure"

"Creating the Label Security Policy Container Using Cloud Control"

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

Step 2: Create Data Labels for the Label Security Policy

This section contains:

About Data Labels

About Policy Level Sensitivity Components

Creating a Policy Level Component

About Policy Compartment Components

Creating a Policy Compartment Component

About Policy Group Components

Creating a Policy Group Component

About Associating the Policy Components with a Named Data Label

Associating the Policy Components with a Named Data Label

About Data Labels

A data label indicates the sensitivity of a database table row. Each label is a single attribute with multiple components that control the types of filtering to be used for user access.

Table 5-1 describes the different components of a data label.

Table 5-1 Sensitivity Data Label Components

Component
Description
Examples

Level

A single specification of the sensitivity of labeled data within the ordered ranks established

CONFIDENTIAL (1), SENSITIVE (2), HIGHLY_SENSITIVE (3)

Compartments

Zero or more categories associated with the labeled data

FINANCIAL, STRATEGIC, NUCLEAR

Groups

Zero or more identifiers for organizations owning or accessing the data

EASTERN_REGION, WESTERN_REGION

All data labels must contain a level component, but the compartment and group components are optional. Compartments and groups are a way of fine tuning access that users will have to the data. Valid characters for specifying all label components include alphanumeric characters, underscores, and spaces. (Leading and trailing spaces are ignored.) You must define the label components before you can create the data label itself.

You can use Cloud Control to create the label and its components for an existing policy. Alternatively, you can use the SA_COMPONENTS PL/SQL package to create the components, and the SA_LABEL_ADMIN package to create the data label.

See Also:

"SA_COMPONENTS Label Components PL/SQL Package"

About Policy Level Sensitivity Components

A level is a ranking that denotes the sensitivity of the information it labels. The more sensitive the information, the higher its level. The less sensitive the information, the lower its level.

Every label must include one level. Oracle Label Security permits up to 10,000 levels in a policy. For each level, you must define a numeric form, a long character form, and the required short character form.

Table 5-2 shows examples of levels.

Table 5-2 Policy Level Example

Numeric Form
Long Form
Short Form

40

HIGHLY_SENSITIVE

HS

30

SENSITIVE

S

20

CONFIDENTIAL

C

10

PUBLIC

P

Table 5-2 explains the numeric form, long form, and short form for levels.

Table 5-3 Forms of Specifying Levels

Form
Explanation

Numeric form, also called "tag"

The numeric form of the level can range from 0 to 9999. Sensitivity is ranked by this numeric value, so you must assign higher numbers to levels that are more sensitive, and lower numbers to levels that are less sensitive. In Table 5-2, 40 (HIGHLY_SENSITIVE) is a higher level than 30, 20, and 10.

Administrators should avoid using sequential numbers for the numeric form of levels. A good strategy is to use even increments (such as 50 or 100) between levels. You can then insert additional levels between two preexisting levels, at a later date.

Long form

The long form of the level name can contain up to 80 characters.

Short form

The short form can contain up to 30 characters.

Although you define both long and short names for the level (and for each of the other label components), only the short form of the name is displayed upon retrieval. When users manipulate the labels, they use only the short form of the component names.

Examples of levels can be names such as TOP_SECRET, SECRET, CONFIDENTIAL, and UNCLASSIFIED or TRADE_SECRET, PROPRIETARY, COMPANY_CONFIDENTIAL, PUBLIC_DOMAIN.

If you use only levels, a level 40 user (in this example) can access or alter any data row whose level is 40 or less.

Creating a Policy Level Component

Example 5-2 shows how to use the SA_COMPONENTS.CREATE_LEVEL procedure to create a data label level for an existing policy named emp_ols_pol.

Example 5-2 Creating a Policy Level Using SA_COMPONENTS.CREATE_LEVEL

BEGIN
 SA_COMPONENTS.CREATE_LEVEL (
   policy_name   => 'emp_ols_pol',
   level_num     => 40,
   short_name    => 'HS',
   long_name     => 'HIGHLY_SENSITIVE');
END;
/

See Also:

"SA_COMPONENTS.CREATE_LEVEL Procedure"

"Creating Policy Components Using Cloud Control"

About Policy Compartment Components

Compartments identify areas that describe the sensitivity of the labeled data, providing a finer level of granularity within a level. Compartments associate the data with one or more security areas. All data related to a particular project can be labeled with the same compartment.

Table 5-4 shows an example set of compartments.

Table 5-4 Policy Compartment Example

Numeric Form
Long Form
Short Form

85

FINANCIAL

FINCL

65

CHEMICAL

CHEM

45

OPERATIONAL

OP

Table 5-5 Forms of Specifying Compartments

Form
Explanation

Numeric form

The numeric form can range from 0 to 9999. It is unrelated to the numbers used for the levels. The numeric form of the compartment does not indicate greater or less sensitivity. Instead, it controls the display order of the short form compartment name in the label character string. For example, assume a label is created that has all three compartments listed in Table 5-4, and a level of SENSITIVE. When this label is displayed in string format, it looks like this:

S:OP,CHEM,FINCL

meaning SENSITIVE: OPERATIONAL, CHEMICAL, FINANCIAL

The display order follows the order of the numbers assigned to the compartments: 45 is lower than 65, and 65 is lower than 85. By contrast, if the number assigned to the FINCL compartment were 5, the character string format of the label would look like this:

S:FINCL,OP,CHEM

Long form

The long form of the compartment name scan have up to 80 characters.

Short form

The short form can contain up to 30 characters.

Compartments are optional. You can include up to 10,000 compartments for a label.

Not all labels must have compartments. For example, you can specify HIGHLY_SENSITIVE and CONFIDENTIAL levels with no compartments, and a SENSITIVE level that does contain compartments.

When you analyze the sensitivity of data, you may find that some compartments are only useful at specific levels.

Figure 5-1 shows how compartments can be used to categorize data.

Figure 5-1 Compartments in a Label

Here, compartments FINCL, CHEM, and OP are used with the level HIGHLY_SENSITIVE (HS). The label HIGHLY_SENSITIVE:FINCL, CHEM indicates a level of 40 with the two named compartments. Compartment FINCL is not more sensitive than CHEM, nor is CHEM more sensitive than FINCL. Note also that some data in the protected table may not belong to any compartment.

If you specify compartments, then a user whose level would normally permit access to a row's data will nevertheless be prevented from such access unless the user's label also contains all the compartments appearing in that row's label. For example, user hpreston, who is granted access to the HS level, could be granted access only to FINCL and CHEM but not to OP.

Creating a Policy Compartment Component

Example 5-3 shows how to use the SA_COMPONENTS.CREATE_COMPARTMENT procedure to create a compartment for an existing policy named emp_ols_pol.

Example 5-3 Creating a Compartment Using SA_COMPONENTS.CREATE_COMPARTMENT

BEGIN
  SA_COMPONENTS.CREATE_COMPARTMENT (
   policy_name     => 'emp_ols_pol',
   comp_num        => '85',
   short_name      => 'FINCL',
   long_name       => 'FINANCIAL');
END;
/

See Also:

"SA_COMPONENTS.CREATE_COMPARTMENT Procedure"

"Creating Policy Components Using Cloud Control"

About Policy Group Components

Groups identify organizations owning or accessing the data, such as EASTERN_REGION, WESTERN_REGION, WR_SALES. All data pertaining to a certain department can have that department's group in the label. Groups are useful for the controlled dissemination of data and for timely reaction to organizational change. When a company reorganizes, data access can change right along with the reorganization.

Groups are hierarchical. You can label data based upon your organizational infrastructure. A group can thus be associated with a parent group. For example, you can define a set of groups corresponding to the following organizational hierarchy:

Figure 5-2 Group Example

The WESTERN_REGION group includes three subgroups: WR_SALES, WR_HUMAN_RESOURCES, and WR_FINANCE. The WR_FINANCE subgroup is subdivided into WR_ACCOUNTS_RECEIVABLE and WR_ACCOUNTS_PAYABLE.

Table 5-6 shows how the organizational structure in this example can be expressed in the form of Oracle Label Security groups. The numeric form assigned to the groups affects display order only. You specify the hierarchy (that is, the parent and child relationships) separately. The first group listed, WESTERN_REGION, is the parent group of the remaining groups in the table.

Table 5-6 Group Example

Numeric Form
Long Form
Short Form
Parent Group

1000

WESTERN_REGION

WR

1100

WR_SALES

WR_SAL

WR

1200

WR_HUMAN_RESOURCES

WR_HR

WR

1300

WR_FINANCE

WR_FIN

WR

1310

WR_ACCOUNTS_PAYABLE

WR_AP

WR_FIN

1320

WR_ACCOUNTS_RECEIVABLE

WR_AR

WR_FIN

Table 5-7 shows the forms that you must use when you specify groups.

Table 5-7 Forms of Specifying Groups

Form
Explanation

Numeric form

The numeric form of the group can range from 0 to 9999, and it must be unique for each policy.

The numeric form does not indicate any kind of ranking. It does not indicate a parent-child relationship, or greater or less sensitivity. It only controls the display order of the short form group name in the label character string.

For example, assume that a label is created that has the level SENSITIVE, the compartment CHEMICAL, and the groups WESTERN_REGION and WR_HUMAN_RESOURCES as listed in Table 5-6. When displayed in string format, the label looks like this:

S:CHEM:WR,WR_HR

WR is displayed before WR_HR because 1000 comes before 1200.

Long form

The long form of the group name can contain up to 80 characters.

Short form

The short form can contain up to 30 characters.

Groups are optional. A label can contain up to 10,000 groups.

All labels do not need to have groups. When you analyze the sensitivity of data, you may find that some groups are only used at specific levels. For example, you can specify HIGHLY_SENSITIVE and CONFIDENTIAL labels with no groups, and a SENSITIVE label that does contain groups.

Creating a Policy Group Component

Example 5-4 shows how to use the SA_COMPONENTS.CREATE_GROUP procedure to create a data label group. The first CREATE_GROUP procedure creates the parent group, WR, and the second procedure associates a second group with the WR group by using the parent_name parameter.

Example 5-4 Creating a Group Using SA_COMPONENTS.CREATE_GROUP

BEGIN
 SA_COMPONENTS.CREATE_GROUP (
  policy_name     => 'emp_ols_pol',
  group_num       => 1000,
  short_name      => 'WR',
  long_name       => 'WESTERN_REGION');
END;
/
BEGIN
 SA_COMPONENTS.CREATE_GROUP (
  policy_name     => 'emp_ols_pol',
  group_num       => 1100,
  short_name      => 'WR_SAL',
  long_name       => 'WR_SALES',
  parent_name     => 'WR');
END;
/

See Also:

"SA_COMPONENTS.CREATE_GROUP Procedure"

"Creating Policy Components Using Cloud Control"

About Associating the Policy Components with a Named Data Label

After defining the data label components, you can create a data label itself by associating it with an existing level and optionally, compartments and groups.

You can use Oracle Enterprise Manager Cloud Control or the SA_LABEL_ADMIN.CREATE_LABEL procedure. Character string representations of labels use the following syntax:

level:compartment1,...,compartmentn:group1,...,groupn

The text string that specifies the label can have a maximum of 4,000 characters, including alphanumeric characters, spaces, and underscores. The label names are case-insensitive. You can enter them in uppercase, lowercase, or mixed case, but the string is stored in the data dictionary and displayed in uppercase. Separate each set of components with a colon. You do not need to enter trailing delimiters in this syntax.

For example, you can create valid labels such as these:

SENSITIVE:FINANCIAL,CHEMICAL:EASTERN_REGION,WESTERN_REGION
CONFIDENTIAL:FINANCIAL:VP_GRP
SENSITIVE
HIGHLY_SENSITIVE:FINANCIAL
SENSITIVE::WESTERN_REGION

Associating the Policy Components with a Named Data Label

Example 5-5 shows how to use the SA_LABEL_ADMIN.CREATE_LABEL procedure to create a data label for the emp_ols_pol policy.

Example 5-5 Creating a Data Label Using SA_LABEL_ADMIN.CREATE_LABEL

BEGIN
 SA_LABEL_ADMIN.CREATE_LABEL  (
  policy_name     => 'emp_ols_pol',
  label_tag       => '1310',
  label_value     => 'SENSITIVE:FINANCIAL,CHEMICAL:EASTERN_REGION,WESTERN_REGION',
  data_label      => TRUE);
END;
/

When you create a data label, two additional actions occur:

The label is automatically designated as a valid data label. This functionality limits the labels that can be assigned to data. Oracle Label Security can also create valid data labels dynamically at run time, from those that are predefined in Oracle Internet Directory. Most users, however, prefer to create the labels manually in order to limit data label proliferation.

A numeric label tag is associated with the text string representing the label. It is this label tag, rather than the text string, that is stored in the policy label column of the protected table.

Note:

For Oracle Label Security installations that do not use Oracle Internet Directory, dynamic creation of valid data labels uses the TO_DATA_LABEL function. Its usage should be tightly controlled. Refer to "Inserting Labels Using TO_DATA_LABEL".

See Also:

"SA_LABEL_ADMIN.CREATE_LABEL Procedure"

"Creating Data Labels for the Policy Using Cloud Control"

Step 3: Authorize Users for the Label Security Policy

This section contains:

About Authorizing Users for Label Security Policies

About Authorizing Levels

Authorizing a Level

About Authorizing Compartments

Authorizing a Compartment

About Authorizing Groups

Authorizing a Group

About Authorizing Users for Label Security Policies

When you authorize users, you enable them to have access to row data based on how the data labels are defined. First, you set the user's authorization for each level, compartment, and group that is associated with the label.

About Authorizing Levels

You can explicitly set the following level authorizations:

Table 5-8 Authorized Levels Set by the Administrator

Authorization
Meaning

User Max Level

The maximum ranking of sensitivity that a user can access during read and write operations

User Min Level

The minimum ranking of sensitivity that a user can access during write operations. The User Max Level must be equal to or greater than the User Min Level.

User Default Level

The level that is assumed by default when connecting to Oracle Database

User Default Row Level

The level that is used by default when inserting data into Oracle Database

For example, you might set the following level authorizations for user hpreston:

Type | Short Name | Long Name | Description
Maximum | HS | HIGHLY_SENSITIVE | User's highest level
Minimum | P | PUBLIC | User's lowest level
Default | C | CONFIDENTIAL | User's default level
Row | C | CONFIDENTIAL | Row level on INSERT

Authorizing a Level

Example 5-6 shows how to use the SA_USER_ADMIN.SET_LEVELS procedure to authorize user hpreston for an ols_admin_pol policy levels component. Note that when you specify the levels, you must always use the short names, not the long names.

Example 5-6 Authorizing a User Level with SA_USER_ADMIN.SET_LEVELS

BEGIN
 SA_USER_ADMIN.SET_LEVELS (
  policy_name   => 'ols_admin_pol',
  user_name     => 'hpreston',
  max_level     => 'HS',
  min_level     => 'P',
  def_level     => 'C',
  row_level     => 'C');
END;
/

See Also:

"SA_USER_ADMIN.SET_LEVELS Procedure"

"Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control"

About Authorizing Compartments

After you authorize the user for a specific level, you can optionally specify the list of compartments that the user can place in their session label. Write access must be explicitly given for each compartment. A user cannot directly insert, update, or delete a row that contains a compartment that the user does not have authorization to write.

For example, you could set the following compartment authorizations for user hpreston:

Short Name | Long Name | WRITE | DEFAULT | ROW
CHEM | CHEMICAL | YES | YES | NO
FINCL | FINANCIAL | YES | YES | NO
OP | OPERATIONAL | YES | YES | YES

Authorizing a Compartment

Example 5-7 shows how to use the SA_USER_ADMIN.SET_COMPARTMENTS procedure to authorize user hpreston for an ols_admin_pol policy compartments component. When you specify the compartments, you must use their short names, not their long names.

Example 5-7 Authorizing a User Compartment with SA_USER_ADMIN.SET_COMPARTMENTS

BEGIN
 SA_USER_ADMIN.SET_COMPARTMENTS (
  policy_name   => 'ols_admin_pol',
  user_name     => 'hpreston',
  read_comps    => 'FINCL',
  write_comps   => 'FINCL',
  def_comps     => 'FINCL',
  row_comps     => 'FINCL');
END;
/

After you have run this procedure, you can authorize the user for additional compartments by running the SA_USER_ADMIN.ADD_COMPARTMENTS procedure.

See Also:

"SA_USER_ADMIN.SET_COMPARTMENTS Procedure"

"SA_USER_ADMIN.ADD_COMPARTMENTS Procedure"

"Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control"

About Authorizing Groups

You can specify the list of groups that a user can place in session label. Write access must be explicitly given for each group listed.

For example, you could set the following group authorizations:

Short Name | Long Name | WRITE | DEFAULT | ROW | Parent
WR_HR | WR_HUMAN_RESOURCES | YES | YES | YES | WR
WR_AP | WR_ACCOUNTS_PAYABLE | YES | YES | NO | WR_FIN
WR_AR | WR_ACCOUNTS_RECEIVABLE | YES | YES | NO | WR_FIN

Authorizing a Group

Example 5-8 shows how to use the SA_USER_ADMIN.SET_GROUPS procedure to authorize user hpreston for an ols_admin_pol policy groups component. When you specify the groups, you must use the short name, not the long name.

Example 5-8 Authorizing a User Group with SA_USER_ADMIN.SET_GROUPS

BEGIN
 SA_USER_ADMIN.SET_GROUPS (
  policy_name   => 'ols_admin_pol',
  user_name     => 'hpreston',
  read_groups   => 'WR_AP',
  write_groups  => 'WR_AP',
  def_groups    => 'WR_AP',
  row_groups    => 'WR_AP');
END;
/

See Also:

"SA_USER_ADMIN.SET_GROUPS Procedure"

"Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control"

Step 4: Grant Privileges to Users and Trusted Stored Program Units

This section contains:

About Granting Privileges to Users and Trusted Program Units for the Policy

Granting Privileges to a User

Granting Privileges to a Trusted Program Unit

About Granting Privileges to Users and Trusted Program Units for the Policy

After you have authorized users for policy levels, compartments, and groups, you are ready to grant the user privileges.

Trusted program units are functions, procedures, or packages that are granted Oracle Label Security privileges. You create a trusted stored program unit in the same way that you create a standard procedure, function, or package, that is by using the CREATE PROCEDURE, CREATE FUNCTION, or CREATE PACKAGE and CREATE PACKAGE BODY statements. The program unit becomes trusted when you grant Oracle Label Security privileges to it.

Table 5-9 summarizes the privileges that can be granted to users or trusted stored program units.

Table 5-9 Oracle Label Security Privileges

Security Privilege
Explanation

READ

Allows read access to all data protected by the policy

FULL

Allows full read and write access to all data protected by the policy

COMPACCESS

Allows a session access to data authorized by the row's compartments, independent of the row's groups

PROFILE_ACCESS

Allows a session to change its labels and privileges to those of a different user

WRITEUP

Allows users to set or raise only the level, within a row label, up to the maximum level authorized for the user. (Active only if LABEL_UPDATE is active.)

WRITEDOWN

Allows users to set or lower the level, within a row label, to any level equal to or greater than the minimum level authorized for the user. (Active only if LABEL_UPDATE is active.)

WRITEACROSS

Allows a user to set or change groups and compartments of a row label, but does not allow changes to the level. (Active only if LABEL_UPDATE is active.)

Granting Privileges to a User

To grant a user privileges, use the SA_USER_ADMIN.SET_USER_PRIVS procedure.

Example 5-9 shows how to use the SA_USER_ADMIN.SET_USER_PRIVS procedure to grant user hpreston the WRITEDOWN privilege for an ols_admin_pol policy.

Example 5-9 Granting a Privileges to a User with SA_USER_ADMIN.SET_USER_PRIVS

BEGIN
 SA_USER_ADMIN.SET_USER_PRIVS(
  policy_name   => 'ols_admin_pol',
  user_name     => 'hpreston',
  privileges    => 'WRITEDOWN');
END;
/

See Also:

"SA_USER_ADMIN.SET_USER_PRIVS Procedure"

"Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control"

Granting Privileges to a Trusted Program Unit

Example 5-10 shows how to use the SA_USER_ADMIN.SET_PROG_PRIVS procedure to grant the READ privilege to the check_order_updates program unit.

Example 5-10 Granting Privileges to a Program Unit with SA_USER_ADMIN.SET_PROG_PRIVS

BEGIN
 SA_USER_ADMIN.SET_PROG_PRIVS (
  policy_name         => 'oe_ols_pol',
  schema_name         => 'oe',
  program_unit_name   => 'check_order_updates',
  privileges          => 'READ');
END;
/

See Also:

"SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

"Granting Privileges to Trusted Program Units Using Cloud Control"

Step 5: Apply the Policy to a Database Table or Schema

This section contains:

About Applying the Policy to a Database Table or Schema

Applying a Policy to a Schema

About Applying the Policy to a Database Table or Schema

When you apply a policy to a table, the policy is automatically enabled. To disable a policy is to turn off its protections, although it is still applied to the table. To enable a policy is to turn on and enforce its protections for a particular table or schema.

To remove a policy is to take it entirely away from the table or schema. Note, however, that the policy label column and the labels remain in the table unless you explicitly drop them.

You can alter the default policy enforcement options for future tables that may be created in a schema. This does not, however, affect policy enforcement options on existing tables in the schema.

To change the enforcement options on an existing table, you must first remove the policy from the table, make the desired changes, and then reapply the policy to the table.

After you have created the policy components and configured user authorizations, privileges, and auditing for them, you can apply the policy to a database table or to an entire schema.

When you apply the policy to a database table, in addition to the policy name and target schema table, you must specify the following information:

table_options: A comma-delimited list of policy enforcement options to be used for the table. If NULL, then the policy's default options are used.

label_function: A string calling a function to return a label value to use as the default. For example, my_label(:new.dept,:new.status) computes the label based on the new values of the DEPT and STATUS columns in the row.

predicate: An additional predicate to combine (using AND or OR) with the label-based predicate for READ_CONTROL

Note the following aspects of using Oracle Label Security policies with schemas:

If you apply a policy to an empty schema, then every time you create a table within that schema, the policy is applied. Once the policy is applied to the schema, the default options you choose are applied to every table added.

If you remove the policy from a table so that it is unprotected, and then run SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY, then the table will remain unprotected. If you wish to protect the table once again, then you must apply the policy to the table, or re-apply the policy to the schema.

If you apply a policy to a schema that already contains tables protected by the policy, then all future tables will have the new options that were specified when you applied the policy. The existing tables will retain the options they already had.

Applying a Policy to a Schema

Example 5-11 shows how to use the SA_POLICY_ADMIN.APPLY_TABLE_POLICY procedure to apply the ols_admin_pol policy to the HR.EMPLOYEES table.

Example 5-11 Applying a Policy with SA_POLICY_ADMIN.APPLY_TABLE_POLICY

BEGIN
 SA_USER_ADMIN.APPLY_TABLE_POLICY (
  policy_name    => 'ols_admin_pol',
  schema_name    => 'hr',
  table_name     => 'employees',
  table_options  => 'READ_CONTROL,WRITE_CONTROL,CHECK_CONTROL',
  label_function => ''hr.gen_emp_label(:new.deptartment_id,:new.salary',
  predicate      => NULL);
END;
/

Example 5-12 shows how to use the SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY procedure to apply a policy to an entire schema.

Example 5-12 Applying a Schema Policy with SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY

BEGIN
 SA_USER_ADMIN.APPLY_SCHEMA_POLICY (
  policy_name      => 'ols_admin_pol',
  schema_name      => 'hr',
  default_options  => NULL);
END;
/

See Also:

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

"SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure"

Table 8-2 for a listing of the default enforcement options

"Applying a Policy to a Database Table with Cloud Control"

Step 6: Add Policy Labels to Table Rows

This section contains:

About Adding Policy Labels to Table Rows

Adding a Policy Label to a Table Row

About Adding Policy Labels to Table Rows

After you have applied a policy to a table, you must add data labels to the rows in the table. These labels are stored in the policy label column that you created earlier in the table. The user updating the table must have the FULL security privilege for the policy. This user is normally the owner of the table.

Adding a Policy Label to a Table Row

To add data labels to a table, in SQL*Plus, enter an UPDATE statement using the following syntax:

UPDATE table_name
SET ols_column = CHAR_TO_LABEL('ols_policy','data_label')
WHERE UPPER(table_column) IN (column_data);

For example, suppose LABCSYS has created a policy called ACCESS_LOCATIONS and wants to add the label SENS to the cities Beijing, Tokyo, and Singapore in the HR.LOCATIONS table. The policy label column is called ROW_LABEL. The UPDATE statement is as follows:

UPDATE LOCATIONS
SET ROW_LABEL = CHAR_TO_LABEL('ACCESS_LOCATIONS','SENS')
WHERE UPPER(city) IN ('BEIJING', 'TOKYO', 'SINGAPORE');

If you want to check that your labels really made it into the table, run the following SELECT statement:

SELECT LABEL_TO_CHAR (ROW_LABEL) FROM LOCATIONS;

See Also:

"Applying Policy Labels to Table Rows Using Cloud Control"

Step 7: (Optional) Configure Auditing

This section contains:

About Configuring Auditing

Configuring Auditing

About Configuring Auditing

After you have authorized users for the policy and granted them privileges, you can configure auditing for each user. You also can configure auditing for the policy itself.

If unified auditing is not enabled, then use the procedures in this section to configure the auditing. If it is enabled, then you must create a unified audit policy, as described in Oracle Database Security Guide.

Table 5-10 describes the available auditing options.

Table 5-10 Auditing Options for Oracle Label Security

Option
Description

APPLY

Audits application of specified Oracle Label Security policies to tables and schemas

REMOVE

Audits removal of specified Oracle Label Security policies from tables and schemas

SET

Audits the setting of user authorizations, and user and program privileges

PRIVILEGES

Audits use of all policy-specific privileges

Configuring Auditing

Example 5-13 shows how to use the SA_USER_ADMIN.AUDIT procedure to configure auditing for user hpreston for the ols_admin_pol policy.

Example 5-13 Configuring Auditing with SA_AUDIT_ADMIN.AUDIT

BEGIN
 SA_USER_ADMIN.AUDIT(
  policy_name   => 'ols_admin_pol',
  users         => 'hpreston',
  audit_option  => 'REMOVE',
  audit_type    => 'BY ACCESS',
  success       => NULL);
END;
/

See Also:

"SA_AUDIT_ADMIN.AUDIT Procedure"

"Auditing Oracle Label Security Policies Using Cloud Control"

Using Enterprise Manager Cloud Control to Create an OLS Policy

This section contains:

Creating the Label Security Policy Container Using Cloud Control

Creating Policy Components Using Cloud Control

Creating Data Labels for the Policy Using Cloud Control

Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control

Granting Privileges to Trusted Program Units Using Cloud Control

Applying a Policy to a Database Table with Cloud Control

Applying Policy Labels to Table Rows Using Cloud Control

Auditing Oracle Label Security Policies Using Cloud Control

Creating the Label Security Policy Container Using Cloud Control

Log in to Cloud Control as the SYSTEM user.

To navigate to your database, select Databases from the Targets menu.

Click the database name in the list that appears.

The database page appears.

Under the Administration menu, select Security, Oracle Label Security. The Label Security Policies page appears.

You may be required to log in to the database with appropriate credentials. You can use the LBACSYS account credentials that you create in "Enabling the LBACSYS Oracle Label Security User Account".

Click Create to start creating a new label security policy. The Create Label Security Policy page appears.

Define the policy's name, label column, and the default policy enforcement options.

Name: Enter a name for the policy, for example, ACCESS_LOCATIONS.

Label Column: (Optional) Enter a name for the label column, for example, OLS_COLUMN. If you create an OLS policy without specifying the column name, the column name is auto-generated as Pol_name_COL.Later on, when you apply the policy to a table, the label column is added to that table. By default, the data type of the policy label column is NUMBER(10). You can also specify an existing table column of the NUMBER(10) data type as the label column.

Hide Label Column: Select to hide the column. When you first create the policy, you may want to disable Hide Label Column during the development phase of the policy. When the policy is satisfactory and ready for use by users, hide the column so that it is transparent to applications.

Enabled: Toggle to enable or disable the policy.

Default Policy Enforcement Options: The default policy enforcement options are used when the policy is applied. Ensure that these meet the needs of the application to which you are applying the policy.

Select from the following options:

Apply No Policy Enforcements (NO_CONTROL)

Apply Policy Enforcements

For all queries (READ_CONTROL)

For Insert operations (INSERT_CONTROL)

For Update Operations (UPDATE_CONTROL)

Use session's default label for label column update (LABEL_DEFAULT)

Operations that update the label column (LABEL_UPDATE)

Update and Insert operations so that they are read accessible (CHECK_CONTROL)

Click OK.

The new policy appears in the Oracle Label Security Policies page.

Creating Policy Components Using Cloud Control

After you have created a container for the policy and set enforcement options for it, you are ready to create components for the policy.

In the Oracle Label Security Policies page, select the policy you just created. Click Edit.

In the Edit Label Security Policy page, select the Label Components tab.

Click Add 5 Rows under Levels to add levels for the policy. Enter a Long Name, Short Name, and Numeric Tag for each level that you create. The numeric tag corresponds to the sensitivity of the level. To create more levels, you can click Add 5 Rows again. Use the same steps to create compartments and rows. For compartments and groups, the numeric tags do not correspond to sensitivity.

At a minimum, you must create one level, such as SECRET. Creating compartments and groups is optional.

The level numbers indicate the level of sensitivity for their corresponding labels. A greater number implies greater sensitivity. Select a numeric range that can be expanded later on, in case your security policy needs more levels. For example, if you have created levels PUBLIC (7000) and SENSITIVE (8000), and you now want to create an intermediate level called CONFIDENTIAL, then you can assign the numeric value 7500 to this level.

Compartments identify categories associated with data, providing a finer level of granularity within a level. For example, a single table might have data corresponding to different departments that you might like to separate using compartments. Compartments are optional.

Groups identify organizations owning or accessing the data. Groups are useful for the controlled dissemination of data and for timely reaction to organizational change. Groups are optional.

Click Apply.

Creating Data Labels for the Policy Using Cloud Control

In the Label Security Policies page, select the policy that needs to have labels linked to levels.

In the Actions box, select Data Labels. Click Go.

The Data Labels page appears.

Click Add.

The Create Data Label page appears.

Enter the following information:

Numeric Tag: Enter a number that uniquely identifies the label. This number should be unique across all policies.

Level: Select a level from the list.

You can optionally select Compartments to add to the label. To add compartments, click Add under Compartments. Select the compartments to be added to the label. Click Select to add the compartments.

Optionally, to add groups, click Add under Groups. Select the groups to be added to the label. Click Select to add the groups.

Click OK in the Create Data Label page.

The data label appears in the Data Labels page.

Repeat steps 3 to 7 to create more data labels.

Alternatively, you can use the SA_LABEL_ADMIN package to define label components for a policy.

See Also:

"SA_LABEL_ADMIN Label Management PL/SQL Package"

Authorizing, Granting Privileges, and Auditing Users for a Policy Using Cloud Control

This section contains:

In the Label Security Policies page, select the policy that needs authorization.

In the Actions box, select Authorization. Click Go.

The Create User page appears.

Add users as follows:

Under Database Users, click Add. In the Search and Select window, select users that you want and then click Select.

Under Non Database Users, click Add 5 Rows, and then add the user names of the non-database users that you want to add. Most application users are considered non-database users. A non-database user does not exist in the database. This can be any user name that meets the Oracle Label Security naming standards and can fit into the VARCHAR2(30) length field. However, be aware that Oracle Database does not automatically configure the associated security information for the non-database user when the application connects to the database. In this case, the application needs to call an Oracle Label Security function to assume the label authorizations of the specified user who is not a real database user.

In the Create User page, select the user that you want to authorize. Click Next. If you have multiple users that need the same authorizations, then select all users who need the same authorizations. Click Next.

The Privileges step appears.

Next, you can assign privileges to the user you selected in the preceding step. Privileges allow a database user to bypass certain controls enforced by the policy. Select the privileges you want to grant. Click Next.

If you do not want to assign any privileges to the user, then click Next without selecting any privileges.

The Labels, Compartments, and Groups step appears.

Next, to create the user label for the user: under Levels, use the flashlight icon to select data to enter for the following fields:

Maximum Level: Enter the highest level for read and write access for this user.

Minimum Level: Enter the lowest level for write access.

Default Level: Enter the default level when the user logs in.

This value is equal to or greater than the minimum level and equal to or less than the maximum level.

Row Level: Enter the level given to the row when user writes to the table.

Click Add under Compartments, to add compartments to the user label. Select the compartments to add. Click Select.

For each compartment that you add, you can select the following properties:

Write: Allows the user to write to data that has the compartment as part of its label

Default: Adds the compartment to the user's default session label

Row: Adds the compartment to the data label when the user writes to the table

Click Add under Groups, to add groups to the user label. Select the groups and click Select.

For each group that you add, you can select the following properties:

Write: Allows the user to write to data that has the group as part of its label

Default: Adds the group to the user's default session label

Row: Adds the group to the data label when the user writes to the table

Click Next.

The Audit step appears.

Select from the following audit options:

Policy Applied:

Audit On Success By audits successful application of the policy to a table or schema. Select ACCESS to audit by access or SESSION to audit by session.

Audit On Failure By audits failed application of the policy to a table or schema. Select ACCESS to audit by access or SESSION to audit by session.

Policy Removed:

Audit On Success By audits successful removal of the policy from a table or schema. Select ACCESS to audit by access or SESSION to audit by session.

Audit On Failure By audits failed removal of the policy from a table or schema. Select ACCESS to audit by access or SESSION to audit by session.

Labels And Privileges Set:

Audit On Success By audits successful setting of user authorizations and privileges. Select ACCESS to audit by access or SESSION to audit by session.

Audit On Failure By audits failed setting of user authorizations and privileges. Select ACCESS to audit by access or SESSION to audit by session.

All Policy Specific Privileges:

Audit On Success By audits successful use of policy privileges. Select ACCESS to audit by access or SESSION to audit by session.

Audit On Failure By audits failed use of policy privileges. Select ACCESS to audit by access or SESSION to audit by session.

Click Next.

You can review the policy authorization settings. Click Finish to create the policy authorization. Alternatively, you can click Back to modify the authorization settings.

Alternatively, you can use the SA_USER_ADMIN package to authorize users.

Granting Privileges to Trusted Program Units Using Cloud Control

In the Label Security Policies page, select the policy that needs authorization.

In the Actions box, select Authorization. Click Go.

The Authorization page appears.

Click the Trusted Program Units tab.

Click Add to add Oracle Label Security privileges for a procedure, function, or package.

The Create Program Unit page appears.

Enter the name of the procedure, function, or package, for which the privileges need to be granted, in the Program Unit field. You can also use the Search icon to search for the procedure, function, or package.

Select one or more policy-specific privileges that need to be granted to the program unit. Click OK.

The trusted program unit is added to the Authorizations page.

Alternatively, you can use the SA_USER_ADMIN package to authorize trusted program units.

See Also:

"SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

"SA_USER_ADMIN.SET_USER_PRIVS Procedure"

Chapter 9, "Administering and Using Trusted Stored Program Units"

Applying a Policy to a Database Table with Cloud Control

In the Label Security Policies page, select the policy that needs to be applied to a table.

Select Apply from the Actions box. Click Go.

The Apply page appears.

Select the Tables tab to apply the policy to a table.

Note:

Select the Schemas tab if you are applying the policy to a schema.The process is same as applying the policy to a table.

Click Create.

The Add Table page appears.

Next to the Table box, click the flashlight icon.

In the Search and Select window, enter the following information under Search:

Schema: Enter the name of the schema in which the table appears. Leaving this field empty displays tables in all schemas.

Name: Optionally, enter the name of the table. Leaving this box empty displays all the tables within the schema.

To narrow the search by using wildcards, use the percent (%) sign. For example, enter O% to search for all tables beginning with the letter O.

Select the table and click Select.

The Add Table page appears.

Enter the following information:

Policy Enforcement Options: Select enforcement options as needed. These options will apply to the table on top of the enforcement options that you selected when you created the policy in "Step 1: Create the Label Security Policy Container".

To make no change from those enforcement options, that is, to use the same enforcement options created earlier, select Use Default Policy Enforcement. To add more enforcement options, select from the other options listed.

Labeling Function: Optionally, specify a labeling function to automatically compute the label to be associated with a new or updated row. That function is always invoked thereafter to provide the data labels written under that policy, because active labeling functions take precedence over any alternative means of supplying a label.

Predicate: Optionally, specify an additional predicate to combine (using AND or OR) with the label-based predicate for READ_CONTROL.

Click OK.

Alternatively, you can use the SA_POLICY_ADMIN package to apply policies to tables and schemas.

See Also:

"SA_POLICY_ADMIN Policy Administration PL/SQL Package"

Applying Policy Labels to Table Rows Using Cloud Control

In the Label Security Policies page, select the policy, for example, ACCESS_LOCATIONS.

Select Authorization from the Actions box. Click Go.

The Authorization page appears.

Click Add.

The Create User page appears.

Under Database Users, click Add.

The Search and Select window appears.

Select the check box corresponding to the user that owns the table. Click Select.

The Create User page lists the user that was added.

Click Next.

The Privileges step appears.

Select the appropriate privileges for the user, and then click Next.

The Labels, Compartments, and Groups page appears.

Click Next.

The Audit step appears.

Click Next.

The Review step appears.

Click Finish.

Auditing Oracle Label Security Policies Using Cloud Control

In the Label Security Policies page, select the policy that you need to configure.

Click Edit.

The Edit Label Security Policy Settings page appears.

Click the Advanced tab. You can edit the audit settings under the Audit section.

Select Include Label In Audit trail under Audit Labels, if you wish to include user session labels in the audit table.

Select the Operation, to audit, under Audit Settings. You can choose from the following operations:

Policy Applied: Audits application of the policy to a table or schema.

Policy Removed: Audits removal of the policy from a table or schema.

Labels And Privileges Set: Audits setting of user authorizations and privileges.

All Policy Specific Privileges: Audits use of policy privileges.

Click Add under Policy Applied to add users that will be audited for the Operation you selected in the preceding step.

The Search and Select window appears.

Select the users that you need to add. Click Select.

Select values for Audit on Success By and Audit on Failure By, for each user that you added.

For each user that you added, you can choose to audit successful and failed instances of the chosen operation. You can also choose to audit by access or session.

Repeat steps 5 to 8 for each operation that you choose to audit.

See Also:

Chapter 10, "Auditing Under Oracle Label Security"

6 Working with Labeled Data

This chapter explains how to use Oracle Label Security features to manage labeled data, view that data of security attributes for a session, and change the value of session attributes.

The chapter contains these sections:

The Policy Label Column and Label Tags

Presenting the Label

Filtering Data Using Labels

Inserting Labeled Data

Note:

Many of the examples in this book use the HUMAN_RESOURCES sample policy. Its policy name is HR and its policy label column is HR_LABEL. Unless otherwise noted, the examples assume that the SQL statements are performed on rows within the user's authorization and with full Oracle Label Security policy enforcement in effect.

The Policy Label Column and Label Tags

This section explains how policy label columns in a table or schema are created and filled, using these topics:

The Policy Label Column

Label Tags

The Policy Label Column

Each policy that is applied to a table creates a column in the database. By default, the data type of the policy label column is NUMBER.

Note:

The act of creating a policy does not in itself have any effect on tables or schemas. It only applies the policy to a table or schema. Refer to these sections:

"SA_SYSDBA.CREATE_POLICY Procedure"

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

"SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure"

Each row's label for that policy is represented by a tag in that column, using the numeric equivalent of the character-string label value. The label tag is automatically generated when the label is created, unless the administrator specifies the tag manually at that time.

The automatic label generation follows the rules established by the administrator while defining the label components, as described in Chapter 2, "Understanding Data Labels and User Labels".

Hiding the Policy Label Column

The administrator can decide not to display the column representing a policy by applying the HIDE option to the table. After a policy using HIDE is applied to a table, a user executing a SELECT * or performing a DESCRIBE operation will not see the policy label column. If the policy label column is not hidden, then the label tag is displayed as data type NUMBER. Refer to "The HIDE Policy Column Option".

Example 1: Numeric Column Data Type (NUMBER)

DESCRIBE EMP;
 Name                                      Null?    Type
 ----------------------------------------- -------- --------
 EMPNO                                     NOT NULL NUMBER(4)
 ENAME                                              CHAR(10)
 JOB                                                CHAR(9)
 MGR                                                NUMBER(4)
 SAL                                                NUMBER(7,2)
 DEPTNO                                    NOT NULL NUMBER(2)
 HR_LABEL                                           NUMBER(10)

Example 2: Numeric Column Data Type with Hidden Column

Notice that in this example, the HR_LABEL column is not displayed.

DESCRIBE EMP;
 Name                                      Null?    Type
 ----------------------------------------- -------- --------
 EMPNO                                     NOT NULL NUMBER(4)
 ENAME                                              CHAR(10)
 JOB                                                CHAR(9)
 MGR                                                NUMBER(4)
 SAL                                                NUMBER(7,2)
 DEPTNO                                    NOT NULL NUMBER(2)

Label Tags

As noted in Chapter 2, "Understanding Data Labels and User Labels", the administrator first defines a set of label components to be used in a policy. When creating labels, the administrator specifies the set of valid combinations of components that can make up a label, that is, a level optionally combined with one or more groups or compartments. Each such valid label within a policy is uniquely identified by an associated numeric tag assigned by the administrator or generated automatically upon its first use. Manual definition has the advantage of allowing the administrator to control the ordering of label values when they are sorted or logically compared.

However, label tags must be unique across all policies in the database. When you use multiple policies in a database, you cannot use the same numeric label tag in different policies. Remember that each label tag uniquely identifies one label, and that numeric tag is what is stored in the data rows, not the label's character-string representation.

This section contains these topics:

Manually Defining Label Tags to Order Labels

Manually Defining Label Tags to Manipulate Data

Automatically Generated Label Tags

Manually Defining Label Tags to Order Labels

By manually defining label tags, the administrator can implement a data manipulation strategy that permits labels to be meaningfully sorted and compared. To do this, the administrator predefines all of the labels to be associated with protected data, and assigns to each label a meaningful label tag value. Manually assigned label tags can have up to eight digits. The value of a label tag must be greater than zero.

It may be advantageous to implement a strategy in which label tag values are related to the numeric values of label components. In this way, you can use the tags to group data rows in a meaningful way. This approach, however, is not mandatory. It is good practice to set tags for labels of higher sensitivity to a higher numeric value than tags for labels of lower sensitivity.

Table 6-1 illustrates a set of label tags that have been assigned by an administrator. Notice that, in this example, the administrator has based the label tag value on the numeric form of the levels, compartments, and rows that were discussed in Chapter 2, "Understanding Data Labels and User Labels".

Table 6-1 Administratively Defined Label Tags (Example)

Label Tag
Label String

10000

P

20000

C

21000

C:FNCL

21100

C:FNCL,OP

30000

S

31110

S:OP:WR

40000

HS

42000

HS:OP

In this example, labels with a level of PUBLIC begin with "1", labels with a level of CONFIDENTIAL begin with "2", labels with a level of SENSITIVE begin with "3", and labels with a level of HIGHLY_SENSITIVE begin with "4".

Labels with the FINANCIAL compartment then come in the 1000 range, labels with the compartment OP are in the 1100 range, and so on. The tens place is used to indicate the group WR, for example.

Another strategy might be completely based on groups, where the tags might be 3110, 3120, 3130, and so on.

Note, however, that label tags identify the whole label, independent of the numeric values assigned for the individual label components. The label tag is used as a whole integer, not as a set of individually evaluated numbers.

Manually Defining Label Tags to Manipulate Data

An administratively defined label tag can serve as a convenient way to reference a complete label string (that is, a particular combination of label components). As illustrated in Table 6-1, for example, the tag "31110" could stand for the complete label string "S:OP:WR".

Label tags can be used as a convenient way to partition data. For example, all data with labels in the range 1000 - 1999 could be placed in tablespace A, all data with labels in the range 2000 - 2999 could be placed in tablespace B, and so on.

This simplified notation also comes in handy when there is a finite number of labels and you need to perform various operations upon them. Consider a situation in which one company hosts a human resources system for many other companies. Assume that all users from Company Y have the label "C:ALPHA:CY", for which the tag "210" has been set. To determine the total number of application users from Company Y, the host administrator can enter:

SELECT * FROM tab1
  WHERE hr_label = 210;

Automatically Generated Label Tags

Dynamically generated label tags, illustrated in Table 6-2, have 10 digits, with no relationship to numbers assigned to any label component. There is no way to group the data by label.

Table 6-2 Generated Label Tags (Example)

Label Tag
Label String

100000020

P

100000052

C

100000503

C:FNCL

100000132

C:FNCL,OP

100000003

S

100000780

S:OP:WR

100000035

HS

100000036

HS:OP

See Also:

"SA_LABEL_ADMIN.CREATE_LABEL Procedure"

"Planning a Label Tag Strategy to Enhance Performance"

Assigning Labels to Data Rows

For rows that are being inserted, refer to Inserting Labeled Data.

For existing data rows, labels can be assigned by a labeling function that you create. In such a function, you specify the exact table and row conditions defining what label to insert. The function can be named in the call to apply a policy to a table or schema, or in an update by the administrator.

See Also:

"Using a Labeling Function"

SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure.

"SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure"

Presenting the Label

When you retrieve labels, you do not automatically obtain the character string value. By default, the label tag value is returned. Two label manipulation functions enable you to convert the label tag value to and from its character string representation:

Converting a Character String to a Label Tag, with CHAR_TO_LABEL

Converting a Label Tag to a Character String, with LABEL_TO_CHAR

Converting a Character String to a Label Tag, with CHAR_TO_LABEL

Use the CHAR_TO_LABEL function to convert a character string to a label tag. This function returns the label tag for the specified character string.

Syntax

FUNCTION CHAR_TO_LABEL (
     policy_name     IN VARCHAR2,
     label_string    IN VARCHAR2)
RETURN NUMBER;

Example

INSERT INTO emp (empno,hr_label)
VALUES (999, CHAR_TO_LABEL('HR','S:A,B:G5');

Here, HR is the label policy name, S is a sensitivity level, A,B compartments, and G5 a group.

Converting a Label Tag to a Character String, with LABEL_TO_CHAR

When you query a table or view, you automatically retrieve all of the rows in the table or view that satisfy the qualifications of the query and are dominated by your label. If the policy label column is not hidden, then the label tag value for each row is displayed. You must use the LABEL_TO_CHAR function to display the character string value of each label.

Note that all conversions must be explicit. There is no automatic casting to and from tag and character string representations.

Syntax

FUNCTION LABEL_TO_CHAR (
     label                 IN NUMBER)
RETURN VARCHAR2;

LABEL_TO_CHAR Examples

The examples that follow illustrate the use of LABEL_TO_CHAR.

Example 1

To retrieve the label of a row from a table or view, specify the policy label column in the SELECT statement as follows:

SELECT label_to_char (hr_label) AS label, ename FROM tab1;
  WHERE ename = 'RWRIGHT';

This statement returns the following:

LABEL          ENAME
------------   ----------
S:A,B:G1       RWRIGHT

Example 2

You can also specify the policy label column in the WHERE clause of a SELECT statement. The following statement displays all rows that have the policy label S:A,B:G1

SELECT label_to_char (hr_label) AS label,ename FROM emp
  WHERE hr_label = char_to_label ('HR', 'S:A,B:G1');

This statement returns the following:

LABEL           ENAME
-------------   ---------
S:A,B:G1        RWRIGHT
S:A,B:G1        ESTANTON

Alternatively, you could use a more flexible statement to look up data that contains the string "S:A,B:G1" anywhere in the text of the HR_LABEL column:

SELECT label_to_char (hr_label) AS label,ename FROM emp
  WHERE label_to_char (hr_label) like '%S:A,B:G1%';

If you do not use the LABEL_TO_CHAR function, then you will see the label tag.

Example 3

The following example is with the numeric column data type (NUMBER) and dynamically generated label tags, but without using the LABEL_TO_CHAR function. If you do not use the LABEL_TO_CHAR function, then you will see the label tag.

SQL> select empno, hr_label from emp
     where ename='RWRIGHT';

EMPNO      HR_LABEL
---------- ----------
7839       1000000562

Retrieving All Columns from a Table When the Policy Label Column Is Hidden

If the policy label column is hidden, then it is not automatically returned when you select all columns from a table using the SELECT * command. You must explicitly specify that you want to retrieve the label. For example, to retrieve all columns from the DEPT table (including the policy label column in its character representation), enter the following:

SQL> column label format a10
SQL> select label_to_char (hr_label) as label, dept.*
  2  from dept;

Running these SQL statements returns the following data:

Table 6-3 Data Returned from Sample SQL Statements re Hidden Column

LABEL
DEPTNO
DNAME
LOC

L1

10

ACCOUNTING

NEW YORK

L1

20

RESEARCH

DALLAS

L1

30

SALES

CHICAGO

L1

40

OPERATIONS

BOSTON

By contrast, if you do not explicitly specify the HR_LABEL column, the label is not displayed at all. Note that while the policy column name is on a policy basis, the HIDE option is on a table-by-table basis.

See Also:

"The HIDE Policy Column Option"

Filtering Data Using Labels

During the processing of SQL statements, Oracle Label Security makes calls to the security policies defined in the database by the create and apply procedures discussed in "SA_POLICY_ADMIN Policy Administration PL/SQL Package". For SELECT statements, the policy filters the data rows that the user is authorized to see. For INSERT, UPDATE, and DELETE statements, Oracle Label Security permits or denies the requested operation, based on the user's authorizations.

This section contains these topics:

Using Numeric Label Tags in WHERE Clauses

Ordering Labeled Data Rows

Ordering by Character Representation of Label

Determining Upper and Lower Bounds of Labels

Merging Labels with the MERGE_LABEL Function

See Also:

"Partitioning Data Based on Numeric Label Tags"

Using Numeric Label Tags in WHERE Clauses

This section describes techniques of using numeric label tags in WHERE clauses of SELECT statements.

When using labels in the NUMBER format, the administrator can set up labels so that a list of their label tags distinguishes the different levels. Comparisons of these numeric label tags can be used for ORDER BY processing, and with the logical operators.

For example, if the administrator has assigned all UNCLASSIFIED labels to the 1000 range, all SENSITIVE labels to the 2000 range, and all HIGHLY_SENSITIVE labels to the 3000 range, then you can list all SENSITIVE records by entering:

SELECT * FROM emp
WHERE hr_label BETWEEN 2000 AND 2999;

To list all SENSITIVE and UNCLASSIFIED records, you can enter:

SELECT * FROM emp
WHERE hr_label <3000;

To list all HIGHLY_SENSITIVE records, you can enter:

SELECT * FROM emp
WHERE hr_label=3000;

Note:

Remember that such queries have meaning only if the administrator has applied a numeric ordering strategy to the label tags that he or she originally assigned to the labels. In this way, the administrator can provide for convenient dissemination of data. If, however, the label tag values are generated automatically, then there is no intrinsic relationship between the value of the tag and the order of the labels.

Alternatively, you can use dominance relationships to set up an ordering strategy.

See Also:

"Using Dominance Functions"

Ordering Labeled Data Rows

You can perform an ORDER BY referencing the policy label column to order rows by the numeric label tag value that the administrator has set. For example:

SELECT * from emp
ORDER BY hr_label;

Notice that no functions were necessary in this statement. The statement made use of label tags set up by the administrator.

Note:

Again, such queries have meaning only if the administrator has applied a numeric ordering strategy to the label tags originally assigned to the labels.

Ordering by Character Representation of Label

Using the LABEL_TO_CHAR function, you can order data rows by the character representation of the label. For example, the following statement returns all rows sorted by the text order of the label:

SELECT * FROM emp
ORDER BY label_to_char (hr_label);

Determining Upper and Lower Bounds of Labels

This section describes the Oracle Label Security functions that determine the least upper bound or the greatest lower bound of two or more labels. Two single-row functions operate on each row returned by a query. They return one result for each row.

Finding Least Upper Bound with LEAST_UBOUND

Finding Greatest Lower Bound with GREATEST_LBOUND

Note:

In all functions that take multiple labels, the labels must all belong to the same policy.

Finding Least Upper Bound with LEAST_UBOUND

The OLS_LEAST_UBOUND (OLS_LUBD) function returns a character string label that is the least upper bound of label1 and label2: that is, the one label that dominates both. The least upper bound is the highest level, the union of the compartments in the labels, and the union of the groups in the labels. For example, the least upper bound of HIGHLY_SENSITIVE:ALPHA and SENSITIVE:BETA is HIGHLY_SENSITIVE:ALPHA,BETA.

Syntax

FUNCTION OLS_LEAST_UBOUND (
     label1                    IN NUMBER,
     label2                    IN NUMBER)
RETURN VARCHAR2;

Note:

The old OLS functions, LEAST_UBOUND and LUBD have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_LEAST_UBOUND and OLS_LUBD functions instead. Using the new function names avoids potential name conflicts with other database components.

The OLS_LEAST_UBOUND function is useful when joining rows with different labels, because it provides a high water mark label for joined rows.

The following query compares each employee's label with the label of his or her department, and returns the higher label, whether it be in the EMP table or the DEPT table.

SELECT ename,dept.deptno,
  OLS_LEAST_UBOUND(emp.hr_label,dept.hr_label) as label
  FROM emp, dept
  WHERE emp.deptno=dept.deptno;

This query returns the following data:

Table 6-4 Data Returned from Sample SQL Statements re Least_UBound

ENAME
DEPTNO
LABEL

KING

10

L3:M:D10

BLAKE

30

L3:M:D30

CLARK

10

L3:M:D10

JONES

20

L3:M:D20

MARTIN

30

L2:E:D30

Finding Greatest Lower Bound with GREATEST_LBOUND

The OLS_GREATEST_LBOUND (OLS_GLBD) standalone function can be used to determine the lowest label of the data that can be involved in an operation, given two different labels. It returns a character string label that is the greatest lower bound of label1 and label2. The greatest lower bound is the lowest level, the intersection of the compartments in the labels and the groups in the labels. For example, the greatest lower bound of HIGHLY_SENSITIVE:ALPHA and SENSITIVE is SENSITIVE.

Syntax

FUNCTION OLS_GREATEST_LBOUND (
     label1                  IN NUMBER,
     label2                  IN NUMBER)
RETURN VARCHAR2;

Note:

The old OLS functions, GREATEST_LBOUND and GLBD have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_GREATEST_LBOUND and OLS_GLBD functions instead. Using the new function names avoids potential name conflicts with other database components.

Merging Labels with the MERGE_LABEL Function

The MERGE_LABEL function is a utility for merging two labels together. It accepts the character string form of two labels and the three-character specification of a merge format. Its syntax is as follows:

Syntax

FUNCTION merge_label (label1 IN number,
                      label2 IN number,
                      merge_format IN VARCHAR2)
RETURN number;

The valid merge format is specified with a three-character string:

<highest level or lowest level><union or intersection of compartments><union or intersection of groups>

The first character indicates whether to merge using the highest level or the lowest level of the two labels.

The second character indicates whether to merge using the union or the intersection of the compartments in the two labels.

The third character indicates whether to merge using the union or the intersection of the groups in the two labels.

The following table defines the MERGE_LABEL format constants.

Table 6-5 MERGE_LABEL Format Constants

Format Specification
Data Type
Constant
Meaning
Positions in Which Format Is Used

max_lvl_fmt

CONSTANT varchar2(1)

H

Maximum level

First (level)

min_lvl_fmt

CONSTANT varchar2(1)

L

Minimum level

First (Level)

union_fmt

CONSTANT varchar2(1)

U

Union of the two labels

Second (compartments) and Third (groups)

inter_fmt

CONSTANT varchar2(1)

I

Intersection of the two labels

Second (compartments) and Third (groups)

minus_fmt

CONSTANT varchar2(1)

M

Remove second label from first label

Second (compartments) and Third (groups)

null_fmt

CONSTANT varchar2(1)

N

If specified in compartments column, returns no compartments. If specified in groups column, returns no groups.

Second (compartments) and Third (groups)

For example, HUI specifies the highest level of the two labels, union of the compartments, intersection of the groups.

The MERGE_LABEL function is particularly useful to developers if the LEAST_UBOUND function does not provide the intended result. The LEAST_UBOUND function, when used with two labels containing groups, may result in a less sensitive data label than expected. The MERGE_LABEL function enables you to compute an intersection on the groups, instead of the union of groups that is provided by the LEAST_UBOUND function.

For example, if the label of one data record contains the group UNITED_STATES, and the label of another data record contains the group UNITED_KINGDOM, and the LEAST_UBOUND function is used to compute the least upper bound of these two labels, then the resulting label would be accessible to users authorized for either the UNITED_STATES or the UNITED_KINGDOM.

If, by contrast, the MERGE_LABEL function is used with a format clause of HUI, then the resulting label would contain the highest level, the union of the compartments, and no groups. This is because UNITED_STATES and UNITED_KINGDOM do not intersect.

Inserting Labeled Data

When you insert data into a table protected by a policy under Oracle Label Security, a numeric label value tag must be supplied, usually in the INSERT statement itself.

To do this, you must explicitly specify the tag for the desired label or explicitly convert the character string representation of the label into the correct tag. Note that this does not mean generating new label tags, but referencing the correct tag. When Oracle Label Security is using Oracle Internet Directory, the only permissible labels (and corresponding tags) are those pre-defined by the administrator and already in Oracle Internet Directory.

The only times an INSERT statement may omit a label value are:

If the LABEL_DEFAULT enforcement option was specified when the policy was applied, or

If no enforcement options were specified when the policy was applied and LABEL_DEFAULT was specified when the policy was created, or

If the statement applying the policy named a labeling function.

In cases 1 and 2, the user's session default row label is used as the inserted row's label. In case 3, the inserted row's label is created by that labeling function.

See Also:

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

"SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure"

"SA_SYSDBA.CREATE_POLICY Procedure"

"Using a Labeling Function"

All of Chapter 8, "Implementing Policy Enforcement Options and Labeling Functions" regarding reading and writing labeled data (and labels) and according to policy enforcement options

This section explains the different ways to specify a label in an INSERT statement:

Inserting Labels Using CHAR_TO_LABEL

Inserting Labels Using Numeric Label Tag Values

Inserting Data Without Specifying a Label

Inserting Data When the Policy Label Column Is Hidden

Inserting Labels Using TO_DATA_LABEL

Inserting Labels Using CHAR_TO_LABEL

To insert a row label, you can specify the label character string and then transform it into a label using the CHAR_TO_LABEL function. Using the definition for table emp, the following example shows how to insert data with explicit labels:

INSERT INTO emp (ename,empno,hr_label)
VALUES ('ESTANTON',10,char_to_label ('HR', 'SENSITIVE'));

Inserting Labels Using Numeric Label Tag Values

You can insert data using the numeric label tag value of a label, rather than using the CHAR_TO_LABEL function. For example, if the numeric label tag for SENSITIVE is 3000, it would look like this:

INSERT INTO emp (ename, empno, hr_label)
VALUES ('ESTANTON', 10, 3000);

Inserting Data Without Specifying a Label

If LABEL_DEFAULT is set, or if there is a labeling function applied to the table, then you do not need to specify a label in your INSERT statements. The label will be provided automatically. You can enter the following command:

INSERT INTO emp (ename, empno)
VALUES ('ESTANTON', 10);

The resulting row label is set according to the default value (or by a labeling function).

See Also:

"About Policy Enforcement Options"

"The Label Management Enforcement Options"

"Using a Labeling Function"

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

"SA_SYSDBA.CREATE_POLICY Procedure"

Inserting Data When the Policy Label Column Is Hidden

If the label column is hidden, then the existence of the column is transparent to the insertion of data. INSERT statements can be written that do not explicitly list the table columns and do not include a value for the label column. The session's row label is used to label the data, or a labeling function is used if one was specified when the policy was applied to the table or schema.

You can insert into a table without explicitly naming the columns, as long as you specify a value for each non-hidden column in the table. The following example shows how to insert a row into the table described in "Example 2: Numeric Column Data Type with Hidden Column":

INSERT INTO emp
VALUES ('196','ESTANTON',Technician,RSTOUT,50000,10);

Its label will be one of the following three possibilities:

The label you specify

The label established by the LABEL_DEFAULT option of the policy being applied

The label created by a labeling function named by the policy being applied

Note:

If the policy label column is not hidden, then you must explicitly include a label value (possibly null, indicated by a comma) in the INSERT statement.

Inserting Labels Using TO_DATA_LABEL

Note:

When Oracle Label Security is installed to work with Oracle Internet Directory, dynamic label generation is not allowed, because labels are managed centrally in Oracle Internet Directory, using olsadmintool commands. Refer to Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory"

So, when Oracle Label Security is directory-enabled, this function, TO_DATA_LABEL, is not available and will generate an error message if used.

If you are generating new labels dynamically as you insert data, then you can use the TO_DATA_LABEL function to guarantee that this produces valid data labels. To do this, you must the have EXECUTE authority on the TO_DATA_LABEL function.

Whereas the CHAR_TO_LABEL function requires that the label already be an existing data label for the transaction to succeed, the TO_DATA_LABEL does not have this requirement. It will automatically create a valid data label.

For example:

INSERT INTO emp (ename, empno, hr_label)
VALUES ('ESTANTON', 10, to_data_label ('HR', 'SENSITIVE'));

Note:

The TO_DATA_LABEL function must be explicitly granted to individuals, in order to be used. Its usage should be tightly controlled.

Changing Session and Row Labels

During a given session, a user can change his or her labels, within the authorizations set by the administrator.

7 Oracle Label Security Using Oracle Internet Directory

This chapter contains:

Introducing Label Management on Oracle Internet Directory

Configuring Oracle Internet Directory-Enabled Label Security

Oracle Label Security Profiles

Integrated Capabilities When Label Security Uses the Directory

Oracle Label Security Policy Attributes in Oracle Internet Directory

Restrictions on New Data Label Creation

Administrator Duties for Oracle Internet Directory and Oracle Label Security

Bootstrapping Databases

Synchronizing the Database and Oracle Internet Directory

Security Roles and Permitted Actions

Superseded PL/SQL Statements

Procedures for Policy Administrators Only

Introducing Label Management on Oracle Internet Directory

Managing Oracle Label Security metadata in a centralized LDAP repository provides many benefits.

You can easily provision policies and user label authorizations, and distribute them throughout the enterprise.

When employees are terminated, you can revoke their label authorizations in one place and the change automatically propagates throughout the enterprise.

Previous releases of Oracle Label Security relied on the Oracle Database as the central repository for policy and user label authorizations. This leveraged the scalability and high availability of the Oracle Database, but not the identity management infrastructure, which includes the Oracle Internet Directory (OID). Integrating your installation of Oracle Label Security with Oracle Internet Directory allows label authorizations as part of your standard provisioning process.

These advantages apply also to directory-stored information about policies, user labels, and privileges that Oracle Label Security assigns to users. These labels and privileges are specific to the installation policies defining access control on tables and schemas. If a site is not using Oracle Internet Directory, then such information is stored locally in the database.

The following Oracle Label Security information is stored in the directory:

Policy information, specifically policy name, column name, policy enforcement options, and audit options

User profiles identifying their labels and privileges

Policy label components: levels, compartments, and groups

Policy data labels

Database-specific metadata, such as the following, is not stored in the directory:

Lists of schemas or tables, with associated policy information

Program units, with associated policy privileges

Note the following important aspects of integrating an Oracle Label Security installation with Oracle Internet Directory (OID):

Note:

Oracle will continue to support both the database and directory-based (OID) architectures for Oracle Label Security. However, a single database environment cannot host both architectures. Administrators must decide whether to use the centralized LDAP administration model or the database-centric model.

Note:

You can manage Oracle Label Security policies directly in the directory using the Oracle Label Security administration tool (olsadmintool), described in Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory".

You can also use the graphical user interface provided by Oracle Enterprise Manager to manage Oracle Label Security. The Oracle Enterprise Manager help contains detailed documentation.

For sites that use Oracle Internet Directory, databases retrieve Oracle Label Security policy information from the directory. Administrators use the olsadmintool policy administration tool or the Enterprise Manager graphical user interface to operate directly on the directory to insert, alter, or remove metadata as needed. Because enterprise users can log in to multiple databases using the credentials stored in Oracle Internet Directory, it is logical to store their Oracle Label Security policy authorizations and privileges there as well. An administrator can then modify these authorizations and privileges by updating such metadata in the directory.

For distributed databases, centralized policy management removes the need for replicating policies, because the appropriate policy information is available in the directory. Changes are effective without further effort, synchronized with policy information in the databases by means of the Directory Integration Platform.

See Also:

Synchronization using the Directory Integration Platform is described in the Oracle Identity Management Integration Guide

Figure 7-1 illustrates the structure of metadata storage in Oracle Internet Directory.

Figure 7-1 Diagram of Oracle Label Security Metadata Storage in Oracle Internet Directory

Figure 7-2 illustrates how different policies stored in Oracle Internet Directory apply to the databases accessed by different enterprise users. Directory entries corresponding to the user and the accessed database determine the policy to be applied.

Figure 7-2 Oracle Label Security Policies Applied through Oracle Internet Directory

In this figure, the directory has information about two Oracle Label Security policies, Alpha, applying to database DB1, and Beta, applying to database DB2 Although both policies are known to each database, only the appropriate one is applied in each case. In addition, enterprise users who are to access rows protected by Oracle Label Security are listed in profiles within the Oracle Label Security attributes in Oracle Internet Directory.

As Figure 7-2 shows, the connections between different databases and the directory are established over either SSL or SASL. The database always binds to the directory as a known identity using password-based authentication. Links between databases and their clients (such as a SQL*Plus session, any PL/SQL programs, and so on) can use either SSL or non-SSL connections. The example of Figure 7-2 assumes that users are logged on through password authentication. The choice of connection type depends on the enterprise user model.

The Oracle Label Security policy administration tool operates directly on metadata in Oracle Internet Directory. Changes in the directory are then propagated to the Oracle Directory Integration and Provisioning server, which is configured to send changes to the databases at specific time intervals.

The databases update the policy information in Oracle Internet Directory only when policies are being applied to tables or schemas. These updates ensure that policies that are in use will not be dropped from the directory.

See Also:

Oracle Database Enterprise User Security Administrator's Guide for more information on enterprise domains, user models and authentication activities

Oracle Internet Directory Administrator's Guide for detailed information on Oracle Internet Directory

Configuring Oracle Internet Directory-Enabled Label Security

You can configure a database for Oracle Internet Directory-enabled Label Security at any time after database creation or during custom database creation. Oracle Internet Directory-enabled label security relies on the Enterprise User security feature.

See Also:

"Enterprise User Security Configuration Tasks and Troubleshooting" in the Oracle Database Enterprise User Security Administrator's Guide, for prerequisites and steps to configure a database for directory usage

"Database Configuration Assistant" in the Oracle Database Enterprise User Security Administrator's Guide, for information about DBCA, the Database Configuration Assistant.

Granting Permissions for Configuring OID-Enabled Oracle Label Security

Users who perform Oracle Internet Directory enabled Oracle Label Security using the Database Configuration Assistant (DBCA) need additional privileges. The following steps describe what permissions are needed, and how to grant them:

Use Enterprise Manager to add the user to the OracleDBCreators group.

See Also:

"Managing Identity Management Realm Administrators" in the Oracle Database Enterprise User Security Administrator's Guide for more information on adding a user to an administrative group

Add the user to the Provisioning Admins group. This is necessary because DBCA creates a DIP provisioning profile for Oracle Label Security. Use ldapmodify command with the following .ldif file to add a user to the Provisioning Admins group:

dn: cn=Provisioning Admins,cn=changelog subscriber, cn=oracle internet directory
changetype: modify
add: uniquemember
uniquemember: DN of the user who is to be added

Add the user to the policyCreators group using the olsadmintool command line tool. DBCA bootstraps the database with the Oracle Label Security policy information from Oracle Internet Directory, and only policyCreators can perform this bootstrap.

If the database is already registered with the Oracle Internet Directory using DBCA, use Enterprise Manager to add the user to the OracleDBAdmins group of that database.

Note that the permissions specified earlier are also needed by the administrator who unregisters the database that has Oracle Internet Directory enabled Oracle Label Security configuration.

Registering a Database and Configuring OID-Enabled Oracle Label Security

To register a database and configure OID-enabled Oracle Label security, you must following these general steps:

Step 1: Configure Your Oracle Home for Directory Usage

Step 2: Configure Oracle Internet Directory for Oracle Label Security

Step 2 Alternate: Configuring Database for OID-Enabled Oracle Label Security

Step 3: Set the DIP Password and Connect Data

Step 1: Configure Your Oracle Home for Directory Usage

See Also:

Oracle Database Enterprise User Security Administrator's Guide about configuring your database to use the directory

Step 2: Configure Oracle Internet Directory for Oracle Label Security

Register your database in the directory using DBCA (Database Configuration Assistant).

See Also:

"Registering Your Database with the Directory" in the Oracle Database Enterprise User Security Administrator's Guide

After your database is registered in the directory, configure Label Security:

Start DBCA, select Configure database options in a database, and click Next.

Select a database and click Next.

Regarding the option of unregistering the database or keeping it registered, select Keep the database registered.

If the database is registered with Oracle Internet Directory, the Database options screen shows a customize button beside the Label Security check box. Select the Label Security option and click Customize.

This customize dialog has two configuration options, for standalone Oracle Label Security or for Oracle Internet Directory-enabled Oracle Label Security. Click OID-enabled Label security configuration and enter the Oracle Internet Directory credentials of an appropriate administrator. Click Ok.

Continue with the remaining DBCA steps and click Finish when it appears.

Note:

You can configure a standalone Oracle Label Security on a database that is registered with Oracle Internet Directory. Select the standalone option in step e.

When configuring for Oracle Internet Directory-enabled Oracle Label Security, DBCA also does the following things in addition to registering the database:

Creates a provisioning profile for propagating Label Security policy changes to the database.

Installs the required packages on the database side for Oracle Internet Directory-enabled Oracle Label Security.

Bootstraps the database with all the existing Label Security policy information in the Oracle Internet Directory.

See Also:

"Bootstrapping Databases" for more information.

Step 2 Alternate: Configuring Database for OID-Enabled Oracle Label Security

Registering the database and configuring Oracle Label Security can be done in one invocation of DBCA.

Start DBCA.

Select Configure database options in a database and click Next.

Select a database and click Next.

Click Register the database.

Enter the Oracle Internet Directory credentials of an appropriate administrator, and the corresponding password for the database wallet that will be created.

Enter an optional Custom Database Name for the database.

The ability to specify a custom database name is new in Oracle Database 12c. By default, the database CN (first part of the DN or the distinguished name) in the directory is the DB_UNIQUE_NAME. You can change this to a custom value.

The Database options screen shows a Customize button beside the Label Security check box. Select the Label Security option and click Customize.

The Customize dialog box is displayed, showing two configuration options, for standalone Oracle Label Security or for Oracle Internet Directory-enabled Oracle Label Security.

Click OID-enabled Label Security Configuration.

Continue with the remaining DBCA steps and click Finish.

Step 3: Set the DIP Password and Connect Data

Use the command line tool oidprovtool to set the password for the DIP user and update the interface connect information in the DIP provisioning profile for that database with the new password.

See "Oracle Directory Integration and Provisioning (DIP) Provisioning Profiles" for more details.

Upon creation, the DIP profile uses a schedule value of 3600 seconds by default, meaning that Oracle Label Security changes are propagated to the database every hour. You can use oidprovtool to change this value if deployment considerations require that.

Once the database is configured for Oracle Internet Directory-enabled Oracle Label Security, further considerations regarding enterprise user security may apply.

See Also:

Oracle Database Enterprise User Security Administrator's Guide for further concepts, tools, steps, and procedures

Unregistering a Database with Oracle Internet Directory Enabled Oracle Label Security

To perform this task, you use DBCA, which does the following things:

Deletes the DIP provisioning profile for the database created for Oracle Label Security.

Installs the required packages for standalone Oracle Label Security, so that after unregistering, Oracle Internet Directory enabled Oracle Label Security becomes standalone Oracle Label Security.

Note:

Specific instructions for database unregistration appear in the Oracle Database Enterprise User Security Administrator's Guide. No special steps are required when Oracle Internet Directory-enabled Oracle Label Security is configured.

If a database has standalone Oracle Label Security, it cannot be converted to Oracle Internet Directory-enabled Oracle Label Security. You need to drop Oracle Label Security from the database and then use DBCA again to configure Oracle Internet Directory-enabled Oracle Label Security.

Removing Directory-Enabled Oracle Label Security from Database

To remove Oracle Internet Directory-enabled Oracle Label Security from a database, first unregister the database using DBCA, and then run the following script:

$ORACLE_HOME/rdbms/admin/catnools.sql

Oracle Label Security Profiles

A user profile is a set of user authorizations and privileges. Profiles are maintained as part of each Oracle Label Security policy stored in the Directory.

If a user is added to a profile, then the authorizations and privileges defined in that profile for that particular policy are acquired by the user, which include the following attributes:

Five label authorizations:

maximum read label

maximum write label

minimum write label

default read label

default row label

Privileges

The list of enterprise users to whom these authorizations apply

See Also:

"Oracle Label Security Policy Attributes in Oracle Internet Directory"

"Getting Started with Enterprise User Security" in the Oracle Database Enterprise User Security Administrator's Guide for more information on creating and managing enterprise users

Oracle Enterprise Manager help for information on creating and administering Oracle Label Security profiles and policies

An enterprise user can belong to only one profile, or none.

Integrated Capabilities When Label Security Uses the Directory

The integration of Oracle Label Security and Oracle Internet Directory enables the following capabilities:

User/administrator actions

Storing multiple Oracle Label Security policies in Oracle Internet Directory

Managing Oracle Label Security policies and options in the directory, including

creating or dropping a policy

changing policy options

changing audit settings

Creating label components for any Oracle Label Security policies by

creating or removing levels, compartments, or groups

assigning numeric values to levels, compartments, or groups

changing long names of levels, compartments, or groups

creating children groups

Managing enterprise users configured as users of any Oracle Label Security policies, including

assigning or removing enterprise users to/from profiles within policies

assigning policy-specific privileges to enterprise users, or removing them

changing policy label authorizations assigned to enterprise users

Managing all user/administrator actions and capabilities by means of an integrated set of command line tools that monitor and manage Oracle Label Security policies in Oracle Internet Directory.

Automatic results of Oracle Label Security

Limiting database policy usage to directory-defined policies only (no local policies defined or applied)

Synchronizing changes to policies in the directory with the databases using Oracle Label Security (to apply after enterprise users reconnect)

After changes are propagated by the Directory Integration Platform, having immediate access to enterprise users' Oracle Label Security attributes when these users log on to any database using Oracle Label Security, assuming they are configured within any Oracle Label Security policies. These attributes include users' label authorizations and users' privileges.

Oracle Label Security Policy Attributes in Oracle Internet Directory

In Oracle Internet Directory, Oracle-related metadata is stored under cn=OracleContext. Within Label Security, each policy holds the information and parameters shown in Figure 7-1, "Diagram of Oracle Label Security Metadata Storage in Oracle Internet Directory":

When Oracle Label Security is used without Oracle Internet Directory, it supports automatic creation of data labels by means of a label function. However, when Oracle Label Security is used with Oracle Internet Directory, such functions can create labels only using data labels that are already defined in the directory.

Table 7-1 Contents of Each Policy

Type of Entry
Contents
Meaning/Sample Usage/References

Policy Name

The name assigned to this policy at its creation

Used in olsadmintool commands such as olsadmintool createpolicy (refer to Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory")

Column Name

The name of the column that will hold the label values relevant to this policy

Column is added to database. Refer to "The Policy Label Column and Label Tags"

"Inserting Labeled Data"

"The HIDE Policy Column Option"

Appendix F, "Oracle Label Security Reference".

Used in

olsadmintool createpolicy

Enforcement Options

Any combination of the following entries:

LABEL_DEFAULT,LABEL_UPDATE, CHECK_CONTROL,READ_CONTROL, WRITE_CONTROL,INSERT_CONTROL, DELETE_CONTROL,UPDATE_CONTROL, ALL_CONTROL, or NO_CONTROL

Refer to the discussions in Chapter 8, "Implementing Policy Enforcement Options and Labeling Functions" and Appendix F, "Oracle Label Security Reference".

Used in

olsadmintool createpolicy

and olsadmintool alterpolicy

Options

Enabled:TRUE or FALSE, Type: ACCESS or SESSION, Success: SUCCESSFUL,UNSUCCESSFUL, or BOTH.

Used in

olsadmintool audit

Levels

Name and number for each level

Used in olsadmintool create/alter/droplevel

Compartments

Name and number for each compartment

Used in olsadmintool create/alter/drop compartment

Groups

Name, number, and parent for each group

Used in olsadmintool create/alter/dropgroup

Profiles

Maximum and default read labels, maximum and minimum write labels, default row label, list of users, and a set of privileges from this list:

READ, FULL,

WRITEUP, WRITEDOWN, WRITEACROSS,

PROFILE_ACCESS, or COMPACCESS

Policies can have one or more profiles, each of which can be assigned to many users. Profiles reduce the need to set up label authorizations for individual users.

All users with the same set of labels and privileges are grouped in a single profile. Each profile represents a different set of labels, privileges, and users. Each profile in a policy is unique.

Data Labels

Full name and number for each valid data label

Refer to "Restrictions on New Data Label Creation".

Administrators

Name of each administrator authorized to modify the parameters within this policy.

Policy administrators can modify parameters within a policy. They are not necessarily also policy creators, who have the right to create or remove policies or policy administrators. Refer to "Security Roles and Permitted Actions".

Subscribing Policies in Directory-Enabled Label Security

In an Oracle Internet Directory-enabled Oracle Label Security, you must subscribe a policy before it can be applied (by SA_POLICY_ADMIN.APPLY_TABLE_POLICY or SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY).

In a standalone Oracle Label Security installation, the SA_POLICY_ADMIN.APPLY_TABLE_POLICY or SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY functions can be used directly without the need to subscribe.

See Also:

"SA_POLICY_ADMIN Policy Administration PL/SQL Package"

"Step 5: Apply the Policy to a Database Table or Schema"

Restrictions on New Data Label Creation

When Oracle Label Security is used with Oracle Internet Directory, data labels must be pre-defined in the directory.

They cannot be created dynamically by a label function, as is possible when label security is not integrated with the directory.

Administrator Duties for Oracle Internet Directory and Oracle Label Security

Administrators listed within a policy are those individuals authorized to do the following policy-specific administrative tasks:

Modify existing policy options and audit settings.

Enable or disable auditing for a policy.

Create or remove levels, compartments, groups or children groups.

Modify full/long names for levels, compartment, or groups.

Define or modify enterprise user settings, in this policy, for:

Privileges

Maximum or minimum levels

Read, write, or row access for levels, compartments, or groups

Label profiles

Remove enterprise users from a policy.

There is a higher level of administrators, called policy creators, who can create and remove Oracle Label Security policies and the policy administrators named within them.

Bootstrapping Databases

After you register a new database with Oracle Internet Directory, you can install Oracle Internet Directory enabled Oracle Label Security on that database. This installation process automatically creates a Directory Integration Platform (DIP) provisioning profile enabling policy information to be periodically refreshed in the future by downloading it to the database. Refer to "Oracle Directory Integration and Provisioning (DIP) Provisioning Profiles".

When configuring the database for Oracle Internet Directory enabled Oracle Label Security, the DBCA tool puts all the policy information in Oracle Internet Directory into the database. At any point, the administrator can decide to bootstrap the database with the policy information again, using the bootstrap utility script at $ORACLE_HOME/bin/olsoidsync. The parameters it requires are as follows:

olsoidsync --dbconnectstring <"database connect string in host:port:sid format">
--dbuser <database user> --dbuserpassword <database user password> [-c] [-r]
[-b <admin context>] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

For example,

olsoidsync --dbconnectstring yippee:1521:ora101 --dbuser lbacsys
--dbuserpassword lbacsys -c
-b "ou=Americas,o=Oracle,c=US" -h yippee -D cn=policycreator -w Easy2rem

The olsoidsync command pulls policy information from Oracle Internet Directory and populates the information in the database. Users must provide the database TNS name, the database user name, the database user's password, the administrative context (if any), the Oracle Internet Directory host name, the bind DN and bind password, and optionally the Oracle Internet Directory port number.

The optional -c switch causes the command to drop all the existing policies in the database and refresh it with policy information from Oracle Internet Directory.

The optional -r switch causes the command to drop all the policy metadata (without dropping the policies themselves) and refresh the policies with new metadata from Oracle Internet Directory.

Without these two switches, the command will only create new policies from Oracle Internet Directory, and will halt on any errors encountered during the refresh.

Synchronizing the Database and Oracle Internet Directory

This section contains:

About Synchronizing the Database and Oracle Internet Directory

Oracle Directory Integration and Provisioning (DIP) Provisioning Profiles

Disabling, Changing, and Enabling a Provisioning Profile

Changing the Database Connection Information for a Provisioning Profile

Configuring Oracle Directory-Enabled Oracle Label Security with Oracle Data Guard

About Synchronizing the Database and Oracle Internet Directory

Oracle Label Security metadata in the directory is synchronized with the databases using the Oracle Directory Provisioning Integration Service of the Directory Integration Platform.

Changes to the label security data in the directory are conveyed by the provisioning integration service in the form of provisioning events. A software agent receives these events and generates appropriate SQL or PL/SQL statements to update the database. After these statements are processed, Oracle Label Security data dictionaries are updated to match the changes already made in the directory.

Oracle Label Security subscribes itself to the Provisioning Integration Service automatically during installation. The provisioning service stores the information associated with each database in the form of a provisioning profile. The software agent uses the identity of the user DIP, which is created as for Oracle Label Security, to connect to the database, when synchronizing the changes in Oracle Internet Directory with the database.

If the password for the user DIP is changed, then you must update this password in the provisioning profile of the provisioning integration service.

Oracle Directory Integration and Provisioning (DIP) Provisioning Profiles

The DIP server synchronizes policy changes in the directory with the connected databases, using a separate DIP provisioning profile created for each database. This profile is created automatically as part of the installation process for Oracle Internet Directory-enabled Oracle Label Security. The administrator can use the provisioning tool oidprovtool to modify the password for a database profile, using the script $ORACLE_HOME/bin/oidprovtool. Each such profile contains the following information:

Table 7-2 Elements in a DIP Provisioning Profile

Element
Name for This Element When Invoking oidprovtool

The LDAP host name

ldap_host

The LDAP port number

ldap_port

The user DN and password to bind to Oracle Internet Directory to retrieve policy information

ldap_user

ldap_user_password

The database DN

application_dn

The organization DN, that is, the administrative context in which changes are being made

organization_dn

The callback function to be invoked, that is, LBACSYS.OLS_DIP_NTFY

interface_name

The database connect information, which is the host name of the database, the port number used to connect to the database, the database SID, the database user name and password

interface_connect_info

Event subscriptions, including all MODIFY, ADD and DELETE events under cn=LabelSecurity in Oracle Internet Directory

operation

The time interval between synchronizations

schedule

Here is an example of using oidprovtool, followed by an explanation of the parameters in this example:

oidprovtool operation=modify ldap_host=yippee ldap_port=389
ldap_user=cn=defense_admin ldap_user_password=Easy2rem
application_dn="cn=db1,cn=OracleContext,ou=Americas,o=Oracle,c=US"
organization_dn="ou=Americas,o=Oracle,c=US" interface_name=LBACSYS.OLS_DIP_NTFY
interface_type=PLSQL interface_connect_info=yippee:1521:db1:dip:newdip schedule=60
event_subscription= "ENTRY:cn=LabelSecurity,cn=Products,cn=OracleContext,
ou=Americas,o=Oracle,c=US:ADD(*)" event_subscription=
"ENTRY:cn=LabelSecurity,cn=Products, cn=OracleContext,ou=Americas,
o=Oracle,c=US:MODIFY(*)" event_subscription="ENTRY:cn=LabelSecurity,cn=Products,
cn=OracleContext, ou=Americas,o=Oracle,c=US:DELETE"

This sample oidprovtool command creates and enables a new DIP provisioning profile with the following attributes:

Oracle Internet Directory in host yippee using port 389

Oracle Internet Directory user bind DN: cn=defense_admin with password Easy2rem

Database DN: cn=db1, cn=OracleContext, ou=Americas, o=Oracle, c=US

Organization DN (administrative context): ou=Americas, o=Oracle, c=US

Database on host yippee, listening on port 1521

Oracle SID: db1

Database user: dip with new password newdip

Interval to synchronize directory with connected databases: 60 seconds

All the ADD, MODIFY and DELETE events under cn=LabelSecurity to be sent to DIP

To start the DIP server, use $ORACLE_HOME/bin/oidctl. For example:

oidctl server=odisrv connect=db2 config=0 instance=0 start

This command will start the DIP server by connecting to db2 (the Oracle Internet Directory database) with config set to 0 and instance number 0.

See also:

Oracle Identity Management Integration Guide for more information on DIP provisioning profiles

Disabling, Changing, and Enabling a Provisioning Profile

You can change the password for the interface_connect_info, which is the database password, by using the oidprovtool modify command, but first you must disable the profile. After changing the password, you then reenable the profile.

You can disable the Oracle Label Security provisioning profile using oidprovtool, specifying the disable operation and the first six original parameters shown here. (The other original parameters are not needed.) The command form is:

oidprovtool operation=disable ldap_host=host ldap_port=port ldap_user_dn=ldap_user_dn  ldap_user_password=password application_dn=app_dn  organization_dn=org_dn

Using parameters from the example given in the previous section, this command would look like this:

oidprovtool operation=disable ldap_host=yippee ldap_port=389

ldap_user=cn=defense_admin ldap_user_password=password
application_dn="cn=db1,cn=OracleContext,ou=Americas,o=Oracle,c=US"
organization_dn="ou=Americas,o=Oracle,c=US"

To modify the password in the connection information, use the oidprovtool command, specifying the modify operation, the first six original parameters, and the new dip user password given in the connection info. The command form is:

oidprovtool operation=modify  ldap_host=ldap_host ldap_port=port

ldap_user_dn=ldap_user_dn  ldap_user_password=password application_dn=app_dn
organization_dn=org_dn interface_connect_info=new_connect_info

Using parameters from the example given in the previous section, this command would look like this:

oidprovtool operation=modify ldap_host=yippee ldap_port=389

ldap_user=cn=defense_admin ldap_user_password=Easy2rem
application_dn="cn=db1,cn=OracleContext,ou=Americas,o=Oracle,c=US"
organization_dn="ou=Americas,o=Oracle,c=US"
interface_connect_info=yippee:1521:db1:dip:NewestDIPpassword

Similarly, you can re-enable the Directory Integration Platform provisioning profile using oidprovtool as follows, again specifying the desired operation and the first six original parameters. (The other original parameters are not needed.) The command form is:

oidprovtool operation=enable ldap_host=host ldap_port=port ldap_user_dn=ldap_user_dn ldap_user_password=password application_dn=app_dn organization_dn=org_dn

Again using parameters from the example given in the previous section, this command would look like this:

oidprovtool operation=enable ldap_host=yippee ldap_port=389

ldap_user=cn=defense_admin ldap_user_password=password
application_dn="cn=db1,cn=OracleContext,ou=Americas,o=Oracle,c=US"
organization_dn="ou=Americas,o=Oracle,c=US"

Changing the Database Connection Information for a Provisioning Profile

To change the database connection information in the DIP profile:

Disable the provisioning profile.

See "Disabling, Changing, and Enabling a Provisioning Profile" for information about disabling the provisioning profile. This step temporarily stops the propagation of label security changes in the directory to the database, but no data is lost. Once the profile is enabled, any label security changes that happened in the directory since the profile was disabled are synchronized with the database.

Update the database connection information in the profile.

Enable the profile.

See "Disabling, Changing, and Enabling a Provisioning Profile".

Note:

The database character set must be compatible with Oracle Internet Directory for Oracle Internet Directory-enabled Oracle Label Security to work correctly. Only then can there be successful synchronization of the Label Security metadata in Oracle Internet Directory with the Database.

See Oracle Database Globalization Support Guide for more information about character sets and Globalization Support parameters.

See Also:

Disabling, Changing, and Enabling a Provisioning Profile

Oracle Identity Management Integration Guide for more information about enabling and disabling of provisioning profiles

Configuring Oracle Directory-Enabled Oracle Label Security with Oracle Data Guard

This section contains:

About Registering Oracle Label Security Failover with Oracle Internet Directory

Step 1: Set Up Directory-Enabled Oracle Label Security with Data Guard

Step 2: After the Switchover, Update the OID Provisioning Profile

About Registering Oracle Label Security Failover with Oracle Internet Directory

This section explains how to set up the primary database and includes steps to follow after you have switched over to a standby database for Oracle Label Security in an Oracle Internet Directory-enabled environment.

Step 1: Set Up Directory-Enabled Oracle Label Security with Data Guard

Configure Oracle Data Guard for your database.

See Oracle Data Guard Broker for information about installing Oracle Data Guard.

Register Oracle Label Security in Oracle Internet Directory on the primary database.

See "Registering a Database and Configuring OID-Enabled Oracle Label Security" for more information.

Verify the that the policies have been propagated to the primary database.

Create the Oracle Label Security policies in an Oracle Internet Directory using the olsadmintool utility or in Oracle Enterprise Manager Cloud Control.

See Appendix C for more information about using the olsadmintool utility.

Connect to the primary database as user LBACSYS.

Query the DBA_SA_POLICIES data dictionary view to confirm that the policies were propagated to the primary database.

SELECT POLICY_NAME FROM DBA_SA_POLICIES;

Connect to the standby database as user LBACSYS and then perform the SELECT POLICY_NAME FROM DBA_SA_POLICIES; query to ensure that the policies that were propagated on the primary database are on the standby database, though the redo log apply process.

Copy the ewallet.p12, sqlnet.ora, and ldap.ora files from the primary database to the standby database after the OLS-OID registration is complete.

This step is useful in case of failover and the primary database is not accessible. By default, these files are in the following locations:

ewallet.p12, the wallet file, is in either the $ORACLE_BASE/admin/Oracle_SID/wallet directory or the $ORACLE_HOME/admin/Oracle_SID/wallet directory.

sqlnet.ora is in the $ORACLE_HOME/network/admin directory. (Back up this file before copying it to the standby database.)

ldap.ora is in the $ORACLE_HOME/network/admin directory.

Go to the directory where you copied the ewallet.p12 file.

Create SSO wallet file (cwallet.sso) associated to PKCS#12 wallet (ewallet.p12) by using the following syntax:

orapki wallet create -wallet wallet_location -auto_login [-pwd password]

Step 2: After the Switchover, Update the OID Provisioning Profile

In this step, after you have you have performed the switchover and completed steps 5, 6, and 7 under "Step 1: Set Up Directory-Enabled Oracle Label Security with Data Guard", you are ready to update the provisioning profile in Oracle Internet Directory with the connection information of the new primary database. If you do not complete the following procedure, then the policies will continue to be propagated to the new standby database, and the old primary database will fail with an ORA-16000 database open for read-only access error. After you have updated the provisioning profile with the new primary database connection information, then policy propagation takes place in the new primary database. In addition, these policies are propagated to the new standby through the redo apply process.

On either the primary or the standby computer, run the following oidprovtool utility command for the new primary database.

oidprovtool operation=modify \
ldap_host=OID_Server_hostname ldap_port=OID_Server_Port \
ldap_user_dn="cn=orcladmin"  \ application_dn="LDAP_distinguised_name_of_application" \

The application_dn setting can be derived from dn=dbname, cn=oraclecontext, default_admin_context. The ldap.ora file lists the default_admin_context setting.

When prompted, enter the LDAP user password.

Please enter the LDAP password:

When prompted, enter the interface connection information in the following format:

host:port:service_name:dip:password

DIP is the Oracle Directory Integration and Provisioning (DIP) account that is installed with Oracle Label Security. This account is created automatically as part of the installation process for Oracle Internet Directory-enabled Oracle Label Security.

To specify no interface connection information, omit any settings and press Return.

After you complete the provisioning profile, then restart the DIP server.

Security Roles and Permitted Actions

To manage Oracle Label Security policies in Oracle Internet Directory, certain entities are given access control rights in the directory. The access control mechanisms are provided by Oracle Internet Directory.

Table 7-3 describes, in abstract terms, these entities and the tasks they are enabled to perform.

Table 7-3 Tasks That Certain Entities Can Perform

Entity
Tasks This Entity Can Perform

Policy creators

Create new (or delete existing) policies, create new (or remove existing) policy administrators.

Policy administrators

For Policies: modify existing policy options and audit settings, enable or disable auditing for a policy.

For Label components: create, modify, or remove levels, compartments and groups, such as by changing their full or long names or (for groups) by creating or deleting their children groups.

For enterprise users: remove enterprise users from a policy, modify enterprise users' maximum or minimum levels, their read, write, and row access for compartments or groups, their privileges for a policy, and their label profiles.

Table 7-4 lists the specific access level operations permitted or disallowed for policy creators, policy administrators, and label security users.

Table 7-4 Access Levels Allowed by Users in OID

Entries
Policy Creators
Policy Administrators
Databases

cn=Policies

can modify

no access

no access

cn=Admins, cn=Policy1

can modify

no access

no access

uniqueMember: cn=Policy1

can browse

can browse

can modify

cn=PolicyCreators

no accessFoot 1 

no access

no access

cn=Levels, cn=Policy1

can browse and delete

can modify

no access

cn=Compartments, cn=Policy1

can browse and delete

can modify

no access

cn=Groups, cn=Policy1

can browse and delete

can modify

no access

cn=AuditOptions,cn=Policy1

can browse and delete

can modify

no access

cn=Profiles,cn=Policy1

can browse and delete

can modify

no access

cn=Labels,cn=Policy1

can browse and delete

can modify

no access

cn=DBServers

no accessFoot 2 

no access

no access

Footnote 1 The group cn=OracleContextAdmins is the owner of the group cn=PolicyCreators, so members in cn=OracleContextAdmins can modify cn=PolicyCreators.

Footnote 2 The group cn=OracleDBCreators is the owner of the group cn=DBServers, so members in cn=OracleDBCreators can modify cn=DBServers.

Restriction on Policy Creators for Directory-enabled Oracle Label Security

A member of the Policy Creators group can only create, browse, and delete Oracle Label Security policies.

This user cannot perform policy administrative tasks, such as creating label components and adding users, even if explicitly added to the Policy Admins group of that policy. In short, a policy creator cannot be the administrator of any policy.

Superseded PL/SQL Statements

When Oracle Internet Directory is enabled with Oracle Label Security, the procedures listed in the following table are superseded. Only LBACSYS is allowed to run these procedures.

For some of the procedures listed in the table, the functionality they provided is replaced by the olsadmintool command named in the second column (and explained in Appendix F, "Oracle Label Security Reference").

Table 7-5 Procedures Superseded by olsadmintool When Using Oracle Internet Directory

Disabled Procedure
Replaced by olsadmintool Command

SA_SYSDBA.CREATE_POLICY

olsadmintool createpolicy

SA_SYSDBA.ALTER_POLICY

olsadmintool alterpolicy

SA_SYSDBA.DROP_POLICY

olsadmintool droppolicy

SA_COMPONENTS.CREATE_LEVEL

olsadmintool createlevel

SA_COMPONENTS.ALTER_LEVEL

olsadmintool alterlevel

SA_COMPONENTS.DROP_LEVEL

olsadmintool droplevel

SA_COMPONENTS.CREATE_COMPARTMENT

olsadmintool createcompartment

SA_COMPONENTS.ALTER_COMPARTMENT

olsadmintool altercompartment

SA_COMPONENTS.DROP_COMPARTMENT

olsadmintool dropcompartment

SA_COMPONENTS.CREATE_GROUP

olsadmintool creategroup

SA_COMPONENTS.ALTER_GROUP

olsadmintool altergroup

SA_COMPONENTS.ALTER_GROUP_PARENT

olsadmintool altergroup

SA_COMPONENTS.DROP_GROUP

olsadmintool dropgroup

SA_USER_ADMIN.SET_LEVELS

None

SA_USER_ADMIN.SET_COMPARTMENTS

None

SA_USER_ADMIN.SET_GROUPS

None

SA_USER_ADMIN.ADD_COMPARTMENTS

None

SA_USER_ADMIN.ALTER_COMPARTMENTS

None

SA_USER_ADMIN.DROP_COMPARTMENTS

None

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS

None

SA_USER_ADMIN.ADD_GROUPS

None

SA_USER_ADMIN.ALTER_GROUPS

None

SA_USER_ADMIN.DROP_GROUPS

None

SA_USER_ADMIN.DROP_ALL_GROUPS

None

SA_USER_ADMIN.SET_USER_LABELS

olsadmintool createprofile; olsadmintool adduser; olsadmintool dropprofile; olsadmintool dropuser;

SA_USER_ADMIN.SET_DEFAULT_LABEL

None

SA_USER_ADMIN.SET_ROW_LABEL

None

SA_USER_ADMIN.DROP_USER_ACCESS

olsadmintool dropuser

SA_USER_ADMIN.SET_USER_PRIVS

olsadmintool createprofile; olsadmintool adduser; olsadmintool dropprofile; olsadmintool dropuser;

SA_AUDIT_ADMIN.AUDIT

olsadmintool audit

SA_AUDIT_ADMIN.NOAUDIT

olsadmintool noaudit

SA_AUDIT_ADMIN.AUDIT_LABEL

None

SA_AUDIT_ADMIN.NOAUDIT_LABEL

None

Procedures for Policy Administrators Only

The following procedures are allowed to be run only by policy administrators (enterprise users defined in Oracle Internet Directory):

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY

SA_POLICY_ADMIN.APPLY_TABLE_POLICY

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY

SA_POLICY_ADMIN.GRANT_PROG_PRIVS

SA_POLICY_ADMIN.POLICY_SUBSCRIBE

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY

SA_POLICY_ADMIN.SET_PROG_PRIVS

SA_POLICY_ADMIN.REVOKE_PROG_PRIVS

Part III

Administering an Oracle Label Security Application

This part contains the following chapters:

Chapter 8, "Implementing Policy Enforcement Options and Labeling Functions"

Chapter 9, "Administering and Using Trusted Stored Program Units"

Chapter 10, "Auditing Under Oracle Label Security"

Chapter 11, "Using Oracle Label Security with a Distributed Database"

Chapter 12, "Performing DBA Functions Under Oracle Label Security"

Chapter 13, "Releasability Using Inverse Groups"

8 Implementing Policy Enforcement Options and Labeling Functions

This chapter explains how to customize the enforcement of Oracle Label Security policies and how to implement labeling functions, in the following sections:

Choosing Policy Options

Using a Labeling Function

Inserting Labeled Data Using Policy Options and Labeling Functions

Updating Labeled Data Using Policy Options and Labeling Functions

Deleting Labeled Data Using Policy Options and Labeling Functions

Using a SQL Predicate with an Oracle Label Security Policy

Choosing Policy Options

This section introduces the policy options, and discusses their use.

About Policy Enforcement Options

Levels of Policy Enforcement Options

Categories of Policy Enforcement Options

Relationships of Policy Enforcement Options

The HIDE Policy Column Option

The Label Management Enforcement Options

The Access Control Enforcement Options

The Overriding Enforcement Options

Guidelines for Using the Policy Enforcement Options

Exemptions from Oracle Label Security Policy Enforcement

About Policy Enforcement Options

Of all the enforcement controls that Oracle Label Security permits, the administrator must choose those that meet the needs of the given application. This means identifying levels of data sensitivity to exposure, alteration, or misuse, as well as identifying which users have the need or the right to access or alter such data. The policy enforcement options enable administrators to fine-tune users' abilities to read or write data or labels.

Levels of Policy Enforcement Options

The policy enforcement options can operate at three levels:

Table 8-1 When Policy Enforcement Options Take Effect

Level at which option set
Options set at this level affect user operations ...

Policy Level

... only when the policy has been applied to the table or schema

Schema Level

... whenever a user acts in this schema

Table Level

... whenever a user acts in this table

When you apply a policy to a table or schema, you can specify the enforcement options that are to constrain use of that table or schema. If you do not specify enforcement options at that time, then the default enforcement options you specified when you created that policy are used automatically.

See Also:

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

"SA_SYSDBA.CREATE_POLICY Procedure"

These options customize your policy enforcement to meet your security requirements as to READ access, WRITE access, and label changes. You can also specify whether the label column should be displayed or hidden. You can choose to enforce some or all of the policy options for any protected table by specifying only those you want.

Optionally, you can assign each table a labeling function, which determines the label of any row inserted or updated in that table. You can also specify, optionally, a SQL predicate for a table, to control which rows are accessible to users, based on their labels.

See Also:

Using a Labeling Function.

Using a SQL Predicate with an Oracle Label Security Policy.

When Oracle Label Security policy enforcement options are applied, they control which rows are accessible to view or to insert, update, or delete.

Categories of Policy Enforcement Options

Table 8-2 lists the policy enforcement options in three categories:

Label management options, ensuring that data labels written for inserted or updated rows do not violate policies set for such labels

Access control options, ensuring that only rows whose labels meet established policies are accessible for SELECT, UPDATE, INSERT, or DELETE operations.

Overriding options, which can suspend or apply all other enforcement options.

Table 8-2 Policy Enforcement Options

Type of Enforcement
Option
Description

The Label Management Enforcement Options

LABEL_DEFAULT

Uses the session's default row label value unless the user explicitly specifies a label on INSERT.

LABEL_UPDATE

Applies policy enforcement to UPDATE operations that set or change the value of a label attached to a row. The WRITEUP, WRITEDOWN, and WRITEACROSS privileges are enforced only if the LABEL_UPDATE option is active.

CHECK_CONTROL

Applies READ_CONTROL policy enforcement to INSERT and UPDATE statements to assure that the new row label is read-accessible.

The Access Control Enforcement Options

READ_CONTROL

Applies policy enforcement to all queries. Only authorized rows are accessible for SELECT, UPDATE, and DELETE operations.

WRITE_CONTROL

Determines the ability to INSERT, UPDATE, and DELETE data in a row. If this option is active, it enforces INSERT_CONTROL, UPDATE_CONTROL, and DELETE_CONTROL.

INSERT_CONTROL

Applies policy enforcement to INSERT operations, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

DELETE_CONTROL

Applies policy enforcement to DELETE operations, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

UPDATE_CONTROL

Applies policy enforcement to UPDATE operations on the data columns within a row, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

The Overriding Enforcement Options

ALL_CONTROL

Applies all enforcement options.

NO_CONTROL

Applies no enforcement options. A labeling function or a SQL predicate can nonetheless be applied.

Remember that even when Oracle Label Security is applicable to a table, some DML operations may not be covered by the policies being applied. The policy enforcement options set by the administrator determine both the SQL processing behavior and what an authorized user can actually see in response to a query on a protected table. Except where noted, this chapter assumes that ALL_CONTROL is active, meaning that all enforcement options are in effect. If users attempt to perform an operation for which they are not authorized, then an error message is raised and the SQL statement fails.

See Also:

"Implementing Inverse Groups with the INVERSE_GROUP Enforcement Option"

Understanding the relationships among these policy enforcement options, and what SQL statements they control, is essential to their effective use in designing and implementing your Oracle Label Security policies.

Relationships of Policy Enforcement Options

Table 8-3 describes the relationships between policy enforcement options.

Table 8-3 What Policy Enforcement Options Control

Specifying This Option in a Policy
Controls These SQL Operations
Using These Criteria and with These Effects

READ_CONTROL

SELECT, UPDATE, and DELETE

Only authorized rows (*) are accessible.

WRITE_CONTROL

INSERT, UPDATE, and DELETE

(a) Only authorized rows (**) are accessible

(b) Data labels writable unless LABEL_UPDATE is active.

WRITE_CONTROL is necessary for these three:

INSERT_CONTROL

INSERT

UPDATE_CONTROL

UPDATE

DELETE_CONTROL

DELETE

CHECK_CONTROL

Applies READ_CONTROL policy enforcement to INSERT and UPDATE statements to assure that the new row label is read-accessible.

The Access Control Enforcement Options

Applies policy enforcement to all queries. Only authorized rows are accessible for operations.

Determines the ability to data in a row. If this option is active, then it enforces.

INSERT_CONTROL

Applies policy enforcement to INSERT operations, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

DELETE_CONTROL

Applies policy enforcement to DELETE operations, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

UPDATE_CONTROL

Applies policy enforcement to UPDATE operations on the data columns within a row, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

The Overriding Enforcement Options

ALL_CONTROL

Applies all enforcement options.

NO_CONTROL

Applies no enforcement options. A labeling function or a SQL predicate can nonetheless be applied.

(*) A row is authorized for READ access if the following three criteria are all met:(user-minimum-level) < = (data-row-level) < = (session-level)(any-data-group) is a child of (any-user-group-or-childgroup)(every-data-compartment) is also in (the user's compartments)Refer to Figure 3-6, "Label Evaluation Process for Read Access"

(**) A row is authorized for READ access if the following three criteria are all met:(user-minimum-level) < = (data-row-level) < = (session-level)(any-data-group) is a child of (any-user-group-or-childgroup)(every-data-compartment) is also in (the user's compartments)Refer to Figure 3-6, "Label Evaluation Process for Read Access".

The HIDE Policy Column Option

You can specify the HIDE policy configuration option when you initially apply an Oracle Label Security policy to a table, that is, when adding the policy column to the table. This prevents display of the column containing the policy's labels.

See Also:

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

Once the policy has been applied, the hidden (or not hidden) status of the column cannot be changed unless the policy is removed with the DROP_COLUMN parameter set to TRUE. Then, the policy can be reapplied with a new hidden status.

See Also:

"SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

INSERT statements doing all-column inserts do not require the values for hidden label columns.

SELECT statements do not automatically return the values of hidden label columns. Such values must be explicitly retrieved.

A DESCRIBE on a table may or may not display the label column. If the administrator sets the HIDE option, then the label column will not be displayed. If HIDE is not specified for a policy, then the label column is displayed in response to a SELECT.

See Also:

"Retrieving All Columns from a Table When the Policy Label Column Is Hidden"

The Label Management Enforcement Options

The three label enforcement options control the data label written when a row is inserted or updated. When a policy specifies these options and is applied to a table or schema, these options apply to the situations described in this section.

A user inserting a row can specify any data label within the range of the user's label authorizations. If the user does not specify a label for the row being written, LABEL_DEFAULT can do so. Updates can be restricted by LABEL_UPDATE. Inserts or updates that use a labeling function need CHECK_CONTROL to prevent assigning a data label outside the user's authorizations. Such a label would prevent the user from accessing the row just written, and could enable the user to make data available inappropriately.

Any labeling function in force on a table overrides these options. Such a function can be named in the call that applies the policy to the table. If the administrator named such a function when applying a policy, but then disables or removes that policy, then that function is no longer applied.

See Also:

"SA_SYSDBA.DISABLE_POLICY Procedure"

LABEL_DEFAULT: Using the Session's Default Row Label

A user can update a row without specifying a label value, because the updated row uses its original label. However, to insert a new row, the user must supply a valid label unless a labeling function is in force or LABEL_DEFAULT applies for the table. LABEL_DEFAULT causes the user's session default row label to be used as the new row label.

If neither LABEL_DEFAULT nor a labeling function is in force and the user attempts to INSERT a row, then an error occurs.

Note that any labeling function in force on a table overrides the LABEL_DEFAULT option.

LABEL_UPDATE: Changing Data Labels

A user updating a row can normally change its label to any label within his authorized label range. However, if LABEL_UPDATE applies, then to modify a label, the user must have one or more of these privileges: WRITEUP, WRITEDOWN, and WRITEACROSS.

The LABEL_UPDATE option uses an Oracle after-row trigger which is called only on an update operation affecting the label. Note that any labeling function in force on a table overrides the LABEL_UPDATE option.

See Also:

"Special Row Label Privileges".

CHECK_CONTROL: Checking Data Labels

If a row being inserted or updated gets its label from a labeling function, then that label could conceivably be outside the user's authorizations, preventing future access by that user.

CHECK_CONTROL causes READ_CONTROL to apply to the new label, ensuring that this user will be authorized to read the inserted or updated row after the operation. If not, then the insert or update operation is canceled and has no effect.

In other words, if CHECK_CONTROL is included as an option in a policy being enforced on a row, then the user modifying that row must still be able to access it after the operation. CHECK_CONTROL prevents a user or a labeling function from modifying a row's label to include a level, group, or compartment that the modifying user would be prevented from accessing.

Note that CHECK_CONTROL overrides any labeling function in force on a table.

The Access Control Enforcement Options

Access control options limit the rows accessible for SELECT, UPDATE, INSERT, or DELETE operations to only those rows whose labels meet established policies:

READ_CONTROL: Reading Data

WRITE_CONTROL: Writing Data

INSERT_CONTROL, UPDATE_CONTROL, and DELETE_CONTROL

READ_CONTROL: Reading Data

READ_CONTROL uses Oracle virtual private database (VPD) technology to enforce the read access mediation algorithm illustrated in Figure 3-6, "Label Evaluation Process for Read Access".

READ_CONTROL limits the set of records accessible to a session for SELECT, UPDATE and DELETE operations. If READ_CONTROL is not active, then even rows in the table protected by the policy are accessible to all users.

WRITE_CONTROL: Writing Data

WRITE_CONTROL uses Oracle after-row triggers to enforce the write access mediation algorithm illustrated in Figure 3-7, "Label Evaluation Process for Write Access". When an Oracle Label Security policy specifying the WRITE_CONTROL option is applied to a table, triggers are generated and the algorithm is enforced.

Note:

The protection implementation for WRITE_CONTROL is the same for all write operations, but you need not apply all write options across the board. You can apply WRITE_CONTROL selectively for INSERT, UPDATE, and DELETE operations by using the corresponding policy enforcement option (INSERT_CONTROL, UPDATE_CONTROL, and DELETE_CONTROL) instead of WRITE_CONTROL.

If WRITE_CONTROL is on but LABEL_UPDATE is not specified, then the user can change both data and labels. If you want to control updating the row labels, then specify the LABEL_UPDATE option in addition to WRITE_CONTROL when creating your policies.

INSERT_CONTROL, UPDATE_CONTROL, and DELETE_CONTROL

These options apply policy enforcement during the corresponding operations on the data columns within a row, according to the algorithm for write access described in Figure 3-7, "Label Evaluation Process for Write Access".

Specifying WRITE_CONTROL limits all INSERT, UPDATE, and DELETE operations. However,

Specifying INSERT_CONTROL limits insertions but not updates or deletes;

Specifying UPDATE_CONTROL limits updates but not insertions or deletes; and

Specifying DELETE_CONTROL limits deletes but not insertions or updates.

See Also:

For inserts, Inserting Labeled Data Using Policy Options and Labeling Functions;

for updates, Updating Labeled Data Using Policy Options and Labeling Functions;

and for deletions, Deleting Labeled Data Using Policy Options and Labeling Functions.

The Overriding Enforcement Options

Whereas ALL_CONTROL applies all of the label management and access control enforcement options, NO_CONTROL applies none of them. In either case, labeling functions and SQL predicates can be applied. Note that the ALL_CONTROL option can be used only on the command line.

If you apply a policy with NO_CONTROL specified, then a policy label column is added to the table, but the label values are NULL. Because no access controls are operating on the table, you can proceed to enter labels as desired. You can then set the policy enforcement options as you wish.

NO_CONTROL can be a useful option if you have a labeling function in force to label the data correctly, but want to let all users access all the data.

Guidelines for Using the Policy Enforcement Options

You can customize policy enforcement for a schema or table through the Oracle Enterprise Manager as described in Chapter 5, "Creating an Oracle Label Security Policy" or by using the SA_POLICY_ADMIN package as described in "SA_POLICY_ADMIN Policy Administration PL/SQL Package".

See Also:

"Authorized Levels"

"Oracle Enterprise Manager Cloud Control"

This section documents the supported keywords.

Note that when you create a policy, you can specify a string of default options to be used whenever the policy is applied without schema or table options being specified.

If a policy is first applied to a table, and then also applied to the schema containing that table, then the options on the table are not affected by the schema policy. The options of the policy originally applied to the table remain in force.

In general, administrators use the LABEL_DEFAULT policy option, causing data written by a user to be labeled with that user's row label. Alternatively, a labeling function can be used to label the data. If neither of these two choices is used, then a label must be specified in every INSERT statement. (Updates retain the row's original label.)

The following table suggests that certain combinations of policy enforcement options are useful when implementing an Oracle Label Security policy. As the table indicates, you might typically enforce READ_CONTROL and WRITE_CONTROL, choosing from among several possible combinations for setting the data label on writes.

Table 8-4 Suggested Policy Enforcement Option Combinations

Options
Access Enforcement

READ_CONTROL, WRITE_CONTROL, LABEL_DEFAULT

Read and write access based on session label. Default label provided; users can insert/update both data and labels.

READ_CONTROL, WRITE_CONTROL, Labeling Function

Read and write access based on session label. Users can set/change only row data; all row labels are set explicitly by the labeling function.

Add CHECK_CONTROL to restrict new labels (on insert or update) to visible range of labels.

READ_CONTROL, WRITE_CONTROL, LABEL_UPDATE

Read and write access based on session label. Users cannot change labels without privileges.

Add CHECK_CONTROL to restrict new labels (on insert or update) to visible range.

Exemptions from Oracle Label Security Policy Enforcement

Oracle Label Security is not enforced during DIRECT path export.

See Also:

"Using Oracle Data Pump Export with Oracle Label Security"

By design, Oracle Label Security policies cannot be applied to objects in schema SYS. As a consequence, the SYS user, and users making a DBA-privileged connection to the database (such as CONNECT AS SYSDBA) do not have Oracle Label Security policies applied to their actions. DBAs need to be able to administer the database. It would make no sense, for example, to export part of a table due to an Oracle Label Security policy being applied. The database user SYS is thus always exempt from Oracle Label Security enforcement, regardless of the export mode, application, or utility used to extract data from the database.

See Also:

For other DBA-related considerations, see Chapter 12, "Performing DBA Functions Under Oracle Label Security".

Similarly, database users granted the EXEMPT ACCESS POLICY privilege, either directly or through a database role, are exempted from some Oracle Label Security policy enforcement controls such as READ_CONTROL and CHECK_CONTROL, regardless of the export mode, application or utility used to access the database or update its data. Refer to Table 8-2, "Policy Enforcement Options". The following policy enforcement options remain in effect even when EXEMPT ACCESS POLICY is granted:

INSERT_CONTROL, UPDATE_CONTROL, DELETE_CONTROL, WRITE_CONTROL, LABEL_UPDATE, and LABEL_DEFAULT.

If the Oracle Label Security policy specifies the ALL_CONTROL option, then all enforcement controls are applied except READ_CONTROL and CHECK_CONTROL.

EXEMPT ACCESS POLICY is a very powerful privilege and should be carefully managed.

Note that this privilege does not affect the enforcement of standard Oracle Database object privileges such as SELECT, INSERT, UPDATE, and DELETE. These privileges are enforced even if a user has been granted the EXEMPT ACCESS POLICY privilege.

Viewing Policy Options on Tables and Schemas

Use the following views to show the policy enforcement options currently applied to tables and schemas:

DBA_SA_TABLE_POLICIES

DBA_SA_SCHEMA_POLICIES

Using a Labeling Function

Application developers can create labeling functions. These programs can compute and return a label using a wide array of resources, including context variables (such as date or username) and data values.

The following sections describe how to use labeling functions.

Labeling Data Rows under Oracle Label Security

Understanding Labeling Functions in Oracle Label Security Policies

Creating a Labeling Function for a Policy

Specifying a Labeling Function in a Policy

Labeling Data Rows under Oracle Label Security

There are three ways to label data that is being inserted or updated:

Explicitly specify a label in every INSERT or UPDATE to the table.

Set the LABEL_DEFAULT option, which causes the session's row label to be used if an explicit row label is not included in the INSERT or UPDATE statement.

Create a labeling function, automatically calls on every INSERT or UPDATE statement and independently of any user's authorization.

The recommended approach is to write a labeling function to implement your rules for labeling data. If you specify a labeling function, then Oracle Label Security embeds a call to that function in INSERT and UPDATE triggers to compute a label.

For example, you could create a labeling function named my_label to use the contents of COL1 and COL2 of the new row to compute and return the appropriate label for the row. Then, you could insert, into your INSERT or UPDATE statements, the following reference:

my_label(:new.col1,:new.col2)

If you do not specify a labeling function, then specify the LABEL_DEFAULT option. Otherwise, you must explicitly specify a label on every INSERT or UPDATE statement.

Understanding Labeling Functions in Oracle Label Security Policies

Labeling functions enable you to consider, in your rules for assigning labels, information drawn from the application context. For example, you can use as a labeling consideration the IP address to which the user is attached. There are many opportunities to use SYS_CONTEXT in this way.

Note:

If the SQL statement is invalid, then an error will occur when you apply the labeling function to the table or policy. You should thoroughly test a labeling function before using it with tables.

Labeling functions override the LABEL_DEFAULT and LABEL_UPDATE options.

A labeling function is called in the context of a before-row trigger. This enables you to pass in the old and new values of the data record, as well as the old and new labels.

You can construct a labeling function to permit an explicit label to be passed in by the user.

All labeling functions must have return types of the LBACSYS.LBAC_LABEL data type. The TO_LBAC_DATA_LABEL function can be used to convert a label in character string format to a data type of LBACSYS.LBAC_LABEL. Note that LBACSYS must have the EXECUTE privilege on your labeling function. The owner of the labeling function must have the EXECUTE privilege on the TO_LBAC_DATA_LABEL function, with the GRANT option.

Note:

LBACSYS is a unique schema providing opaque types for Oracle Label Security. Refer to the discussions in Chapter 12, "Performing DBA Functions Under Oracle Label Security".

Creating a Labeling Function for a Policy

The following example shows how to create a labeling function.

 SQL> CREATE OR REPLACE FUNCTION sa_demo.gen_emp_label
           (Job varchar2,
            Deptno number,
            Total_sal number)
       Return LBACSYS.LBAC_LABEL
     as
       i_label varchar2(80);
     Begin
       /************* Determine Class Level *************/
       if total_sal > 2000 then
       i_label := 'L3:';
       elsif total_sal > 1000 then
       i_label := 'L2:';
       else
       i_label := 'L1:';
       end if;

       /************* Determine Compartment *************/
       IF Job in ('MANAGER','PRESIDENT') then
       i_label := i_label||'M:';
       else
       i_label := i_label||'E:';
       end if;
       /************* Determine Groups *************/
       i_label := i_label||'D'||to_char(deptno);
       return TO_LBAC_DATA_LABEL('human_resources',i_label);
     End;
     /

Note:

When Oracle Label Security is configured to work directly with Oracle Internet Directory, dynamic label generation is disabled, because labels are managed centrally in Oracle Internet Directory, using olsadmintool commands. Refer to Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory". So, if the label function generates a data label using a string value that is not already established in Oracle Internet Directory, then an error message results.

Specifying a Labeling Function in a Policy

The following example uses the sa_demo.gen_emp_label label from the example in the previous section to show how to specify a labeling function.

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY('human_resources','sa_demo','emp');
SA_POLICY_ADMIN.APPLY_TABLE_POLICY (

POLICY_NAME => 'human_resources',
SCHEMA_NAME => 'sa_demo',
TABLE_NAME  => 'emp',
TABLE_OPTIONS => 'READ_CONTROL,WRITE_CONTROL,CHECK_CONTROL',
LABEL_FUNCTION => 'sa_demo.gen_emp_label(:new.job,:new.deptno,:new.sal)',
PREDICATE => NULL);

Inserting Labeled Data Using Policy Options and Labeling Functions

This section explains how enforcement options and labeling functions affect the insertion of labeled data.

Evaluating Enforcement Control Options and INSERT

Inserting Labels When a Labeling Function Is Specified

Inserting Child Rows into Tables with Declarative Referential Integrity Enabled

Evaluating Enforcement Control Options and INSERT

When you attempt to insert or update data based on your authorizations, the outcome depends upon what policy enforcement controls are active.

If INSERT_CONTROL is active, then rows you insert can only have labels within your write authorizations. If you attempt to update data that you can read, but for which you do not have write authorization, an error is raised. For example, if you can read compartments A and B, but you can only write to compartment A, then if you attempt to insert data with compartment B, then the statement will fail.

If INSERT_CONTROL is not active, then you can use any valid label on rows you insert.

If the CHECK_CONTROL option is active, then rows you insert can only have labels you are authorized to read, even if the labels are generated by a labeling function.

Inserting Labels When a Labeling Function Is Specified

A labeling function takes precedence over labels entered by the user. If the administrator has set up an automatic labeling function, then no data label a user enters will have effect (unless the labeling function itself makes use of the user's proposed label). New row labels are always determined by an active labeling function, if present.

Note that a labeling function can set the label of a row being inserted to a value outside the range that the user writing that row can see. If such a function is in use, then the user can potentially insert a row but not be authorized to see that row. You can prevent this situation by specifying the CHECK_CONTROL option in the policy. If this option is active, then the new data label is checked against the user's read authorization, and if the user cannot read it, then the insert operation is not performed.

Inserting Child Rows into Tables with Declarative Referential Integrity Enabled

If a parent table is protected by declarative referential integrity, then inserting a child row is constrained by the requirement that the parent row be visible. The user must be able to see the parent row for the insert operation to succeed, that is, the user must have read access to the parent row.

If READ_CONTROL is active on the parent table, then the user's read authorization must be sufficient to authorize a SELECT operation on the parent row. For example, a user who cannot read department 20 cannot insert child rows for department 20. Note that all records will be visible if the user has FULL or READ privileges on the table or schema.

Updating Labeled Data Using Policy Options and Labeling Functions

The rules for updates in Oracle Label Security are almost identical to those for inserts, as long as the user is authorized to change the rows in question. This section contains these topics:

Updating Labels Using CHAR_TO_LABEL

Evaluating Enforcement Control Options and UPDATE

Updating Labels When a Labeling Function Is Specified

Updating Child Rows in Tables with Declarative Referential Integrity Enabled

Updating Labels Using CHAR_TO_LABEL

If you need to change a row's label from SENSITIVE to CONFIDENTIAL, then you can change the label by using the CHAR_TO_LABEL function as follows:

UPDATE emp
SET hr_label = char_to_label ('HR', 'CONFIDENTIAL')
WHERE ename = 'ESTANTON';

Evaluating Enforcement Control Options and UPDATE

When you attempt to update data based on your authorizations, the outcome depends on what enforcement controls are active.

If UPDATE_CONTROL is active, then you can only update rows whose labels fall within your write authorizations. If you attempt to update data that you can read, but for which you do not have write authorization, then an error is raised. Assume, for example, that you can read compartments A and B, but you can only write to compartment A. In this case, if you attempt to update data with compartment B, then the statement will fail.

If UPDATE_CONTROL is not active, then you can update all rows to which you have read access.

If LABEL_UPDATE is active, then you must have the appropriate privilege (WRITEUP, WRITEDOWN, or WRITEACROSS) to change a label by raising or lowering its sensitivity level, or altering its groups or compartments.

If LABEL_UPDATE is not active but UPDATE_CONTROL is active, then you can update a label to any new label value within your write authorization.

If CHECK_CONTROL is active, then you can only write labels you are authorized to read.

The following figure illustrates the label evaluation process for LABEL_UPDATE.

Figure 8-1 Label Evaluation Process for LABEL_UPDATE

Updating Labels When a Labeling Function Is Specified

A labeling function takes precedence over labels entered by the user. If the administrator has set up an automatic labeling function, then no label a user enters will have effect (unless the labeling function itself makes use of the user's proposed label). New row labels are always determined by an active labeling function, if present.

Note that the security administrator can establish a labeling function that sets the label of a row being updated to a value outside the range that you can see. If this is the case, then you can update a row, but not be authorized to see the row. If the CHECK_CONTROL option is on, then you will not be able to perform such an update. The CHECK_CONTROL option verifies your read authorization on the new label.

Updating Child Rows in Tables with Declarative Referential Integrity Enabled

If a child row is in a table that has a referential integrity constraint, then the update can succeed only if the parent row is visible that is the user must be able to see the parent row. If the parent table has READ_CONTROL on, then the user's read authorization must be sufficient to authorize a SELECT on the parent row.

For example, a user who cannot read department 20 in a parent table cannot update an employee's department to department 20 in a child table. (If the user has FULL or READ privilege, then all records will be visible.)

See Also:

Oracle Database Development Guide

Deleting Labeled Data Using Policy Options and Labeling Functions

This section covers the deletion of labeled data.

If DELETE_CONTROL is active, then you can delete only rows within your write authorization.

If DELETE_CONTROL is not active, then you can delete only rows that you can read.

With DELETE_CONTROL active, and declarative referential integrity defined with cascading deletes, you must have write authorization on all the rows to be deleted, or the statement will fail.

You cannot delete a parent row if there are any child rows attached to it, regardless of your write authorization. To delete such a parent row, you must first delete each of the child rows. If DELETE_CONTROL is active on any of the child rows, then you must have write authorization to delete the child rows.

Consider, for example, a situation in which the user is UNCLASSIFIED and there are three rows as follows:

Row | Table | Sensitivity
Parent row: | DEPT | UNCLASSIFIED
Child row: | EMP | UNCLASSIFIED
Child row: | EMP | UNCLASSIFIED

In this case, the UNCLASSIFIED user cannot delete the parent row.

DELETE_CONTROL has no effect when DELETERESTRICT is active. DELETERESTRICT is always enforced. In some cases (depending on the user's authorizations and the data's labels) it may look as though a row has no child rows, when it actually does have children but the user cannot see them. Even if a user cannot see child rows, he still cannot delete the parent row.

Using a SQL Predicate with an Oracle Label Security Policy

You can use a SQL predicate to provide extensibility for selective enforcement of data access rules.

This section contains these topics:

Modifying an Oracle Label Security Policy with a SQL Predicate

Affecting Oracle Label Security Policies with Multiple SQL Predicates

Modifying an Oracle Label Security Policy with a SQL Predicate

A SQL predicate is a condition, optionally preceded by AND or OR. It can be appended for READ_CONTROL access mediation. The following predicate, for example, adds an application-specific test based on COL1 to determine if the session has access to the row.

AND my_function(col1)=1

The combined result of the policy and the user-specified predicate limits the rows that a user can read. So, this combination affects the labels and data that CHECK_CONTROL will permit a user to change. An OR clause, for example, increases the number of rows a user can read.

A SQL predicate can be useful if you want to avoid performing label-based filtering. In certain situations, a SQL predicate can easily implement row-level security on tables. Used instead of READ_CONTROL, a SQL predicate will filter the data for SELECT, UPDATE, and DELETE operations.

Similarly, in a typical, Web-enabled human resources application, a user might have to be a manager to access rows in the employee table. In such cases, the user's user label would have to dominate the label on the employee's row. A SQL predicate like the following could be added, so that an employee could bypass label-based filtering if he wanted to view his own record in the employee table. (An OR is used so that either the label policy will apply, or this statement will apply.)

OR SYS_CONTEXT ('USERENV', 'SESSION_USER') = employee_name

This predicate enables you to have additional access controls so that each employee can access his or her own record.

You can use such a predicate in conjunction with READ_CONTROLs or as a standalone predicate even if READ_CONTROL is not implemented.

Note:

Verify that the predicate accomplishes your security goals before you implement it in an application.

If a syntax error occurs in a predicate under Oracle Label Security, then an error will not arise when you try to apply the policy to a table. Rather, a predicate error message will arise when you first attempt to reference the table.

Affecting Oracle Label Security Policies with Multiple SQL Predicates

A predicate applied to a table by means of an Oracle Label Security policy is appended to any other predicates that may be applied by other Oracle Label Security policies, or by Oracle fine grain access control/VPD policies. The predicates are ANDed together.

Consider the following predicates applied to the EMP table in the SCOTT schema:

A predicate generated by an Oracle VPD policy, such as deptno=10

A label-based predicate generated by an Oracle Label Security policy, such as label=100, with a user-specified predicate such as

OR SYS_CONTEXT ('USERENV', 'SESSION_USER') = ename

Correct: These predicates would be ANDed together as follows:

WHERE deptno=10 AND (label=100 OR SYS_CONTEXT ('USERENV', 'SESSION_USER') = ename)

Incorrect: The predicates would not be combined in the following way:

WHERE deptno=10 AND label=100 OR SYS_CONTEXT ('USERENV', 'SESSION_USER') = ename

9 Administering and Using Trusted Stored Program Units

This chapter explains how to use trusted stored program units to enhance system security. It contains these topics:

Introduction to Trusted Stored Program Units

Creating and Compiling Trusted Stored Program Units

Setting and Returning Label Information

Introduction to Trusted Stored Program Units

Oracle Database stored procedures, functions, and packages are sets of PL/SQL statements stored in a database in compiled form. The single difference between functions and procedures is that functions return a value and procedures do not. Trusted stored program units are like any other stored program units in Oracle Database: the underlying logic is the same.

A package is a set of procedures and functions, together with the cursors and variables they use, stored as a unit. There are two parts to a package, the package specification and the package body. The package specification declares the external definition of the public procedures, functions, and variables that the package contains. The package body contains the actual text of the procedures and functions, as well as any private procedures and variables.

A trusted stored program unit is a stored procedure, function, or package that has been granted one or more Oracle Label Security privileges. Trusted stored program units are typically used to let users perform privileged operations in a controlled manner, or update data at several labels. This is the optimal approach to permit users to access data beyond their authorization.

Trusted stored program units provide fine-grained control over the use of privileges. Although you can potentially grant privileges to many users, the granting of privileges should be done with great discretion because it might violate the security policy established for your application. Rather than assigning privileges to users, you can identify any application operations requiring privileges, and implement them as trusted program units. When you grant privileges to these stored program units, you effectively restrict the Oracle Label Security privileges required by users. This approach employs the principle of least privilege.

For example, if a user with the label CONFIDENTIAL needs to insert data into SENSITIVE rows, then you can grant the WRITEUP privilege to a trusted stored program to which the user has access. In this way, the user can perform the task by means of the trusted stored program, while staying at the CONFIDENTIAL level.

The trusted program unit performs all the actions on behalf of the user. You can thus effectively encapsulate the security policy into a module that can be verified to make sure that it is valid.

How a Trusted Stored Program Unit Runs

A trusted stored program unit runs using its own privileges, and the caller's labels. In this way, it can perform privileged operations on the set of rows constrained by the user's labels.

Oracle Database system and object privileges are intended to be bundled into roles. Users are then granted roles as necessary. By contrast, Oracle Label Security privileges can only be assigned to users or to stored program units. These trusted stored program units provide a more manageable mechanism than roles to control the use of Oracle Label Security privileges.

Trusted Stored Program Unit Example

A trusted stored program unit with the READ privilege can read all unprotected data and all data protected by this policy in the database. Consider, for example, a user who is responsible for creating purchasing forecast reports. The user must perform a summation operation on the amount of all purchases. Regardless of whether or not user's own labels authorize access to the individual purchase orders. The syntax for creating the summation procedure in this example is as follows:

CREATE FUNCTION sum_purchases RETURN NUMBER IS
  psum NUMBER;
BEGIN
  SELECT SUM(amount) INTO psum
  FROM purchase_orders;
RETURN psum;
END sum_purchases;

In this way, the program unit can gather information the end user is not able to gather, and can make it available by means of a summation.

Note that to run SUM_PURCHASES, the user would need to be granted the standard Oracle Database EXECUTE object privilege upon this procedure.

See Also:

Chapter 3, "Understanding Access Controls and Privileges"

Creating and Compiling Trusted Stored Program Units

This section contains these topics:

Creating Trusted Stored Program Units

Setting Privileges for Trusted Stored Program Units

Recompiling Trusted Stored Program Units

Re-creating Trusted Stored Program Units

Running Trusted Stored Program Units

Creating Trusted Stored Program Units

You create a trusted stored program unit in the same way that you create a standard procedure, function, or package, that is by using the CREATE PROCEDURE, CREATE FUNCTION, or CREATE PACKAGE and CREATE PACKAGE BODY statements. The program unit becomes trusted when you grant it Oracle Label Security privileges.

See Also:

Oracle Database SQL Language Quick Reference

Setting Privileges for Trusted Stored Program Units

When a developer creates a stored program unit, the Oracle Label Security administrator can verify the correctness of the code before granting the necessary privileges to the stored program unit. Whenever the trusted stored program unit is re-created or replaced, its privileges are removed. The Oracle Label Security administrator must then verify the code again and grant the privileges once again.

Warning:

When you create a trusted stored program unit, have the Oracle Label Security administrator review it carefully and evaluate the privileges you are granting to it. Ensure, for example, that procedures in trusted packages do not perform privileged database operations and then write result or status information into a public variable of the package. In this way, you can make sure that no violations of your site's Oracle Label Security policy can occur.

See Also:

"SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

Recompiling Trusted Stored Program Units

Recompiling a trusted stored program unit, either automatically or manually (using ALTER PROCEDURE), does not affect its Oracle Label Security privileges. You must, however, grant the EXECUTE privilege on the program unit again after recompiling.

Re-creating Trusted Stored Program Units

Oracle Label Security privileges are revoked if you perform a CREATE OR REPLACE operation on a trusted stored program unit. This limits the potential for misuse of a procedure's Oracle Label Security privileges. Note that the procedure, function, or package can still run even if the Oracle Label Security privileges have been removed.

If you re-create a procedure, function, or package, then you should carefully review its text. When you are certain that the re-created program unit does not violate your site's Oracle Label Security policy, you can then grant it the required privileges again.

In a development environment where trusted stored program units must frequently be replaced (for example, during the first few months of a live system), it is advisable to create a script that can grant the proper Oracle Label Security privileges, as required.

Running Trusted Stored Program Units

Under Oracle Label Security all the standard Oracle Database controls on procedure call (regarding access to tables and schemas) are still in force. Oracle Label Security complements these security mechanisms by controlling access to rows. When a trusted stored program unit is carried out, the policy privileges in force are a union of the invoking user's privileges and the program unit's privileges. Whether a trusted stored program unit calls another trusted program unit or a non-trusted program unit, the program unit called runs with the same privileges as the original program unit.

If a sequence of non-trusted and trusted stored program units is carried out, the first trusted program unit will determine the privileges of the entire calling sequence from that point on. Consider the following sequence:

Procedure A (non-trusted)
Procedure B with WRITEUP
Procedure C with WRITEDOWN
Procedure D (non-trusted)

Here, Procedures B, C, and D all runs with the WRITEUP privilege, because B was the first trusted procedure in the sequence. When the sequence ends, the privilege pertaining to Procedure B is no longer in force for subsequent procedures.

Note:

Unhandled exceptions raised in trusted program units are caught by Oracle Label Security. This means that error messages may not be displayed to the user. For this reason, you should always thoroughly test and debug any program units before granting them privileges.

Setting and Returning Label Information

You can use the SA_UTL package for several functions within PL/SQL programs that return information about the current values of the session security attributes, in the form of numeric label values. Although these functions can be used in program units that are not trusted, they are primarily for use in trusted stored program units.

Note that these are public functions; you do not need the policy_DBA role to use them. In addition, each of the functions has a parallel SA_SESSION function that returns the same labels in character string format.

See Also:

"SA_UTL PL/SQL Utility Functions and Procedures"

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

10 Auditing Under Oracle Label Security

This chapter explains how to use Oracle Label Security auditing if you have not configured your database to use unified auditing. It contains these topics:

Overview of Oracle Label Security Auditing

Enabling Systemwide Auditing: AUDIT_TRAIL Initialization Parameter

Enabling Oracle Label Security Auditing

Oracle Label Security and Unified Auditing

Oracle Label Security Auditing Tips

Overview of Oracle Label Security Auditing

Oracle Label Security auditing supplements standard Oracle Database auditing by tracking use of its own administrative operations and policy privileges. You can use either the SA_AUDIT_ADMIN package or Oracle Enterprise Manager to set and change the auditing options for an Oracle Label Security policy.

When you create a new policy, a label column for that policy is added to the database audit trail. The label column is created regardless of whether auditing is enabled or disabled, and independent of whether database auditing or operating system auditing is used. Whenever a record is written to the audit table, each policy provides a label for that record to indicate the session label. The administrator can create audit views to display these labels. Note that in the audit table, the label does not control access to the row, instead it only records the sensitivity of the row.

The auditing options that you specify apply only to subsequent sessions, not to the current session. You can specify audit options even if auditing is disabled. No overhead is created by making only these specifications. When you do enable Oracle Label Security auditing, the options come into effect, and overhead is created beyond that created by standard Oracle Database auditing.

Note that Oracle Label Security does not provide labels for audit data written to the operating system audit trial. All Oracle Label Security audit records are written directly to the database audit trail, even if operating system auditing is enabled. If auditing is disabled, then no Oracle Label Security audit records are generated.

Enabling Systemwide Auditing: AUDIT_TRAIL Initialization Parameter

For Oracle Label Security to generate audit records, you must first enable systemwide auditing by setting the Oracle Database AUDIT_TRAIL initialization parameter in the database's parameter file. The parameter can be set to one of the following values:

Table 10-1 AUDIT_TRAIL Parameter Settings

Setting
Explanation

DB

Enables database auditing and directs all audit records to the database audit trail. This approach is recommended by Oracle.

Note that even with AUDIT_TRAIL set to DB, some records are always sent to the operating system audit trail. These include STARTUP and SHUTDOWN statements, as well as CONNECT AS SYSOPER or SYSDBA.

DB, EXTENDED

Does all actions of AUDIT_TRAIL=DB and also populates the SqlBind and SqlText CLOB-type columns of the AUD$ table.

OS

Enables operating system auditing. This directs most of your Oracle Database audit records to the operating system, rather than to the database; the records will not contain Oracle Label Security labels. By contrast, any Oracle Label Security auditing will go to the database, with labels.

If you set AUDIT_TRAIL to OS, then the Oracle Label Security-specific audit records are written to the database audit trail and the other Oracle Database audit records are written to the operating system audit trail (with no policy column in the operating system data).

NONE

Disables auditing. This is the default.

After you have edited the parameter file, restart the database instance to enable or disable database auditing as specified.

Set the AUDIT_TRAIL parameter before you set audit options. If you do not set this parameter, then you are still able to set audit options. However, audit records are not written to the database until the parameter is set and the database instance is restarted.

See Also:

For information about enabling and disabling systemwide auditing, setting audit options, and managing the audit trail, refer to Oracle Database Security Guide

For information about editing initialization parameters, refer to Oracle Database Reference

For details about systemwide AUDIT and NOAUDIT functioning, see Oracle Database SQL Language Reference

Enabling Oracle Label Security Auditing

After you have enabled systemwide auditing, you can enable or disable Oracle Label Security auditing. To use Oracle Label Security auditing, you must have the policy_DBA role and use the SA_AUDIT_ADMIN PL/SQL package procedures.

See Also:

"SA_AUDIT_ADMIN Oracle Label Security Auditing PL/SQL Package"

Oracle Label Security and Unified Auditing

Oracle Database uses the unified audit trail to capture information from various audit sources, including Oracle Label Security.You can configure OLS auditing using audit policies. Oracle Label Security auditing in Oracle Database 12c Release 1 (12.1) enables you to audit additional events such as enabling and disabling of OLS policies.

If you have upgraded your database to Oracle Database 12c Release 1 (12.1), but have not configured it to use unified auditing, then you must use the pre-12c OLS auditing described in this chapter.

See Also:

Oracle Database Upgrade Guide for instructions on configuring your upgraded database to use unified auditing. After migration, you can find the OLS unified audit information at Oracle Database Security Guide

The Oracle Database audit facility lets you hold database users accountable for the operations they perform. It can track specific database objects, operations, users, and privileges. Oracle Label Security supplements this by tracking use of its own administrative operations and policy privileges. It provides the SA_AUDIT_ADMIN package to set and change the policy auditing options.

Oracle Label Security Auditing Tips

This section contains these topics:

Strategy for Setting SA_AUDIT_ADMIN Options

Auditing Privileged Operations

Strategy for Setting SA_AUDIT_ADMIN Options

Before setting any audit options, you must devise an auditing strategy that monitors events of interest, without recording extraneous events. You should periodically review this strategy, because applications, user base, configurations, and other external factors can change.

The Oracle Label Security options, and those provided by the Oracle Database audit facility, might not directly address all of your specific or application-dependent auditing requirements. However, through use of database triggers, you can audit specific events and record specific information that you cannot audit and record using the more generic audit facility.

See Also:

For more information about using triggers for auditing, see Oracle Database Concepts

Auditing Privileged Operations

Consider auditing any operations that require Oracle Label Security privileges. Because these privileges perform sensitive operations, and because their abuse could jeopardize security, you should closely monitor their dissemination and use.

11 Using Oracle Label Security with a Distributed Database

This chapter describes special considerations for using Oracle Label Security in a distributed configuration. It contains the following sections:

An Oracle Label Security Distributed Configuration

Connecting to a Remote Database Under Oracle Label Security

Establishing Session Label and Row Label for a Remote Session

Setting Up Labels in a Distributed Environment

Using Oracle Label Security Policies in a Distributed Environment

Using Replication with Oracle Label Security

An Oracle Label Security Distributed Configuration

A network configuration that supports distributed databases can include multiple Oracle Database servers, or other database servers, running on the same or different operating systems. Each cooperative server in a distributed system communicates with other clients and servers over a network.

Figure 11-1, "Using Oracle Label Security with a Distributed Database" illustrates a distributed database that includes clients and servers with and without Oracle Label Security. As described in this chapter, if you establish database links from the WESTERN_REGION database to the EASTERN_REGION database, then you can access data if your user ID on EASTERN_REGION is authorized to see it, even if locally (on WESTERN_REGION) you do not have this access.

Figure 11-1 Using Oracle Label Security with a Distributed Database

Connecting to a Remote Database Under Oracle Label Security

Distributed databases act in the standard way with Oracle Label Security: the local user ends up connected as a particular remote user. Oracle Label Security protects the labeled data, whether you connect locally or remotely. If the remote user has the proper labels, then you can access the data. If not, then you cannot access the data.

The database link sets up the connection to the remote database and identifies the user who will be associated with the remote session. Your Oracle Label Security authorizations on the remote database are based on those of the remote user identified in the database link.

For example, local user JANE might connect as remote user AUSTEN, in the database referenced by the connect string sales, as follows:

CREATE DATABASE LINK sales
  CONNECT TO austen IDENTIFIED BY pride
  USING 'sales'

When JANE connects, her authorizations are based on the labels and privileges of remote user AUSTEN, because AUSTEN is the user identified in the database link. When JANE makes the first reference to the remote database, the remote session is actually established. For example, the remote session would be created if JANE enters:

SELECT * FROM emp@sales

You need not be an Oracle Label Security policy user in the local database. If you connect as a policy user on the remote database, you can access protected data.

Establishing Session Label and Row Label for a Remote Session

When connecting remotely, you can directly control the session label and row label in effect when you establish the connection. When you connect, Oracle Label Security passes these values (for all policies) over to the remote database. Notice that:

The local session label and row label are used as the default for the remote session, if they are valid for the remote user.

The remote session is constrained by the minimum and maximum authorizations of the remote user.

Although the local user's session labels are passed to the remote database, the local user's privileges are not passed. The privileges for the remote session are those associated with the remote user.

Consider a local user, Diana, with a maximum level of HS, and a session level of S. On the remote database, the remote user identified in the database link has a maximum level of S.

If Diana's session label is S when the database link is established, then the S label is passed over. This is a valid label. Diana can connect and read SENSITIVE data.

If Diana's session label is HS when the database link is established, then the HS level is passed across, but it is not valid for the remote user. Diana will pick up the remote user's default label (S).

Be aware of the label at which you are running the first time you connect to the remote database. The first time you reference a database link, your local session labels are sent across to the remote system when a connection is made. Later, you can change the label, but to do so, you must run the SA_SESSION.SET_LABEL procedure on the remote database.

Diana can connect at level HS, set the label to S, and then perform a remote access. Connection is implicitly made when the database link is established. Her default label is S on the remote database.

On the local database, Diana can set her session label to her maximum level of HS, but if the label of the remote user is set to S, then she can only retrieve S data from the remote database. If she performs a distributed query, then she will get HS data from the local database, and S data from the remote database.

Setting Up Labels in a Distributed Environment

It is advisable to use the same label component definitions and label tags on any database that is to be protected by the policy.

Setting Label Tags in a Distributed Environment

Setting Numeric Form of Label Components in a Distributed Environment

Setting Label Tags in a Distributed Environment

In a distributed environment, you may choose to use the same label tags across multiple databases. However, if you choose not to use the same tags across multiple databases, then you should retrieve the character form of the label when performing remote operations. This will ensure that the labels are consistent.

In the following example, the character string representation of the label string is the same. However, the label tag does not match. If the retrieved label tag has a value of 11 on the WESTERN_REGION database but a tag of 2001 on the EASTERN_REGION database, then the tags have no meaning. Serious consequences can result.

Figure 11-2 Label Tags in a Distributed Database

When retrieving labels from a remote system, you should return the character string representation (rather than the numeric label tag), unless you are using the same numeric labels on both databases.

If you allow Oracle Label Security to automatically generate labels on different databases, then the label tags will not be identical. Character strings will have meaning, but the numeric values will not, unless you have predefined labels with the same label tags on both instances.

To avoid the complexities of label tags, you can convert labels to strings on retrieval (using LABEL_TO_CHAR) and use CHAR_TO_LABEL when you store labels. Operations will succeed as long as the component names are the same.

Setting Numeric Form of Label Components in a Distributed Environment

In a distributed environment, you should use the same relative ranking of the numeric form of the level component, to ensure proper sorting of the labels.

In the following example, the levels in the two databases are effectively the same. Although the numeric form is different, the relative ranking of the levels numeric form is the same. As long as the relative order of the components is the same, the labels are perceived as identical.

Figure 11-3 Label Components in a Distributed Database

Using Oracle Label Security Policies in a Distributed Environment

Oracle Label Security supports all standard Oracle Database distributed configurations. Whether or not you can access protected data depends on the policies installed in each distributed database.

Be sure to take into account the relationships between databases in a distributed environment:

If the same application runs on two databases and you want them to have the same protection, then you must apply the same Oracle Label Security policy to both the local and the remote databases.

If the local and remote databases have a policy in common, then your local session label and row label will override the default labels for the remote user.

If the remote database has a different policy than the local database, then the remote policy can restrict access to the data independent of your local policies. On the other hand, when you make a connection as a remote user who has authorization on the remote policy, you can access any data to which the remote user has access to, regardless of your local authorizations.

If the remote database has no policy applied to it, you can access its data just as you would with a standard distributed database.

Consider a situation in which three databases exist, with different Oracle Label Security policies in force:

Database 1 has Policy A and Policy B

Database 2 has Policy A

Database 3 had Policy C

Users authorized for Policy A can obtain protected data from Database 1 and Database 2. If the remote user is authorized for Policy C, then this user can obtain data from Database 3 as well.

Using Replication with Oracle Label Security

This section explains how to use the replication option with tables protected by Oracle Label Security policies. It contains these topics:

Introduction to Replication Under Oracle Label Security

Contents of a Materialized View

Requirements for Creating Materialized Views Under Oracle Label Security

How to Refresh Materialized Views

See Also:

For a complete explanation of replication in Oracle Database 12c and how to set up the replication environment, refer to Oracle Database Advanced Replication

For general information about using materialized views, refer to Oracle Database Concepts and Oracle Database Data Warehousing Guide

Introduction to Replication Under Oracle Label Security

This section introduces the use of replication under Oracle Label Security. It contains the following topics:

Replication Functionality Supported by Oracle Label Security

Row-Level Security Restriction on Replication Under Oracle Label Security

Replication Functionality Supported by Oracle Label Security

Oracle Label Security supports standard replication and Advanced Replication, including multimaster replication and updatable materialized views (snapshots).

Oracle Database uses materialized views for replicating data. A materialized view is a local copy of a local or remote master table that reflects a recent state of the master table.

As illustrated in Figure 11-4, "Use of Materialized Views for Replication", a master table is a table you wish to replicate, on a node that you designate as the master node. Using a dblink account (such as REPADMIN), you can create a materialized view of the table in a different database. (This can also be done in the same database, and on the same system.) You can select rows from the remote master table, and copy them into the local materialized view. Here, mvEMP represents the materialized view of table EMP, and mlog$_EMP represents the materialized view log.

Figure 11-4 Use of Materialized Views for Replication

In a distributed environment, a materialized view alleviates query traffic over the network and increases data availability when a node is not available.

Row-Level Security Restriction on Replication Under Oracle Label Security

An Oracle Label Security policy applies Row Level Security (RLS) to a table if READ_CONTROL is specified as one of the policy options. Problems occur if both of the following conditions are true:

The Oracle Label Security policy is applied to any table relevant to replication (such as the master table, materialized view, or materialized view log), and

The policy returns a predicate in the WHERE clause of SELECT statements.

To avoid the additional predicate (and therefore avoid this problem), the users involved in a replication environment should be given the necessary Oracle Label Security privileges. To be specific, the designated users in the database link (such as REPADMIN and the materialized view owner) must have the READ or the FULL privilege. As a result, the queries used to perform the replication will not be modified by RLS.

See Also:

Oracle Database 2 Day + Security Guide

Contents of a Materialized View

This section discusses the contents of materialized views.

How Materialized View Contents Are Determined

Complete Materialized Views

Partial Materialized Views

How Materialized View Contents Are Determined

Oracle Label Security performs the following steps when creating materialized views. These steps determine the contents of the view.

It reads the definition of the master table in the remote database.

It reads the rows in the master table that meet the conditions defined in the materialized view definition.

It writes these rows to the materialized view in the local database.

Because Oracle Label Security writes only those rows to which you have write access in the local database, the contents of the materialized view vary according to:

The policy options in effect

The privileges you have defined in the local database

The session label

Complete Materialized Views

If you read all of the rows in the master table and have write access in the local database to each label in the materialized view, then the result is a complete materialized view of the master table. To ensure that the materialized view is complete, ensure that you have read access to all of the data in the master table and write access in the local database to all labels at which data is stored in the master table.

Note:

Never revoke privileges that you granted when you created the materialized view. If you do, then you may not be able to perform a replication refresh.

Partial Materialized Views

A partial materialized view is created when you specify a WHERE clause in the materialized view definition. This is a convenient way to pass subsets of data to a remote database.

Note:

To create a partial materialized view, you must have write access to all the rows being replicated.

Requirements for Creating Materialized Views Under Oracle Label Security

Requirements for creating a materialized view depend on the type of materialized view you are creating.

Requirements for a Replication Administrator

Requirements for the Owner of the Materialized View

Requirements for Creating Partial Multilevel Materialized Views

Requirements for Creating Complete Multilevel Materialized Views

Requirements for a Replication Administrator

Requirements for a replication administrator, typically using a REPADMIN account, vary depending on the configuration. In general, however, it should meet the following requirements:

It must have the FULL Oracle Label Security privilege (mandatory for all configurations).

It must have the SELECT privilege on the master table.

It must be the account that establishes the database link from the remote node to the database containing the master table.

See Also:

Oracle Database Advanced Replication for further information about the replication administrator and REPADMIN account

Requirements for the Owner of the Materialized View

Remember that the privileges belonging to the owner of the materialized view are used during the refresh of the materialized view. If these privileges are not sufficient, then there are two options:

The materialized view can be created in the REPADMIN account, or

Additional privileges must be granted to the owner of the materialized view.

Consider, for example, the following materialized view created by user SCOTT:

CREATE MATERIALIZED VIEW mvemp as
SELECT *
FROM EMP@link_to_master
WHERE label_to_char(sa_label) = 'HS';

Here, SCOTT should have permission to insert records at the HS level in the local database. If Oracle Label Security policies are applied on the materialized view, then SCOTT must have the FULL privilege to avoid the RLS restriction.

Different configurations can be set up depending on whether Oracle Label Security policies are applied on the materialized view, what privileges are granted to the owner of the materialized view, and so on. If Oracle Label Security policies are applied to the materialized view, but SCOTT should not be granted the FULL privilege, then the REPADMIN account must be used to create the materialized view. SCOTT can then be granted the SELECT privilege on that table.

If no policies are applied to the materialized view, then the view can be created in SCOTT's schema without any additional privileges. In this case, the materialized view should be created in such a way that a WHERE condition limits the records to those which SCOTT can read.

Finally, if SCOTT can be granted the FULL privilege, then the materialized view can be created in SCOTT's schema, and Oracle Label Security policies can also be applied on the materialized view.

Note that the master table can have Oracle Label Security policies containing any set of policy options. If SCOTT has the FULL or the READ privilege, he can select all rows, regardless of policy options.

Requirements for Creating Partial Multilevel Materialized Views

To create a partial materialized view that includes only some of the rows in a remote master table protected by Oracle Label Security, you must have sufficient privileges to WRITE in the local database at every label retrieved by your query.

Requirements for Creating Complete Multilevel Materialized Views

To create a complete materialized view that includes every row in a remote master table protected by Oracle Label Security, you must be able to WRITE in the local database at the labels of all of the rows retrieved by the defined materialized view query.

How to Refresh Materialized Views

If the contents or definition of a master table changes, then refresh the materialized view so that it accurately reflects the contents of the master table. To refresh a materialized view of a remote multilevel table, you must also have privileges to write in the local database at the labels of all of the rows that the materialized view query retrieves

Warning:

A materialized view can potentially contain outdated rows if you refresh a partial or full materialized view but do not have READ access to all the rows in the master table, and consequently do not overwrite the rows in the original materialized view with the updated rows from the master table.

To ensure an accurate materialized view refresh, use job queues to refresh the views automatically. These processes must have sufficient privileges both to read all of the rows in the master table and to write those rows to the materialized view, ensuring that the view is completely refreshed. Remember that the privileges used by these processes are those of the materialized view owner.

See Also:

Oracle Database Data Warehousing Guide for information about job queues

12 Performing DBA Functions Under Oracle Label Security

The standard Oracle Database utilities can be used under Oracle Label Security, but certain restrictions apply, which may require extra steps to get the expected results. This chapter describes these special considerations. It assumes that you are using policy label columns of the NUMBER data type.

The chapter contains these sections:

Using Oracle Data Pump Export with Oracle Label Security

Using Data Pump Import with Oracle Label Security

Using SQL*Loader with Oracle Label Security

Performance Tips for Oracle Label Security

Creating Additional Databases After Installation

Oracle Label Security Upgrades and Downgrades

Using Oracle Data Pump Export with Oracle Label Security

Oracle Data Pump enables high-speed movement of data and metadata from one database to another. This section covers the following topics:

Full Database Export

Schema and Table-Level Export

Full Database Export

Starting with Oracle Database 12c, Oracle Label Security metadata in the LBACSYS schema can be included when doing a full database export and import operation. The source database can be Oracle Database 11g Release 2 (11.2.0.3), or higher, but the target database must be Oracle Database 12c or higher.

Before starting the Data Pump import on the target database, you must enable Oracle Label Security.

Schema and Table-Level Export

The Data Pump export utility functions in the standard way under Oracle Label Security. There are, however, a few differences resulting from the enforcement of Oracle Label Security policies.

Note:

You must have the EXEMPT ACCESS POLICY privilege in order to export all rows in the table, or else no rows are exported.

For any tables protected by an Oracle Label Security policy, only rows with labels authorized for read access are exported. Unauthorized rows are not included in the export file. Consequently, to export all the data in protected tables, you must have a privilege (such as FULL or READ) that gives you complete access.

SQL statements to reapply policies are exported along with tables and schemas that are exported. These statements are carried out during import to reapply policies with the same enforcement options as in the original database.

The HIDE property is not exported. When protected tables are exported, the label columns in those tables are also exported (as numeric values). However, if a label column is hidden, then it is exported as a normal, unhidden column.

The user must have EXEMPT ACCESS POLICY in order to export all rows in the table, or else no rows are exported.

Using Data Pump Import with Oracle Label Security

Oracle Data Pump enables high-speed movement of data and metadata from one database to another. This section covers the following topics:

Full Database Import for the LBACSYS Schema Metadata

Schema and Table Level Import

Full Database Import for the LBACSYS Schema Metadata

Oracle Label Security metadata in the LBACSYS schema can be included when you perform a full database export and import operation. The source database can be Oracle Database 11g Release 2 (11.2.0.3), or higher, but the target database must be Oracle Database 12c Release 1 (12.1) or higher.

Oracle Data Pump import utility, impdp, automatically imports Label Security metadata including policies, labels, user authorizations, schema and table policy enforcements. You must register and enable Oracle Label Security for the target database before beginning the import operation.

See Also:

"Checking if Oracle Label Security Has Been Registered and Enabled"

Schema and Table Level Import

This section explains how the Data Pump Import utility functions under Oracle Label Security:

Requirements for Import Under Oracle Label Security

Defining Data Labels for Import

Importing Labeled Data Without Installing Oracle Label Security

Importing Unlabeled Data

Importing Tables with Hidden Columns

See Also:

Oracle Database Utilities

Requirements for Import Under Oracle Label Security

To use the impdp under Oracle Label Security, you must prepare the import database and ensure that the import user has the proper authorizations.

Preparing the Import Database

Before you can use the Import utility with Oracle Label Security, you must prepare the import database, as follows:

Ensure that Oracle Label Security is enabled. See "Checking if Oracle Label Security Has Been Registered and Enabled".

Create any Oracle Label Security policies that protect the data to be imported.

Ensure that the policies use the same column names as in the export database.

Define in the import database all of the label components and individual labels used in tables being imported.

Ensure that the same tag values are assigned to the policy labels in each database. (Note that if you are importing into a database from which you exported, then the components are most likely already defined.)

Verifying Import User Authorizations

To successfully import data under Oracle Label Security, you must be authorized to run the import operation for all of the labels required to insert the data and labels contained in the export file. Errors will be raised upon import if the following requirements are not met.

Requirement 1: To import tables or schemas with Label Security policies on them, you must have execute privilege on the SA_POLICY_ADMIN package.

To ensure that all rows can be imported, you must have the policy_DBA role for all policies with data being imported. After each schema or table is imported, any policies from the export database are reapplied to the imported objects.

Requirement 2: You must also have the ability to write all rows that have been exported as follows:

You can granted the FULL privilege or given sufficient authorization to write all labels contained in the import file.

A user-defined labeling function can be applied to the table.

See Also:

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

Defining Data Labels for Import

The label definitions at the time of import must include all the policy labels used in the export file. You can use the views DBA_SA_LEVELS, DBA_SA_COMPARTMENTS, DBA_SA_GROUPS, and DBA_SA_LABELS in the export database to design SQL scripts that re-create the label components and labels for each policy in the import database. The following example shows how to generate a PL/SQL block that re-creates the individual labels for the HR policy:

set serveroutput on
BEGIN
   dbms_output.put_line('BEGIN');
   FOR l IN (SELECT label_tag, label
                FROM dba_sa_labels
                WHERE policy_name='HR'
                ORDER BY label_tag) LOOP
       dbms_output.put_line
           ('  SA_LABEL_ADMIN.CREATE_LABEL(''HR'', ' ||
            l.label_tag || ', ''' || l.label || ''');');
   END LOOP;
   dbms_output.put_line ('END;');
   dbms_output.put_line ('/');
END;
/

If the individual labels do not exist in the import database with the same numeric values and the same character string representations as in the export database, then the label values in the imported tables will be meaningless. The numeric label value in the table may refer to a different character string representation, or it may be a label value that has not been defined at all in the import database.

If a user attempts to access rows containing invalid numeric labels, then the operation will fail.

Importing Labeled Data Without Installing Oracle Label Security

When policy label columns are defined as a NUMBER data type, they can be imported into databases that do not have Oracle Label Security installed. In this case, the values in the policy label column are imported as numbers. Without the corresponding Oracle Label Security label definitions, the numbers will not reference any specific label.

Note that errors will be raised during the import if Oracle Label Security is not installed, because the SQL statements to reapply the policy to the imported tables and schemas will fail.

Importing Unlabeled Data

You can import unlabeled data into an existing table protected by an Oracle Label Security policy. Either the LABEL_DEFAULT option or a labeling function must be specified for each table being imported, so that the labels for the rows can be automatically initialized as they are inserted into the table.

Importing Tables with Hidden Columns

A hidden column is exported as a normal column, but the fact that it was hidden is lost. If you want to preserve the hidden property of the label column, you must first create the table in the import database.

Before you perform the import, create the table and apply the policy with the HIDE option. This adds the policy label column to the table as a hidden column.

Then remove the policy from the table, so that the enforcement options specified in the export file can be reapplied to the table during the import operation.

Perform the import with IGNORE=Y. Setting the IGNORE parameter to Y ignores errors during import.

Manually apply the policy to the table with the HIDE option.

Using SQL*Loader with Oracle Label Security

SQL*Loader moves data from external files into tables in Oracle Database. This section contains these topics:

Requirements for Using SQL*Loader Under Oracle Label Security

Oracle Label Security Input to SQL*Loader

See Also:

Oracle Database Utilities for information about SQL*Loader, including log files, discard files, and bad files

Requirements for Using SQL*Loader Under Oracle Label Security

You can use SQL*Loader with the conventional path to load data into a database protected by Oracle Label Security. Because SQL*Loader performs INSERT operations, all of the standard requirements apply when using SQL*Loader on tables protected by Oracle Label Security policies.

Oracle Label Security Input to SQL*Loader

If the policy column for a table is hidden, then you must use the HIDDEN keyword to convey this information to SQL*Loader.

To specify row labels in the input file, include the policy label column in the INTO TABLE clause in the control file.

To load policy labels along with the data for each row, you can specify the CHAR_TO_LABEL function or the TO_DATA_LABEL function in the SQL*Loader control file.

Note:

When Oracle Label Security is installed to work with Oracle Internet Directory, dynamic label generation is not allowed, because labels are managed centrally in Oracle Internet Directory, using olsadmintool commands. Refer to Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory".

When Oracle Label Security is directory-enabled, then the function TO_DATA_LABEL is not available and generates an error message if used.

Table 12-1 shows the variations that you can use when you load Oracle Label Security data with SQL*Loader.

Table 12-1 Input Choices for Oracle Label Security Input to SQL*Loader

Form of Data
Explanation of Results

col1 hidden integer external

Hidden column loaded with tag value of data directly from data file

col2 hidden char(5) "func(:col2)"

Hidden column loaded with character value of data from data file.func() used to translate between the character label and its tag value. Note: func() might be char_to_label().

col3 hidden "func(:col3)"

Same as in col2, field type defaults to char

col4 hidden expression "func(:col4)"

Hidden column not mapped to input data.func() will be called to provide the label value. This could be a user function.

For example, the following is a valid INTO TABLE clause in a control file that is loading data into the DEPT table:

INTO TABLE dept
(hr_label HIDDEN POSITION (1:22) CHAR "CHAR_TO_LABEL('HR',:hr_label)",
deptno    POSITION (23:26) INTEGER EXTERNAL,
dname     POSITION (27:40) CHAR,
loc       POSITION(41,54)  CHAR)

The following could be an entry in the data file specified by this control file:

HS:FN                  231 ACCOUNTING  REDWOOD SHORES

Performance Tips for Oracle Label Security

This section explains how to achieve optimal performance with Oracle Label Security.

Using ANALYZE to Improve Oracle Label Security Performance

Creating Indexes on the Policy Label Column

Planning a Label Tag Strategy to Enhance Performance

Partitioning Data Based on Numeric Label Tags

Using ANALYZE to Improve Oracle Label Security Performance

Run the ANALYZE statement on the Oracle Label Security data dictionary tables in the LBACSYS schema, so that the cost-based optimizer can improve execution plans on queries. This will improve Oracle Label Security performance. See Oracle Database SQL Language Reference for the ANALYZE syntax.

Running ANALYZE on application tables improves the application SQL performance.

Creating Indexes on the Policy Label Column

By creating the appropriate type of index on the policy label column, you can improve the performance of user-raised queries on protected tables.

If you have applied an Oracle Label Security policy on a database table in a particular schema, then you should compare the number of different labels to the amount of data. Based on this information, you can decide which type of index to create on the policy label column.

If the cardinality of data in the policy label column (that is, the number of labels compared to the number of rows) is low, then consider creating a bitmapped index.

If the cardinality of data in the policy label column is high, then consider creating a B-tree index.

Consider the following case, in which the EMP table is protected by an Oracle Label Security policy with the READ_CONTROL enforcement option set, and HR_LABEL is the name of the policy label column. A user raises the following query:

SELECT COUNT (*) FROM SCOTT.EMP;

In this situation, Oracle Label Security adds a predicate based on the label column. For example:

SELECT COUNT (*) FROM SCOTT.EMP
  WHERE hr_label=100;

In this way, Oracle Label Security uses the security label to restrict the rows that are processed, based on the user's authorizations. To improve performance of this query, you could create an index on the HR_LABEL column.

Consider a more complex query (once again, with READ_CONTROL applied to the EMP table):

SELECT COUNT (*) FROM SCOTT.EMP
  WHERE deptno=10

Again, Oracle Label Security adds a predicate based on the label column:

SELECT COUNT (*) FROM SCOTT.EMP
  WHERE deptno=10
  AND hr_label=100;

In this case, you might want to create a composite index based on the DEPTNO and HR_LABEL columns, to improve application performance.

See Also:

Oracle Database Performance Tuning Guide

Planning a Label Tag Strategy to Enhance Performance

For optimal performance, you can plan a strategy for assigning values to label tags. In general, it is best to assign higher numeric values to labels with higher sensitivity levels. This is because, typically, many more users can see data at comparatively low levels and fewer users at higher levels can see many levels of data.

In addition, with READ_CONTROL set, Oracle Label Security generates a predicate that uses a BETWEEN clause to restrict the rows to be processed by the query. As illustrated in the following example, if the higher-sensitivity labels do not have a higher label tag than the lower-sensitivity labels, then the query will potentially examine a larger set of rows. This will affect performance.

Table 12-2 shows a set of label tags assigned as follows:

Table 12-2 Label Tag Performance Example: Correct Values

Label
Label Tag

TS:A,B

100

S:A

50

S

20

U:A

10

Here, a user whose maximum authorization is S:A can potentially access data at labels S:A, S, and U:A. Consider what happens when this user raises the following query:

SELECT COUNT (*) FROM SCOTT.EMP

Oracle Label Security adds a predicate that includes a BETWEEN clause (based on the maximum and minimum authorizations) to restrict the set of rows this user can see:

SELECT COUNT (*) FROM SCOTT.EMP
  WHERE hr_label BETWEEN 10 AND 50;

Performance improves, because the query examines only a subset of data based on the user's authorizations. It does not fruitlessly process rows that the user is not authorized to access.

Table 12-3 shows how unnecessary work is performed if the tag values were assigned as follows:

Table 12-3 Label Tag Performance Example: Incorrect Values

Label
Label Tag

TS:A,B

50

S:A

100

S

20

U:A

10

In this case, the user with S:A authorization can see only some of the labels between 100 and 10. Although the user cannot see TS:A,B labels (that is, rows with a label tag of 50). A query would nonetheless pick up and process these rows, even though the user ultimately will not have access to them.

Partitioning Data Based on Numeric Label Tags

If you are using a numeric ordering strategy with the numeric label tags that you have applied to the labels, then you can use this as a basis for Oracle Database data partitioning. Depending on the application, partitioning data based on label values may or may not be useful.

Consider, for example, a business-hosting CRM application to which many companies subscribe. In the same EMP table, there might be rows (and labels) for Subscriber 1 and Subscriber 2. That is, information for both companies can be stored in the same table, as long as it is labeled differently. In this case, employees of Subscriber 1 will never need to access data for Subscriber 2, so it might make sense to partition based on label. You could put rows for Subscriber 1 in one partition, and rows for Subscriber2 in a different partition. When a query is raised, it will access only one or the other partition, depending on the label. Performance improves because partitions that are not relevant are not examined by the query.

The following example shows this is done. It places labels in the 2000 series on one partition, labels in the 3000 series on another partition, and labels in the 4000 series on a third partition.

CREATE TABLE EMPLOYEE
       (EMPNO NUMBER(10) CONSTRAINT PK_EMPLOYEE PRIMARY KEY,
    ENAME VARCHAR2(10),
    JOB VARCHAR2(9),
    MGR NUMBER(4),
    HIREDATE DATE,
    SAL NUMBER(7,2),
    COMM NUMBER(7,2),
    DEPTNO NUMBER(4),
    HR_LABEL NUMBER(10))
    TABLESPACE PERF_DATA
    STORAGE (initial 2M
    NEXT 1M
    MINEXTENTS 1
    MAXEXTENTS unlimited)
    PARTITION BY RANGE (hr_label)
    (partition sx1 VALUES LESS THAN (2000) NOLOGGING,
     partition sx2 VALUES LESS THAN (3000),
     partition sx3 VALUES LESS THAN (4000) );

Creating Additional Databases After Installation

When you install the Oracle Database Enterprise Edition and Oracle Label Security, an initial Oracle database is created.

If you want to create additional databases, then you should do this using the Database Configuration Assistant. Alternatively, you can create additional databases by following the steps listed in Oracle Database Administrator's Guide.

Each time you create a new database, you must install the Oracle Label Security data dictionary tables, views, and packages into it, and create the LBACSYS account.

For the first database, this is done automatically when you install Oracle Label Security, regardless of whether or not you choose the custom install. If you do not choose the custom install, then you are installing the database with the label security schema in the seed.

To create additional databases, there are different processes for configuring label security, depending on whether the first database was installed with the custom install or with the label security schema in the seed.

Creating additional databases with the label security schema in the seed:

To configure label security if the database was installed with the label security schema in the seed:

Select the label security option in DBCA.

Select the check box to configure label security.

Creating additional databases with the custom install:

To configure label security after a custom database install:

Connect to the Oracle Database instance as user SYS, using the AS SYSDBA syntax.

Run the script $ORACLE_HOME/rdbms/admin/catols.sql.

This script installs the label-based framework, data dictionary, data types, and packages. After the script is run, the LBACSYS account exists, with the password LBACSYS. All the Oracle Label Security packages exist under this account.

Change the default password of the LBACSYS user.

If you initially chose custom install, but did not install label security, you can install and configure label security using either process described above.

Note:

You can also do this at a later time.

Now, you can proceed to create an Oracle Label Security policy.

See Also:

For a complete discussion of Oracle database creation, see Oracle Database Administrator's Guide

Oracle Label Security Upgrades and Downgrades

This section discusses upgrades and downgrades that you must make and describes the preprocess scripts you need to run.

As a safety measure, before you run either the upgrade or downgrade preprocess script, Oracle recommends that you back up your audit records. To do this, you can archive the audit trail as described in Oracle Database Security Guide.

Before they run, the preprocess scripts check that there is enough space in the audit tablespace to copy all the audit records, and will exit without processing if there is not.

You may continue running your applications on the database while OLS preprocess scripts are running.

See Also:

Oracle Database Upgrade Guide for requirements for upgrading databases that use Oracle Label Security and Oracle Database Vault

Oracle Label Security Release 12.1 Upgrades

Oracle Label Security Downgrades

Oracle Label Security Release 12.1 Upgrades

If you are upgrading from a database earlier than Oracle Database 12c Release 1 (12.1) that uses Oracle Label Security (OLS) or Database Vault, then you must perform an upgrade process.

Caution:

Running the olspreupgrade.sql script before upgrading is mandatory for upgrading databases earlier than Oracle Database 12c Release (12.1) that use Oracle Label Security or Database Vault.

After you have upgraded to Oracle Database Release 12c, you do not need to run the Oracle Label Security preprocessing script when you patch or upgrade the database.

Before performing the OLS upgrade process, you must run the OLS preprocess upgrade script, olspreupgrade.sql, to process the aud$ table contents.The OLS upgrade moves the aud$ table from the SYSTEM schema to the SYS schema. The olspreupgrade.sql script is a preprocessing script required for this move. It creates a temporary table, PREUPG_AUD$, in the SYS schema and moves the SYSTEM.aud$ records to SYS.PREUPG_AUD$. The moved records can no longer be viewed through the DBA_AUDIT_TRAIL view, but can be viewed by directly accessing the SYS.PREUPG_AUD$ table, until the upgrade completes. Once the upgrade completes, the SYS.PREUPG_AUD$ table is permanently deleted and all audit records, can be viewed through the DBA_AUDIT_TRAIL view.

To run the Oracle Label Security preprocess script before upgrading:

Copy the ORACLE_HOME/rdbms/admin/olspreupgrade.sql script from the newly installed Oracle home to the Oracle home of the database to be upgraded.

Connect to the database to be upgraded. At the system prompt, enter:

CONNECT SYS AS SYSDBA
Enter password password

Run the Oracle Label Security preprocess script:

@$ORACLE_HOME/rdbms/admin/olspreupgrade.sql

Note:

The upgrade status for the Oracle Label Security component will be marked INVALID if the Oracle Label Security preprocess script reports an error. If this happens, you must correct the errors and then rerun the upgrade process. See Oracle Database Upgrade Guide for more information about rerunning the upgrade process for Oracle Database.

Oracle Label Security Downgrades

If you are downgrading from an Oracle Database 12c Release 1 (12.1) or later database that uses Oracle Label Security (OLS) or Database Vault, then you must first do the following: run the OLS preprocess downgrade script, olspredowngrade.sql, to process the aud$ table contents.

The OLS downgrade script moves the aud$ table from the SYS schema to the SYSTEM schema. The olspredowngrade.sql script is a preprocessing script required in preparation for this move. It creates a temporary table, PREDWG_AUD$, in the SYSTEM schema and moves the SYS.aud$ records to SYSTEM.PREDWG_AUD$. The moved records can no longer be viewed through the DBA_AUDIT_TRAIL view, but can be viewed by directly accessing the SYSTEM.PREDWG_AUD$ table, until the downgrade completes. Once the downgrade completes, the SYSTEM.PREDWG_AUD$ table is permanently deleted and all audit records, can be viewed through the DBA_AUDIT_TRAIL view.

To run the OLS preprocess script before downgrading:

Connect to the database to be downgraded. At the system prompt, enter:

CONNECT SYS AS SYSDBA
Enter password password

Run the OLS preprocess downgrade script:

@$ORACLE_HOME/rdbms/admin/olspredowngrade.sql

13 Releasability Using Inverse Groups

This chapter discusses the Oracle Label Security implementation of releasability using inverse groups.

This chapter contains the following sections:

Introduction to Inverse Groups and Releasability

Comparing Standard Groups and Inverse Groups

How Inverse Groups Work

Algorithm for Read Access with Inverse Groups

Algorithm for Write Access with Inverse Groups

Algorithms for COMPACCESS Privilege with Inverse Groups

Session Labels and Inverse Groups

Changes in Behavior of Procedures with Inverse Groups

Dominance Rules for Labels with Inverse Groups

Introduction to Inverse Groups and Releasability

Inverse groups indicate releasability of information. They are used to mark the dissemination of data. When you add an inverse group to a data label, the data becomes less classified. For example, a user with inverse groups UK and US cannot access data that only has inverse group UK. Adding US to that data makes it accessible to all users with the inverse groups UK and US.

When you assign releasabilities to a user, you mark the communication channel to the user. For data to flow across the communication channel, the data releasabilities must dominate the releasabilities assigned to the user. In other words, releasabilities assigned to a data record must contain all the releasabilities assigned to a user.

The advantage of releasabilities lies in their power to broadly disseminate information. Releasing data to the entire marketing organization becomes as simple as adding the Marketing releasability to the data record.

Comparing Standard Groups and Inverse Groups

Groups in Oracle Label Security identify organizations that own or access data. Like standard groups, inverse groups control the dissemination of information. However, the behavior of inverse groups differs from Oracle Label Security standard group behavior. By default, all policies created in Oracle Label Security use the standard group behavior.

The term, releasabilities is sometimes used to refer to the behavior provided by inverse groups. When you include inverse groups in a data label, the effect is similar to assigning label compartment authorizations to a user. When Oracle Label Security evaluates whether a user can view a row of data assigned to a label with inverse groups, it checks to see whether the data, not the user, has the appropriate group authorizations. It checks whether the data has all the inverse groups assigned to the user. With standard groups, by contrast, Oracle Label Security checks to see whether a user is authorized for at least one of the groups assigned to a row of data.

Consider a policy that contains three standard groups such as, Eastern, Western, and Southern. User1's label authorizations include the groups Eastern and Western. Assuming that User1 has been assigned the appropriate level and compartment authorizations in the policy, then:

With standard Oracle Label Security groups, User1 can view all data records that have the group Eastern, or the group Western, or both Eastern and Western.

With inverse groups, User1 can only view data records that have, at a minimum, all the groups assigned to the user, that is, both Eastern and Western. User1 cannot view records that have only the Eastern group, only the Western group, or that have no groups at all.

Table 13-1 shows all the rows that User1 can potentially access, given the type of group that is used in the policy.

Table 13-1 Access to Standard Groups and Inverse Groups

If row label contains groups:
User1 access with standard groups?
User1 access with inverse groups?

None

Y

N

Eastern

Y

N

Western

Y

N

Southern

N

N

Eastern, Western

Y

Y

Eastern, Southern

Y

N

Western, Southern

Y

N

Eastern, Western, Southern

Y

Y

Standard groups indicate ownership of information. In this way, all data pertaining to a certain department can have that department's group in the label. When you add a group to a data label, the data becomes more classified. For example, a user with no groups can access data that has no groups in its label. If you add the group US to the data label, the user can no longer access the data.

See Also:

"Group Components"

How Inverse Groups Work

This section explains how inverse groups are implemented and how they work. It contains these topics:

Implementing Inverse Groups with the INVERSE_GROUP Enforcement Option

Inverse Groups and Label Components

Computed Labels with Inverse Groups

Inverse Groups and Hierarchical Structure

Inverse Groups and User Privileges

Implementing Inverse Groups with the INVERSE_GROUP Enforcement Option

When creating an Oracle Label Security policy, the administrator can specify whether the policy can use inverse group functionality to implement releasability. To do this, the administrator specifies INVERSE_GROUP as one of the default_options in the CREATE_POLICY statement.

The INVERSE_GROUP option can be set only at policy creation time. Once a policy is created, this option cannot be changed.

The INVERSE_GROUP option is thus policywide. It cannot be turned on or off when the policy is applied to a table or schema. If you attempt to do so, using the procedure APPLY_TABLE_POLICY or APPLY_SCHEMA_POLICY, then an error will be generated.

While other policy enforcement options can be dropped from a policy, the INVERSE_GROUP policy configuration option cannot be dropped once it is set. To remove the option, you must drop and then re-create the policy.

The administrator can give individual users authorization for one or more inverse groups.

Inverse Groups and Label Components

When an Oracle Label Security policy is created with the inverse group option, the components in the policy label (levels, compartments, and groups) are the same as with standard groups. With inverse groups, however, the user's read groups and write groups have a different meaning and role in data access.

Consider the following policy example, with three levels, one compartment, and three groups:

Table 13-2 Policy Example

Policy Component
Abbreviation

Levels:

UNCLASSIFIED

UN

CONFIDENTIAL

CON

SECRET

SE

Compartments:

FINANCIAL

FIN

Groups:

EASTERN

EAS

WESTERN

WES

SOUTHERN

SOU

Two user labels have been assigned, CON:FIN and SE:FIN:EAS,WES

Two data labels have been assigned, CON:FIN:EAS and SE:FIN:EAS

User access to the data differs, depending on the type of group being used:

If the policy uses standard groups, then:

The user with the label CON:FIN cannot read CON:FIN:EAS data.

The user with the label SE:FIN:EAS,WES can read SE:FIN:EAS data.

If the policy has the INVERSE GROUPS policy enforcement option, then:

The user with the label CON: FIN can read CON:FIN:EAS data.

The user with the label SE:FIN:EAS,WES cannot read SE:FIN:EAS data.

Computed Labels with Inverse Groups

This section explains how inverse groups affect computed label values. It contains these topics:

Computed Session Labels with Inverse Groups

Inverse Groups and Computed Max Read Groups and Max Write Groups

Computed Session Labels with Inverse Groups

After the administrator assigns label authorizations to a user, Oracle Label Security automatically computes a number of labels. With inverse groups, these labels are as follows:

Table 13-3 Computed Session Labels with Inverse Groups

Computed Label
Definition

Max Read Label

The user's maximum level combined with his or her authorized compartments and the minimum set of inverse groups that should be in the user label (session label)

Max Write Label

The user's maximum level combined with the compartments for which the user has been granted write access. Contains the maximum authorized inverse groups that can be set in any label. The user has write authorizations on all these inverse groups.

Min Write Label

The user's minimum level.

Default Read Label

The default level, combined with compartments and inverse groups that have been designated as default for the user.

Default Write Label

A subset of the default read label, containing the compartments and inverse groups for which the user has been granted write access. However the inverse groups component has no significance as it is the Max Write Groups that is always used for write access.

Default Row Label

The combination of components between the user's minimum write label and the maximum write label, which has been designated as the default for the data label for inserted data. The Inverse groups should be a superset of inverse groups in the default label and a subset of Max Write Groups.

See Also:

"Computed Session Labels"

Inverse Groups and Computed Max Read Groups and Max Write Groups

From the computed values in Table 13-3, two sets of groups are identified for label evaluation of read and write access:

Table 13-4 Sets of Groups for Evaluating Read and Write Access

Sets of Groups
Meaning

Max Read Groups

Max Read Groups are the groups contained in the Max Read Label, identifying the minimum set of inverse groups that can be set in any user label.

Max Write Groups

Max Write Groups are the groups contained in the Max Write Label, identifying the maximum authorized inverse groups that can be set in any user label. This set of groups is checked at the time of write access, and also when setting session labels.

Note that Max Write Groups is a superset of Max Read Groups.

As shown in Table 13-5, for standard groups you can have READ ONLY and READ/WRITE authorizations; for inverse groups you can have WRITE ONLY and READ/WRITE authorizations.

Table 13-5 Read and Write Authorizations for Standard Groups and Inverse Groups

Type of Group
READ ONLY
READ/WRITE
WRITE ONLY

Standard Groups

The group is present only in Max Read Label, not in Max Write Label.

The group is present in both Max Read Label and Max Write Label.

Not supported

Inverse Groups

Not supported

The group is present in both Max Read Label and Max Write Label.

The group is present only in Max Write Label, not in Max Read Label.

Although Max Read Groups identifies the set of groups contained in the Max Read Label, this value represents the minimum set of inverse groups that can be set. For example:

Max Read Groups: S:C1:G1,G2

Max Write Groups: S:C1:G1,G2,G3,G4,G5

Here, the user can read data that contains at least the two groups listed in Max Read Groups.

Note that in standard groups, there can never be a situation in which there are more groups in the Max Write Label than in the Max Read Label.

Inverse Groups and Hierarchical Structure

Standard groups in Oracle Label Security are hierarchical, so that a group can be associated with a parent group. For example, the EASTERN region can be the parent of two subordinate groups: EAS_SALES, and EAS_HR.

In a policy with standard groups, if the user label has the parent group, then it can access all data of the subordinate groups.

With inverse groups, parent-child relationships are not supported.

Inverse Groups and User Privileges

With inverse groups implemented, the meaning of user privileges remains the same.

When the user has no special privileges, then the read algorithm and the write algorithm are different for standard groups and inverse groups. The differences are described later, in "Algorithm for Read Access with Inverse Groups" and "Algorithm for Write Access with Inverse Groups".

The effect of inverse groups on the COMPACCESS privilege is described later, in "Algorithms for COMPACCESS Privilege with Inverse Groups".

Inverse groups have no impact upon the following user privileges:

PROFILE_ACCESS

WRITEUP

WRITEDOWN

WRITEACROSS

Algorithm for Read Access with Inverse Groups

This section describes the algorithm for read access with inverse groups.

To read data in a table with the INVERSE GROUP option in effect, the label evaluation process proceeds from levels to groups to compartments, as illustrated in Figure 13-1, "Read Access Label Evaluation with Inverse Groups". (Note that the current session label is the label being evaluated.)

The user's level must be greater than or equal to the level of data.

The user's label must include all the compartments assigned to the data

The groups in the data label must be a superset of the groups in the user label.

If the user's label passes these tests, then the user can access the data. If not, the user is denied access. Note that if the data label is null or invalid, then the user is denied access.

Note:

This flow diagram is true only when the user has no special privileges.

Figure 13-1 Read Access Label Evaluation with Inverse Groups

See Also:

"The Oracle Label Security Algorithm for Read Access"

Algorithm for Write Access with Inverse Groups

This section describes the algorithm for write access with inverse groups.

To write data in a table with the INVERSE GROUP option, the label evaluation process proceeds from levels to groups to compartments, as illustrated in Figure 13-2, "Write Access Label Evaluation with Inverse Groups". (Note that the current session label is the label being evaluated.)

The level in the data label must be greater than or equal to the user's minimum level, and less than or equal to the user's session level.

One of the following conditions must be met:

The groups in the data label must be a superset of the groups in the user label.

or

The user has READ access privilege on the policy.

The user's Max Write Groups must be a superset of the data label groups.

The user label must have write access on all of the compartments in the data label.

Note that if the data label is null or invalid, then the user is denied access.

Note:

This flow diagram is true only when the user has no special privileges.

Figure 13-2 Write Access Label Evaluation with Inverse Groups

See Also:

"The Oracle Label Security Algorithm for Write Access"

Algorithms for COMPACCESS Privilege with Inverse Groups

This section describes the algorithms for read and write access with inverse groups, for users who have COMPACCESS privilege.

The COMPACCESS privilege allows a user to access data based on the row's compartments, independent of the row's groups.

When compartments exist and access to them is authorized, then the group authorization is bypassed.

If a row has no compartments, then access is determined by the inverse group authorizations.

Figure 13-3, "Read Access Label Evaluation: COMPACCESS Privilege and Inverse Groups" and Figure 13-4, "Write Access Label Evaluation: COMPACCESS Privilege and Inverse Groups" show the label evaluation process for read access and write access for a user with the COMPACCESS privilege. If the data label is null or invalid, then the user is denied access.

(Note that the current session label is the label being evaluated.)

Figure 13-3 Read Access Label Evaluation: COMPACCESS Privilege and Inverse Groups

Figure 13-4 Write Access Label Evaluation: COMPACCESS Privilege and Inverse Groups

Session Labels and Inverse Groups

This section describes how inverse groups affect session labels and row labels.

Setting Initial Session/Row Labels for Standard or Inverse Groups

Setting Current Session/Row Labels for Standard or Inverse Groups

Examples of Session Labels and Inverse Groups

Setting Initial Session/Row Labels for Standard or Inverse Groups

The use of inverse groups affects the behavior of Oracle Label Security procedures that determine the session label. The SA_USER_ADMIN.SET_DEFAULT_LABEL and SA_USER_ADMIN.SET_ROW_LABEL procedures set the user's initial session label and row label, respectively, to the one specified.

Standard Groups: Rules for Changing Initial Session/Row Labels

A user's default session label can be changed using SA_USER_ADMIN.SET_DEFAULT_LABEL. In the case of standard groups, the default session label can be set to include any groups in the authorized list, as long as the current default row label will still be dominated by the new write label. That is, the row label will have the same or fewer standard groups than the new write label.

The same rule applies for SA_USER_ADMIN.SET_ROW_LABEL.

Inverse Groups: Rules for Changing Initial Session/Row Labels

In the case of inverse groups, the default session label can be set to include any groups in the authorized list, as long as the current default row label will still be dominated by the new write label. That is, the row label will have the same or more inverse groups than the new write label.

The same rule applies for SA_USER_ADMIN.SET_ROW_LABEL.

See Also:

"SA_USER_ADMIN.SET_DEFAULT_LABEL Procedure"

"SA_USER_ADMIN.SET_ROW_LABEL Procedure"

"Dominance Rules for Labels with Inverse Groups"

Setting Current Session/Row Labels for Standard or Inverse Groups

The use of inverse groups affects the behavior of the SA_SESSION.SET_LABEL and SA_SESSION.SET_ROW_LABEL procedures, which can be used to set the user's current session label and row label, respectively.

Standard Groups: Rules for Changing Current Session/Row Labels

With standard groups, the SA_SESSION.SET_LABEL procedure can be used to set the session label to include any groups in the user's authorized group list. (Subgroups of authorized groups are implicitly included in the authorized list.) Note that if you change the session label, then this may affect the value of the session's row label.

Use the SET_ROW_LABEL procedure to set the row label value for the current database session. The compartments and groups in the label must be a subset of compartments and groups in the session label to which the user has write access.

Inverse Groups: Rules for Changing Current Session/Row Labels

With inverse groups, the addition of groups to the session label decreases a user's ability to access sensitive data with fewer groups. The removal of groups enables the user to access more sensitive information. So, the user should be allowed to add groups to the session label, as long as Max Read Groups is a subset of the groups in the session label, and Max Write Groups is a superset of groups in the session label. The same restriction applies when a user removes groups from the session label.

Note that there are no subgroups of authorized groups when using inverse groups. This is because parent groups are not allowed in policies using inverse groups.

Use the SET_ROW_LABEL procedure to set the row label value for the current database session. The compartments in the label must be a subset of compartments in the session label to which the user has write access.

The user is allowed to add inverse groups to the row label, as long as the session label inverse groups are a subset of the row label inverse groups, and Max Write Groups is a superset of inverse groups in the row label.

For example:

If the user has the inverse groups UK and US as his Max Read Groups, and UK,US,CAN as his Max Write Groups. The user can set his session label to C:ALPHA:UK,US,CAN but not to C:ALPHA:UK.

If the user has the inverse group UK as his Max Read Groups, and UK,CAN as his Max Write Groups.assigned to him. The user can set the session label to C:ALPHA:UK,CAN but cannot change it to either C:ALPHA or C:ALPHA:UK,US,CAN.

See Also:

"SA_SESSION.SET_LABEL Procedure"

"SA_SESSION.SET_ROW_LABEL Procedure"

Examples of Session Labels and Inverse Groups

This section presents examples to illustrate the use of inverse groups.

Inverse Groups Example 1

Consider a User1, of a policy implementing inverse groups, with the following labels:

Table 13-6 Labels for Inverse Groups Example 1

Name
Definition

Max Read Label

SE:ALPHA,BETA:G1,G2

Max Write Label

SE:ALPHA:G1,G2,G3

Default Read Label

SE:ALPHA,BETA:G1,G2

Default Write Label

SE:ALPHA:G1,G2

Default Row Label

SE:ALPHA:G1,G2

From which the following values are derived:

Max Read Groups

G1,G2

Max Write Groups

G1,G2,G3

The following conclusions can be drawn:

User1 can update data with label SE:ALPHA:G1,G2 as well as data with label SE:ALPHA:G1,G2,G3. User1 cannot, however, update label SE:ALPHA:G1.

If standard groups were being used, rather than inverse groups, then User1 could update data with label SE:ALPHA:G1.

Data that User1 inserts has the label SE:ALPHA:G1,G2. (This is the same as with standard groups.)

If User1 leaves the default label as is, and sets the row label to SE:ALPHA:G1,G2,G3, then user1 will insert SE:ALPHA:G1,G2,G3 in new rows of data that is written. (In standard groups, User1 can never set more groups in the row label than in the default label.)

Inverse Groups Example 2

Consider a User01, of a policy implementing inverse groups, with the following labels:

Table 13-7 Labels for Inverse Groups Example 2

Name
Definition

Max Read Label

C:ALPHA:

Max Write Label

C:ALPHA:G1,G2,G3

Default Read Label

C:ALPHA:

Default Write Label

C:ALPHA:

Default Row Label

C:ALPHA:

From which the following values are derived:

Max Read Groups

(an empty set)

Max Write Groups

G1,G2,G3

The following conclusions can be drawn:

User01 can update any data with level C, compartment ALPHA, and any combination of groups G1, G2, G3, or no groups. User01 inserts the label C:ALPHA: in new data that User01 writes.

User02, who has Max Read Groups of G1,G2 or G1,G3, and so on, will not be able to view the data written by User01. This is because User01's Default Row Label contains no groups.

User01 can choose to set inverse groups in the row label, as long as the inverse groups in the session label dominates the row label (that is, User01's session label contains the same or fewer groups than contained in the row label).

This is true because the row label must have at least the groups in the session label, and can at most have the Maximum Write Groups. If the session label is G1, then you can set the groups in the row label from G1 to the Max Write Groups (G1,G2,G3).

If User01 sets his session label and row label to C:ALPHA:G1:G2:G3, then his data becomes accessible to anyone who has any combination of G1,G2,G3 in his Max Read Groups.

See Also:

"Computed Session Labels"

Changes in Behavior of Procedures with Inverse Groups

When the INVERSE_GROUP option is specified at the time the policy is created, a change occurs in the algorithms that determine the read and write access of the user to labeled data. This section describes how inverse groups affect the behavior of the following procedures:

SA_SYSDBA.CREATE_POLICY with Inverse Groups

SA_SYSDBA.ALTER_POLICY with Inverse Groups

SA_USER_ADMIN.ADD_GROUPS with Inverse Groups

SA_USER_ADMIN.ALTER_GROUPS with Inverse Groups

SA_USER_ADMIN.SET_GROUPS with Inverse Groups

SA_USER_ADMIN.SET_USER_LABELS with Inverse Groups

SA_USER_ADMIN.SET_DEFAULT_LABEL with Inverse Groups

SA_USER_ADMIN.SET_ROW_LABEL with Inverse Groups

SA_COMPONENTS.CREATE_GROUP with Inverse Groups

SA_COMPONENTS.ALTER_GROUP_PARENT with Inverse Groups

SA_SESSION.SET_LABEL with Inverse Groups

SA_SESSION.SET_ROW_LABEL with Inverse Groups

LEAST_UBOUND with Inverse Groups

GREATEST_LBOUND with Inverse Groups

SA_SYSDBA.CREATE_POLICY with Inverse Groups

The CREATE_POLICY procedure under the SA_SYSDBA package creates the policy, defines an optional policy-specific column name, and specifies a set of default policy options. With inverse group support the, user has one more policy enforcement option, INVERSE_GROUP. For example:

PROCEDURE CREATE_POLICY (
 HR IN VARCHAR2,
 SA_LABEL IN VARCHAR2 DEFAULT NULL,
 INVERSE_GROUP IN VARCHAR2 DEFAULT NULL);

See Also:

"SA_SYSDBA.CREATE_POLICY Procedure"

"About Policy Enforcement Options"

SA_SYSDBA.ALTER_POLICY with Inverse Groups

The ALTER_POLICY procedure under the SA_SYSDBA package enables you to change a policy's default enforcement options, except for the INVERSE_GROUP option. Once a policy is configured for inverse groups, it cannot be changed. You can also change the column names associated with an OLS policy.

See Also:

"SA_SYSDBA.ALTER_POLICY Procedure"

SA_USER_ADMIN.ADD_GROUPS with Inverse Groups

The ADD_GROUPS procedure adds groups to a user, indicating whether the groups are authorized for write as well as read.

See Also:

Syntax for "SA_USER_ADMIN.ADD_GROUPS Procedure"

The type of access authorized depends on the access_mode parameter.

Table 13-8 Access Authorized by Values of access_mode Parameter

Access_Mode Parameter
Meaning

READ_WRITE

Indicates that write is authorized. (That is, the group is contained in both Max Read Groups and Max Write Groups.)

WRITE_ONLY

Indicates that the group is contained in Max Write Groups and not in Max Read Groups

access_mode

If access_mode is set to READ_WRITE, then the group is added to both Max Read Groups and Max Write Groups.

If access_mode is set to SA_UTL.WRITE_ONLY, then the group is added only to the Max Write Groups.

If access_mode is NULL, then it is set to SA_UTL.READ_WRITE.

in_def

Specifies whether these groups should be in the default groups (Y/N).

If in_def is NULL, then it will be set to Y or N as follows:

If access mode is READ_WRITE, in_def is set to Y.

If access mode is WRITE_ONLY, in_def is set to N.

in_row

Specifies whether these groups should be in the row label (Y/N), using the identical criteria as for in_def.

However, if in_def is Y, then in_row must also be Y.

Note that if in_def is Y in a row, then in_row must also be set to Y, but not the other way round.

The same is the case with the in_row field.

See Also:

"Inverse Groups and Computed Max Read Groups and Max Write Groups"

SA_USER_ADMIN.ALTER_GROUPS with Inverse Groups

The ALTER_GROUPS procedure changes the write access, the default label indicator, and the row label indicator for each of the groups in the list.

The behavior of inverse groups is the same as described in the case of ADD_GROUPS.

See Also:

Syntax for "SA_USER_ADMIN.ALTER_GROUPS Procedure"

SA_USER_ADMIN.SET_GROUPS with Inverse Groups

The SET_GROUPS procedure assigns groups to a user and identifies default values for the user's session label and row label.

See Also:

Syntax for "SA_USER_ADMIN.SET_GROUPS Procedure"

Inverse groups are handled differently than standard groups, as follows:

Table 13-9 Assigning Groups to a User

Group Set Name
Meaning

read_groups

A comma-delimited list of groups that would be Max Read Groups

write_groups

A comma-delimited list of groups that would be Max Write Groups. It must be a superset of read_groups.

If write_groups is NULL, then they are set to read_groups.

def_groups

Specifies the default groups. It should at least have read_groups, and write_groups should be a superset of def_groups.

If def_groups is NULL, then they are set to the read_groups.

row_groups

Specifies the row groups. It should at least have the def_groups and should be a subset of max write groups.

If row_groups is NULL, then they are set to the def_groups, because for inverse groups, all def_groups are also in write_groups.

SA_USER_ADMIN.SET_USER_LABELS with Inverse Groups

The SET_USER_LABELS procedure sets the user's levels, compartments, and groups using a set of labels, instead of the individual components.

See Also:

Syntax for "SA_USER_ADMIN.SET_USER_LABELS Procedure"

Inverse groups are handled differently than standard groups, as follows:

Table 13-10 Inverse Group Label Definitions

Name
Definition

max_read_label

Specifies the label string to be used to initialize the user's maximum authorized read label. Composed of the user's maximum level, compartments authorized for read access, and if inverse groups, minimum set of groups that can be set in any label.(Max Read Groups)

max_write_label

Specifies the label string to be used to initialize the user's maximum authorized write label. Composed of the user's maximum level, compartments authorized for write access, and if inverse groups, the maximum authorized groups that can be set in any label (Max Write Groups). All the inverse groups in this have write authorization also. It should be a superset of groups in max_read_label. If max_write_label is not specified, then it is set to max_read_label.

def_label

Specifies the label string to be used to initialize the user's session label, including level, compartments, and groups (a subset of max_read_label). If default_label is not specified, then it is set to max_read_label. For inverse groups, component it should at least have the groups in max_read_label, and groups in max_write_label should be a superset of the groups in the def_label.

row_label

Specifies the label string to be used to initialize the program's row label. Includes levels, compartments, and groups: subsets of max_write_label and def_label. If row_label is not specified, then it is set to def_label, with only the compartments and groups authorized for write access. The inverse groups component is set to the same as that in def_label if the row_label is not specified. The inverse groups in row label should at least be those in default label and should be a subset of Max Write Groups.

SA_USER_ADMIN.SET_DEFAULT_LABEL with Inverse Groups

The SET_DEFAULT_LABEL procedure sets the user's initial session label to the one specified.

All the rules mentioned for setting inverse groups component of session label mentioned in "Session Labels and Inverse Groups" are applicable here.

See Also:

Syntax for "SA_USER_ADMIN.SET_DEFAULT_LABEL Procedure"

SA_USER_ADMIN.SET_ROW_LABEL with Inverse Groups

Use the SET_ROW_LABEL procedure to set the user's initial row label to the one specified.

See Also:

Syntax for "SA_USER_ADMIN.SET_ROW_LABEL Procedure"

When specifying the row_label, the inverse groups component must contain at least all the inverse groups in def_label and should be a subset of Max Write Groups.

See Also:

"Setting Initial Session/Row Labels for Standard or Inverse Groups"

SA_COMPONENTS.CREATE_GROUP with Inverse Groups

Use the CREATE_GROUP procedure to create a group and specify its short name and long name, and optionally a parent group.

See Also:

Syntax for "SA_COMPONENTS.CREATE_GROUP Procedure"

With inverse groups, the parent_name field should always be NULL. If the user specifies a value for this field, then an error message is displayed, indicating that the group hierarchy is disabled.

SA_COMPONENTS.ALTER_GROUP_PARENT with Inverse Groups

This function is disabled for policies with the inverse group option. An error message is displayed if the user calls this function.

See Also:

Syntax for "SA_COMPONENTS.ALTER_GROUP Procedure"

SA_SESSION.SET_LABEL with Inverse Groups

Use the SET_LABEL procedure to set the label of the current database session.

See Also:

Syntax for "SA_SESSION.SET_LABEL Procedure".

For the current user, this procedure follows the same rules for setting the session label as does the sa_user_admin.set_user_label function.

See Also:

"Setting Current Session/Row Labels for Standard or Inverse Groups"

SA_SESSION.SET_ROW_LABEL with Inverse Groups

Use the SET_ROW_LABEL procedure to set the default row label value for the current database session.

See Also:

Syntax for "SA_SESSION.SET_ROW_LABEL Procedure"

For the current user, this procedure follows the same rules for setting the row label as does the sa_user_admin.set_row_label function.

See Also:

"Setting Initial Session/Row Labels for Standard or Inverse Groups"

LEAST_UBOUND with Inverse Groups

The LEAST_UBOUND (LUBD) function returns a character string label that is the least upper bound of label1 and label2 that is, the one label that dominates both.

With standard groups, the least upper bound is the highest level, the union of the compartments in the labels, and the union of the groups in the labels.

With inverse groups, the least upper bound is the highest level, the union of the compartments in the labels, and the intersection of the inverse groups in the labels.

For example, with inverse groups, the least upper bound of HIGHLY_SENSITIVE:ALPHA:G1,G2 and SENSITIVE:BETA:G1 is HIGHLY_SENSITIVE:ALPHA,BETA:G1.

GREATEST_LBOUND with Inverse Groups

The GREATEST_LBOUND (GLBD) function can be used to determine the lowest label of the data that can be involved in an operation, given two different labels. It returns a character string label that is the greatest lower bound of label1 and label2.

With standard groups, the greatest lower bound is the lowest level, and the intersection of the compartments in the labels and the groups in the labels.

With inverse groups, the greatest lower bound is the lowest level, and the intersection of the compartments in the labels and the union of inverse groups in the labels.

For example, with inverse groups the greatest lower bound of HIGHLY_SENSITIVE:ALPHA:G1,G3 and SENSITIVE::G1 is SENSITIVE:G1,G3

See:

"Determining Upper and Lower Bounds of Labels"

Dominance Rules for Labels with Inverse Groups

Dominance rules for Oracle Label Security with standard groups can be summarized as follows:

A user label dominates a data label if:

User level is greater than or equal to the data level

User compartments are a superset of the data compartments

User groups intersects (have at least one group from) the data groups

Dominance rules for Oracle Label Security with inverse groups can be summarized as follows:

A user label dominates a data label if:

User level is greater than or equal to the data level

User compartments are a superset of the data compartments

Data groups are a superset of user groups

See Also:

"About Dominant and Dominated Labels"

Part IV

Appendixes

This part contains the following chapter:

Appendix A, "Disabling and Enabling Oracle Label Security"

Appendix B, "Advanced Topics in Oracle Label Security"

Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory"

Appendix D, "Oracle Label Security in an Oracle RAC Environment"

Appendix E, "Oracle Label Security PL/SQL Packages"

Appendix F, "Oracle Label Security Reference"

Appendix G, "Frequently Asked Questions about Oracle Label Security"

A Disabling and Enabling Oracle Label Security

This appendix contains:

When You Must Disable Oracle Label Security

Checking if Oracle Label Security Is Enabled or Disabled

Disabling Oracle Label Security

Enabling Oracle Label Security

Note:

Oracle does not support the deinstallation of Oracle Label Security.

When You Must Disable Oracle Label Security

You may need to disable Oracle Label Security to perform upgrade tasks or correct erroneous configurations. Another reason for disabling Oracle Label Security is if you want to test an application without enforcing Oracle Label Security. You can reenable Oracle Label Security after you complete the tasks.

Checking if Oracle Label Security Is Enabled or Disabled

To find if Oracle Label Security has been enabled or disabled, query the V$OPTION data dictionary view. Any user can query this view. If Oracle Label Security is enabled, then the query returns TRUE. Otherwise, it returns FALSE. Remember that the PARAMETER column value is case sensitive. For example:

SELECT VALUE FROM V$OPTION WHERE PARAMETER = 'Oracle Label Security';

Disabling Oracle Label Security

If Oracle Database Vault has been enabled, then do not disable Oracle Label Security. See Oracle Database Vault Administrator's Guide to find if Database Vault has been enabled.

Log into the database instance as user SYS or a user who has been granted the LBAC_DBA role.

For example:

sqlplus psmith_ols -- Or, psmith_ols@hrpdb for the hrpdb pluggable database (PDB)
Enterp password: password

Run the following procedure:

EXEC LBACSYS.OLS_ENFORCEMENT.DISABLE_OLS;

Restart the database.

For example:

CONNECT SYS AS SYSOPER
Enter password: password

SHUTDOWN IMMEDIATE
STARTUP

For Oracle Real Application Cluster (Oracle RAC) environment or a multitenant environment, repeat these steps for each Oracle RAC node or PDB on which you enabled Oracle Label Security.

Enabling Oracle Label Security

Log into the database instance as user SYS or a user who has been granted the LBAC_DBA role.

For example:

sqlplus psmith_ols -- Or, psmith_ols@hrpdb for the hrpdb PDB
Enterp password: password

Run the following procedure:

EXEC LBACSYS.OLS_ENFORCEMENT.ENABLE_OLS;

Restart the database.

For example:

CONNECT SYS AS SYSOPER
Enter password: password

SHUTDOWN IMMEDIATE
STARTUP

For Oracle Real Application Cluster (Oracle RAC) environment or a multitenant environment, repeat these steps for each Oracle RAC node or PDB on which you disabled Oracle Label Security.

B Advanced Topics in Oracle Label Security

This appendix covers topics of interest to advanced users of Oracle Label Security. It contains these sections:

Analyzing the Relationships Between Labels

Querying for Audited Oracle Label Security Session Labels

Oracle Call Interface for Setting Session Labels

Analyzing the Relationships Between Labels

This section describes relationships between labels. It contains these topics:

About Dominant and Dominated Labels

Non-Comparable Labels

Using Dominance Functions

About Dominant and Dominated Labels

The relationship between two labels can be described in terms of dominance. A user's ability to access an object depends on whether the user's label dominates the label of the object. If a user's label does not dominate the object's label, then the user is not allowed to access the object.

Label dominance is analyzed in terms of all its components: levels, compartments, and groups.

Table B-1 Dominance in the Comparison of Labels

Factor
Criteria for Dominance

Level

For label1 to dominate label2, the level of label1 must be greater than or equal to that of label2.

Compartment

For label1 to dominate label2, the compartments of label1 must contain all the compartments of label2.

Group

For label1 to dominate label2, label1 must contain at least one of the groups of label2.

One label dominates another label if all of its components dominate the components of the other label. For example, the label HIGHLY_SENSITIVE:FINANCE,OPERATIONS dominates the label HIGHLY_SENSITIVE:FINANCE. Similarly, the label HIGHLY_SENSITIVE::WR_AP dominates the label HIGHLY_SENSITIVE::WR_AP, WR_AR.

See Also:

"Dominance Rules for Labels with Inverse Groups"

Non-Comparable Labels

The relationship between two labels cannot always be defined by dominance. Two labels are non-comparable if neither label dominates the other. If any compartments differ between the two labels (as with HS:A and HS:B), then they are non-comparable. Similarly, the labels HS:A and S:B are non-comparable.

Using Dominance Functions

This section contains:

About the Dominance Functions

OLS_DOMINATES Standalone Function

OLS_LABEL_DOMINATES Standalone Function

OLS_STRICTLY_DOMINATES Standalone Function

OLS_DOMINATED_BY Standalone Function

OLS_STRICTLY_DOMINATED_BY Standalone Function

SA_UTL.DOMINATES

SA_UTL.STRICTLY_DOMINATES

SA_UTL.DOMINATED_BY

SA_UTL.STRICTLY_DOMINATED_BY

See Also:

"Ordering Labeled Data Rows"

About the Dominance Functions

You can use dominance functions to specify ranges in queries. The following functions enable you to indicate dominance relationships between specified labels.

Table B-2 Functions to Determine Dominance

Function
Description

OLS_DOMINATES

The value of label1 dominates, or is equal to, that of label2.

OLS_LABEL_DOMINATES

The value of the session label for the corresponding policy_name dominates, or is equal to, that of label.

OLS_STRICTLY_DOMINATES

The value of label1 dominates that of label2, and is not equal to it.

OLS_DOMINATED_BY

The value of label1 is dominated by that of label2.

OLS_STRICTLY_DOMINATED_BY

The value of label1 is dominated by that of label2, and is not equal to it.

Note that there are two types of dominance function. While the SA_UTL dominance functions return BOOLEAN values, the standalone dominance functions return integers.

OLS_DOMINATES Standalone Function

The OLS_DOMINATES (OLS_DOM) function returns 1 (TRUE) if label1 dominates label2, or 0 (FALSE) if it does not.

Syntax

OLS_DOMINATES (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN INTEGER;

Parameters

Table B-3 OLS_DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SELECT OLS_DOMINATES ('1111', '1112') FROM DUAL;

OLS_DOMINATES('1111','1112')
----------------------------
                           0

Note:

The old OLS functions, DOMINATES and DOM, have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_LABEL_DOMINATES and OLS_DOM functions instead. Using the new function names avoids potential name conflicts with other database components.

OLS_LABEL_DOMINATES Standalone Function

Note:

This feature is available starting with Oracle Database 12c Release 1 (12.1.0.2).

The standalone OLS_LABEL_DOMINATES function returns 1 (TRUE) if the session label of the specified policy_name value dominates or is equal to the label that is specified by the label parameter; otherwise, it returns 0 (FALSE). This function is publicly available.

In addition to Oracle Label Security policies, you can use this function with both Oracle Data Redaction and Oracle Database Vault policies.

Syntax

OLS_LABEL_DOMINATES (
  policy_name    IN VARCHAR2,
  label          IN VARCHAR2)
RETURN INTEGER;

Parameters

Table B-4 OLS_LABEL_DOMINATES Parameters

Parameter
Description

policy_name

The name of the Oracle Label Security policy whose session label must be checked for dominance. To find existing label values for policies, query the POLICY_NAME and LABEL columns of the ALL_SA_LABELS view.

label

The base label against whom the dominance has to be checked

Examples

The following example checks if the session label for the hr_ols_pol policy dominates or is equal to the hs label.

SELECT OLS_LABEL_DOMINATES ('hr_ols_pol', 'hs') FROM DUAL;

OLS_LABEL_DOMINATES('HR_OLS_POL','HS')
--------------------------------------
                                     0

This example shows how you can use the OLS_LABEL_DOMINATES function in an Oracle Data Redaction policy:

BEGIN
 DBMS_REDACT.ADD_POLICY(
   object_schema   => 'oe',
   object_name     => 'customers',
   column_name     => 'customer_id',
   policy_name     => 'redact_cust_user_ids',
   function_type   => DBMS_REDACT.FULL,
   expression      => 'OLS_LABEL_DOMINATES(''hr_ols_pol'', ''hs'') = 0');
END;
/

The following example shows how you can use the OLS_LABEL_DOMINATES function in an Oracle Database Vault rule definition:

EXEC DBMS_MACADM.CREATE_RULE('Check OLS Factor', 'OLS_LABEL_DOMINATES(''hr_ols_pol'', ''hs'') = 1');

See Also:

Oracle Database Advanced Security Guide for more information about Data Redaction

Oracle Database Vault Administrator's Guide for more information about Database Vault realms

OLS_STRICTLY_DOMINATES Standalone Function

The OLS_STRICTLY_DOMINATES (OLS_S_DOM) function returns 1 (TRUE) if label1 dominates label2 and is not equal to it.

Syntax

OLS_STRICTLY_DOMINATES (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN INTEGER;

Parameters

Table B-5 OLS_STRICTLY_DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Examples

The following example compares existing label tags 1111 and 1112.

SELECT OLS_STRICTLY_DOMINATES ('1111', '1112') FROM DUAL;

OLS_STRICTLY_DOMINATES('1111','1112')
-------------------------------------
                                    0

Note:

The old OLS functions, STRICTLY_DOMINATES and S_DOM have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_STRICTLY_DOMINATES and OLS_S_DOM functions instead. Using the new function names avoids potential name conflicts with other database components.

OLS_DOMINATED_BY Standalone Function

The OLS_DOMINATED_BY (OLS_DOM_BY) function returns 1 (TRUE) if label1 is dominated by label2.

Syntax

OLS_DOMINATED_BY (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN INTEGER;

Parameters

Table B-6 OLS_STRICTLY_DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SELECT OLS_DOMINATED_BY ('1111', '1112') FROM DUAL;

OLS_DOMINATED_BY('1111','1112')
-------------------------------
                              1

Note:

The old OLS functions, DOMINATED_BY and DOM_BY have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_DOMINATED_BY and OLS_DOM_BY functions instead. Using the new function names avoids potential name conflicts with other database components.

OLS_STRICTLY_DOMINATED_BY Standalone Function

The OLS_STRICTLY_DOMINATED_BY (OLS_S_DOM_BY) function returns 1 (TRUE) if label1 is dominated by label2 and is not equal to it.

Syntax

OLS_STRICTLY_DOMINATED_BY (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN INTEGER;

Parameters

Table B-7 OLS_DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SELECT OLS_STRICTLY_DOMINATES ('1111', '1112') FROM DUAL;

OLS_STRICTLY_DOMINATES('1111','1112')
-------------------------------------
                                    0

Note:

The old OLS functions, STRICTLY_DOMINATED_BY and S_DOM_BY have been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use the old functions in this release, but Oracle recommends that you use the OLS_STRICTLY_DOMINATED_BY and OLS_S_DOM_BY functions instead. Using the new function names avoids potential name conflicts with other database components.

SA_UTL.DOMINATES

The SA_UTL.DOMINATES function returns TRUE if label1 dominates label2 or if the session label for the given OLS policy dominates label.

Syntax

SA_UTL.DOMINATES (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN BOOLEAN;

Syntax

SA_UTL.DOMINATES (
  ols_policy_name  IN VARCHAR2,
  label            IN VARCHAR2)
RETURN BOOLEAN;

Parameters

Table B-8 SA_UTL.DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SET SERVEROUTPUT ON
BEGIN
 IF SA_UTL.DOMINATES(1111, 1112)
  THEN DBMS_OUTPUT.PUT_LINE('Label 1111 dominates label 1112.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('Label 1112 dominates label 1111.');
 END IF;
END;
/

Label 1112 dominates label 1111.

Note:

The second SA_UTL.DOMINATES function, which takes the Oracle Label Security policy name and label as inputs, has been deprecated in Oracle Database 12c Release 1 (12.1).

You can still use this function, but not with Oracle Data Redaction and Oracle Database Vault conditions. Oracle recommends that you use the OLS_LABEL_DOMINATES function instead. See "OLS_LABEL_DOMINATES Standalone Function" for more information.

The first SA_UTL.DOMINATES function, which uses the NUMBER datatype, is not deprecated.

SA_UTL.STRICTLY_DOMINATES

The SA_UTL.STRICTLY_DOMINATES function returns TRUE if label1 dominates label2 and is not equal to it.

Syntax

SA_UTL.STRICTLY_DOMINATES (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN BOOLEAN;

Parameters

Table B-9 SA_UTL.STRICTLY_DOMINATES Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SET SERVEROUTPUT ON
BEGIN
 IF SA_UTL.STRICTLY_DOMINATES(1111, 1112)
  THEN DBMS_OUTPUT.PUT_LINE('Label 1111 strictly dominates label 1112.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('Label 1112 strictly dominates label 1111.');
 END IF;
END;
/

Label 1112 strictly dominates label 1111.

SA_UTL.DOMINATED_BY

The SA_UTL.DOMINATED_BY function returns TRUE if label1 is dominated by label2.

Syntax

SA_UTL.DOMINATED_BY (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN BOOLEAN;

Parameters

Table B-10 SA_UTL.DOMINATED_BY Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SET SERVEROUTPUT ON
BEGIN
 IF SA_UTL.DOMINATED_BY(1111, 1112)
  THEN DBMS_OUTPUT.PUT_LINE('Label 1111 is dominated by label 1112.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('Label 1112 is dominated by label 1111.');
 END IF;
END;
/

Label 1111 is dominated by label 1112.

SA_UTL.STRICTLY_DOMINATED_BY

The SA_UTL.STRICTLY_DOMINATED_BY function returns TRUE if label1 is dominated by label2 and is not equal to it.

Syntax

SA_UTL.STRICTLY_DOMINATED_BY (
  label1          IN NUMBER,
  label2          IN NUMBER)
RETURN BOOLEAN;

Parameters

Table B-11 SA_UTL.STRICTLY_DOMINATED_BY Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing label tags 1111 and 1112.

SET SERVEROUTPUT ON
BEGIN
 IF SA_UTL.STRICTLY_DOMINATED_BY(1111, 1112)
  THEN DBMS_OUTPUT.PUT_LINE('Label 1111 is strictly dominated by label 1112.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('Label 1112 is strictly dominated by label 1111.');
 END IF;
END;
/

Label 1111 is strictly dominated by label 1112.

See Also::

"Determining Upper and Lower Bounds of Labels".

Querying for Audited Oracle Label Security Session Labels

Oracle Database 12c uses a unified audit trail to capture information from various audit sources, including Oracle Label Security. OLS auditing is configured using audit policies. OLS auditing in Oracle Database 12c enables you to audit additional events like enabling and disabling of OLS policies.

The session labels that the audit trail captures are stored in the APPLICATION_CONTEXTS column of the UNIFIED_AUDIT_TRAIL view. You can use the LBACSYS.ORA_GET_AUDITED_LABEL function to retrieve session labels that are stored in the APPLICATION_CONTEXTS column. This function accepts the UNIFIED_AUDIT_TRAIL.APPLICATION_CONTEXTS column value, and the Oracle Label Security policy name as arguments, and then returns the session label that is stored in the column for the specified policy.

See Oracle Database Security Guide for detailed information on configuring and using OLS auditing in Oracle Database 12c. The following section describes the ORA_GET_AUDITED_LABEL function.

LBACSYS.ORA_GET_AUDITED_LABEL Function

The ORA_GET_AUDITED_LABEL function returns the audited session label for the specified OLS policy and APPLICATION_CONTEXTS column value. The AUDIT_VIEWER role has EXECUTE privilege on the ORA_GET_AUDITED_LABEL function.

Syntax

ORA_GET_AUDITED_LABEL (
  appctx_col_value   IN VARCHAR2,
  ols_policy_name    IN VARCHAR2)
RETURN VARCHAR2;

Parameters

Table B-12 ORA_GET_AUDITED_LABEL Parameters

Parameter
Description

appctx_col_value

Value in the UNIFIED_AUDIT_TRAIL.APPLICATION_CONTEXTS column

policy_name

The label security policy name

Example

The following example returns the audited session label for the hr_ols_pol policy.

SELECT ORA_GET_AUDITED_LABEL ('cust_ctx', 'hr_ols_pol') FROM DUAL;

ORA_GET_AUDITED_LABEL('X','HR_OLS_POL')
---------------------------------------
                                     HS

Oracle Call Interface for Setting Session Labels

When you connect using Oracle Call Interface (OCI), you can use the system SYS_CONTEXT variables to initialize the session label and the row label. Set the variables using the OCIAttrSet function to initialize externally initialized SYS_CONTEXT variables. These are available when Oracle Label Security is enabled.

Each policy has a SYS_CONTEXT named SA$policy_name_X. You can set these two variables, INITIAL_LABEL and INITIAL_ROW_LABEL.

When the new values are set to valid labels within the user's authorizations, they will be used instead of the default values stored for the user. This is the same mechanism used for remote connections.

See Also:

Chapter 11, "Using Oracle Label Security with a Distributed Database"

To use the OCI interface to set session labels, do the following:

Call OCIAttrSet with OCI_ATTR_APPCTX_SIZE to initialize the context array size with the desired number of context attributes:

OCIAttrSet(session, OCI_HTYPE_SESSION,
                 (dvoid *)&size, (ub4)0, OCI_ATTR_APPCTX_SIZE, error_handle);

This defines additional attributes for OCIAttrSet.

Note that the size is ub4 type.

Call OCIAttrGet with OCI_ATTR_APPCTX_LIST to get a handle on the application context list descriptor for the session:

OCIAttrGet(session, OCI_HTYPE_SESSION,
               (dvoid *)&ctxl_desc, (ub4)0, OCI_ATTR_APPCTX_LIST, error_handle);

Note that ctxl_desc is (OCIParam *) type.

Call OCIParamGet with the application context list descriptor to obtain an individual descriptor for the i-th application context:

OCIParamGet(ctxl_desc, OCI_DTYPE_PARAM, error_handle,(dvoid **)&ctx_desc, i);

Note that ctx_desc is (OCIParam *) type.

Call OCIAttrSet with each of the three new attributes, OCI_ATTR_APPCTX_NAME, OCI_ATTR_APPCTX_ATTR, and OCI_ATTR_APPCTX_VALUE, to set the proper values in the application context:

OCIAttrSet(ctx_desc, OCI_DTYPE_PARAM,
                 (dvoid *)ctx_name, sizeof(ctx_name), OCI_ATTR_APPCTX_NAME,
                 error_handle);

OCIAttrSet(ctx_desc, OCI_DTYPE_PARAM,
                 (dvoid *)attr_name, sizeof(attr_name), OCI_ATTR_APPCTX_ATTR,
                 error_handle);

OCIAttrSet(ctx_desc, OCI_DTYPE_PARAM,
                 (dvoid *)value, sizeof(value), OCI_ATTR_APPCTX_VALUE,
                 error_handle);

Note that only character type is supported, because application context operations are based on the VARCHAR2 type.

Using OCI with SYS_CONTEXT

Example B-1 shows how to use externalized SYS_CONTEXT with Oracle Label Security.

Example B-1 Using OCI to Externalize SYS_CONTEXT with OLS

#ifdef RCSID
static char *RCSid =
   "$Header: ext_mls.c 09-may-00.10:07:08 jdoe Exp $ ";
#endif /* RCSID */

/* Copyright (c) Oracle Corporation 1999, 2000. All Rights Reserved. */

/*

   NAME
ext_mls.c - externalized SYS_CONTEXT with Label Security

   DESCRIPTION
Run olsdemo.sql script before executing this example.
Usage: <executable obtained with .c file> <user_name> <password> <session-initial-label
Example: avg_sal sa_demo sa_demo L3:M,E:D10

   PUBLIC FUNCTION(S)
<list of external functions declared/defined - with one-line descriptions>

   PRIVATE FUNCTION(S)
<list of static functions defined in .c file - with one-line descriptions>

   RETURNS
The average salary in the EMP table of the SA_DEMO schema querying as the specified user with the specified session label.

   NOTES
<other useful comments, qualifications, and so on>

   MODIFIED   (MM/DD/YY)
jlev      09/18/03 - cleanup
jdoe      05/09/00 - cleanup
   jdoe      10/13/99 - standalone OCI program to test MLS SYS_CONTEXT
   jdoe      10/13/99 - Creation

*/
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <oci.h>

static OCIEnv *envhp;
static OCIError *errhp;

int main(/*_ int argc, char *argv[] _*/);

/* get and print error */
static void checkerr(/*_OCIError *errhp, sword status _*/);
/* print error */
static void printerr(char *call);
static sword status;

/* return the average of employees' salary */
static CONST text *const selectstmt = (text *)
     "select avg(sal) from sa_demo.emp";

int main(argc, argv)
int argc;
char *argv[];
{
  OCISession *authp = (OCISession *) 0;
  OCIServer *srvhp;
  OCISvcCtx *svchp;
  OCIDefine *defnp = (OCIDefine *) 0;
  dvoid *parmdp;
  ub4 ctxsize;
  OCIParam *ctxldesc;
  OCIParam *ctxedesc;
  OCIStmt *stmtp = (OCIStmt *) 0;
  ub4 avg_sal = 0;
  sword status;

  if (OCIInitialize((ub4) OCI_DEFAULT, (dvoid *) 0,
                    (dvoid * (*)(dvoid *, size_t)) 0,
                    (dvoid * (*)(dvoid *, dvoid *, size_t)) 0,
                    (void (*)(dvoid *, dvoid *)) 0))
    printerr("OCIInitialize");

  if (OCIEnvInit((OCIEnv **) &envhp, OCI_DEFAULT, (size_t) 0, (dvoid **) 0))
    printerr("OCIEnvInit");

  if (OCIHandleAlloc((dvoid *) envhp, (dvoid **) &errhp, OCI_HTYPE_ERROR,
                     (size_t) 0, (dvoid **) 0))
    printerr("OCIHandleAlloc:OCI_HTYPE_ERROR");

  if (OCIHandleAlloc((dvoid *) envhp, (dvoid **) &srvhp, OCI_HTYPE_SERVER,
                     (size_t) 0, (dvoid **) 0))
    printerr("OCIHandleAlloc:OCI_HTYPE_SERVER");

  if (OCIHandleAlloc((dvoid *) envhp, (dvoid **) &svchp, OCI_HTYPE_SVCCTX,
                     (size_t) 0, (dvoid **) 0))
    printerr("OCIHandleAlloc:OCI_HTYPE_SVCCTX");

  if (OCIServerAttach(srvhp, errhp, (text *) "", strlen(""), 0))
    printerr("OCIServerAttach");

  /* set attribute server context in the service context */
  if (OCIAttrSet((dvoid *) svchp, OCI_HTYPE_SVCCTX, (dvoid *) srvhp,
                 (ub4) 0, OCI_ATTR_SERVER, (OCIError *) errhp))
    printerr("OCIAttrSet:OCI_HTYPE_SVCCTX");

  if (OCIHandleAlloc((dvoid *) envhp, (dvoid **) &authp,
                     (ub4) OCI_HTYPE_SESSION, (size_t) 0, (dvoid **) 0))
    printerr("OCIHandleAlloc:OCI_HTYPE_SESSION");

  /* set application context to 1 */
  ctxsize = 1;

  /* set up app ctx buffer */
  if (OCIAttrSet((dvoid *) authp, (ub4) OCI_HTYPE_SESSION, (dvoid *) &ctxsize,
                 (ub4) 0, (ub4) OCI_ATTR_APPCTX_SIZE, errhp))
    printerr("OCIAttrSet:OCI_ATTR_APPCTX_SIZE");

  /* retrieve the list descriptor */
  if (OCIAttrGet((dvoid *) authp, (ub4) OCI_HTYPE_SESSION,
                 (dvoid *) &ctxldesc, 0, OCI_ATTR_APPCTX_LIST, errhp))
    printerr("OCIAttrGet:OCI_ATTR_APPCTX_LIST");

  if (status = OCIParamGet(ctxldesc, OCI_DTYPE_PARAM, errhp,
                           (dvoid **) &ctxedesc, 1))
    {
      if (status == OCI_NO_DATA)
        {
          printf("No Data found!\n");
          exit(1);
        }
    }

  /* set context namespace to SA$<pol_name>_X */
  if (OCIAttrSet((dvoid *) ctxedesc, (ub4) OCI_DTYPE_PARAM,
                 (dvoid *) "SA$HUMAN_RESOURCES_X",
                 (ub4) strlen((char *) "SA$HUMAN_RESOURCES_X"),
                 (ub4) OCI_ATTR_APPCTX_NAME, errhp))
    printerr("OCIAttrSet:OCI_ATTR_APPCTX_NAME:SA$HUMAN_RESOURCES_X");

  /* set context attribute to INITIAL_LABEL */
  if (OCIAttrSet((dvoid *) ctxedesc, (ub4) OCI_DTYPE_PARAM,
                 (dvoid *) "INITIAL_LABEL",
                 (ub4) strlen((char *) "INITIAL_LABEL"),
                 (ub4) OCI_ATTR_APPCTX_ATTR, errhp))
    printerr("OCIAttrSet:OCI_DTYPE_PARAM:INITIAL_LABEL");

  /* set context value to argv[3] - initial label */
  if (OCIAttrSet((dvoid *) ctxedesc, (ub4) OCI_DTYPE_PARAM,
                 (dvoid *) argv[3],
                 (ub4) strlen((char *) argv[3]),
                 (ub4) OCI_ATTR_APPCTX_VALUE, errhp))
    printerr("OCIAttrSet:argv[3]");

  /* username first command line argument */
  if (OCIAttrSet((dvoid *) authp, (ub4) OCI_HTYPE_SESSION, (dvoid *) argv[1],
                 (ub4) strlen((char *) argv[1]), (ub4) OCI_ATTR_USERNAME,
                 errhp))
    printerr("OCIAttrSet:username");

  /* password second command line argument */
  if (OCIAttrSet((dvoid *) authp, (ub4) OCI_HTYPE_SESSION, (dvoid *) argv[2],
                 (ub4) strlen((char *) argv[2]), (ub4) OCI_ATTR_PASSWORD,
                 errhp))
    printerr("OCIAttrSet:password");

  if (OCISessionBegin(svchp, errhp, authp, OCI_CRED_RDBMS, (ub4) OCI_DEFAULT))
    printerr("OCISessionBegin");

  if (OCIAttrSet((dvoid *) svchp, (ub4) OCI_HTYPE_SVCCTX, (dvoid *) authp,
                 (ub4) 0, (ub4) OCI_ATTR_SESSION, errhp))
    printerr("OCIAttrSet:OCI_ATTR_SESSION");

  if (OCIHandleAlloc((dvoid *) envhp, (dvoid **) &stmtp, OCI_HTYPE_STMT,
                     0, 0))
    printerr("OCIHandleAlloc:OCI_HTYPE_STMT");

  if (OCIStmtPrepare(stmtp, errhp, (CONST OraText *) selectstmt,
                     (ub4) strlen((const char *) selectstmt),
                     (ub4) OCI_NTV_SYNTAX, (ub4) OCI_DEFAULT))
    printerr("OCIStmtPrepare");

  if (OCIDefineByPos(stmtp, &defnp, errhp, (ub4) 1, (dvoid *) &avg_sal,
                     (sb4) sizeof(avg_sal), SQLT_INT, 0, 0, 0, OCI_DEFAULT))
    printerr("OCIDefineByPos");

  if (status = OCIStmtExecute(svchp, stmtp, errhp, 1, 0, NULL, NULL,
                              OCI_DEFAULT))
    {
      if (status == OCI_NO_DATA)
        {
          printf("No Data found!\n");
          exit(1);
        }
    }

  if (OCISessionEnd(svchp, errhp, authp, OCI_DEFAULT))
    printerr("OCISessionEnd");

  printf("average salary is: %d\n", avg_sal);
}

void checkerr(errhp, status)
     OCIError *errhp;
     sword status;
{
  text errbuf[512];
  sb4 errcode = 0;

  switch (status)
    {
    case OCI_ERROR:
      (void) OCIErrorGet((dvoid *) errhp, 1, NULL, &errcode, errbuf,
                         (ub4) sizeof(errbuf), OCI_HTYPE_ERROR);
      printf("Error - %.*s\n", 512, errbuf);
      break;
    default:
      break;
    }
}

void printerr(call)
     char *call;
{
  printf("Error: %s\n", call);
}
/* end of file ext_mls.c */

C Command-line Tools for Label Security Using Oracle Internet Directory

When Oracle Label Security is used with Oracle Internet Directory, security administrators can use certain commands to create and alter label security attributes stored in the directory.

Note:

You can also use the graphical user interface provided by Oracle Enterprise Manager to manage Oracle Label Security. Detailed documentation can be found in Oracle Enterprise Manager help.

This appendix describes these commands and the parameters they require. They perform updates, inserts and deletes of entries in the directory and are implemented through a script named olsadmintool, which you call from $ORACLE_HOME/bin/olsadmintool. This appendix contains the following sections and tables:

Table C-1, "Oracle Label Security Commands in Categories" lists all the commands, in categories, with links to their explanations. Some of these commands replace PL/SQL procedures (indicated in Table C-2, "olsadmintool Commands Linked to Their Explanations") that are used for the indicated purposes when Oracle Label Security is used without Oracle Internet Directory. Sites already using Oracle Label Security that add Oracle Internet Directory must replace the use of those PL/SQL procedures by switching to use these new commands instead.

Table C-2, "olsadmintool Commands Linked to Their Explanations" then lists the commands alphabetically, with links to their explanations.

Command Explanations, after Table C-2, "olsadmintool Commands Linked to Their Explanations", provides the individual explanations and examples of the commands and their parameters, in alphabetic order.

Relating Parameters to Commands for olsadmintool follows Table C-2, "olsadmintool Commands Linked to Their Explanations" with Summaries in Table C-3, "Summary: olsadmintool Command Parameters" and Table C-4, "Summary of Profile and Default Command Parameters". These tables present summaries of the commands' use of parameters by listing the commands and their parameters in tabular format, enabling you to see patterns of parameter usage.

Table C-3, "Summary: olsadmintool Command Parameters" gives a detailed explanation for each parameter, in alphabetic order and lists the commands in which it is used.

Examples of Using olsadmintool shows typical uses of the tool and the results of the specific examples shown.

Table C-1 Oracle Label Security Commands in Categories

Command Category
Purpose of Command
Command
Replaces PL/SQL Statement

Policies

Create Policy

olsadmintool createpolicy

SA_SYSDBA.CREATE_POLICY

Alter a Level

olsadmintool alterpolicy

SA_SYSDBA.ALTER_POLICY

Drop a Policy

olsadmintool droppolicy

SA_SYSDBA.DROP_POLICY

Add Policy Creator

olsadmintool addpolcreator

None; new

Drop Policy Creator

olsadmintool droppolcreator

None; new

Levels in a Policy

Create a Level

olsadmintool createlevel

SA_COMPONENTS.CREATE_LEVEL

Alter a Level

olsadmintool alterlevel

SA_COMPONENTS.ALTER_LEVEL

Drop a Level

olsadmintool droplevel

SA_COMPONENTS.DROP_LEVEL

Groups in a Policy

Create a Group

olsadmintool creategroup

SA_COMPONENTS.CREATE_GROUP

Alter a Group

olsadmintool altergroup

SA_COMPONENTS.ALTER_GROUP

(also a group parent)

olsadmintool altergroupparent

SA_COMPONENTS.ALTER_GROUP_PARENT

Drop a Group

olsadmintool dropgroup

SA_COMPONENTS.DROP_GROUP

Compartments in a Policy

Create a Compartment

olsadmintool createcompartment

SA_COMPONENTS.CREATE_COMPARTMENT

Alter a Compartment

olsadmintool altercompartment

SA_COMPONENTS.ALTER_COMPARTMENT

Drop a Compartment

olsadmintool dropcompartment

SA_COMPONENTS.DROP_COMPARTMENT

Data Labels

Create a Label

olsadmintool createlabel

SA_LABEL_ADMIN.CREATE_LABEL

Alter a Label

olsadmintool alterlabel

SA_LABEL_ADMIN.ALTER_LABEL

Drop a Label

olsadmintool droplabel

SA_LABEL_ADMIN.DROP_LABEL

Users

Add a User to a Profile

olsadmintool adduser

None; new

Drop a User

olsadmintool dropuser

SA_USER_ADMIN.DROP_USER_ACCESS

Profiles

Create a Profile

olsadmintool createprofile

Replaces the use of several methods. Foot 1 

List Profiles

olsadmintool listprofile

None; new

Describe a Profile

olsadmintool describeprofile

None; new

Drop a Profile

olsadmintool dropprofile

None; new

Policy Administrators

Drop Policy Administrator

olsadmintool addadmin

None; new

Drop Policy Administrator

olsadmintool dropadmin

None; new

Policy Access

Set Audit Options

olsadmintool addpolaccess

None; new

Relating Parameters to Commands for olsadmintool

olsadmintool droppolaccess

None; new

Auditing

Set Audit Options

olsadmintool audit

SA_AUDIT_ADMIN.AUDIT

olsadmintool noaudit

SA_AUDIT_ADMIN.NOAUDIT

Help

Get Help for olsadmintool

olsadmintool command --help

None; new

Footnote 1 Replaces several methods in SA_USER_ADMIN: SET_LEVELS, SET_USER_PRIVILEGES, and SET_DEFAULT_LABEL

Table C-2 olsadmintool Commands Linked to Their Explanations

Purpose of Command
(Links in Alphabetical Order)
Command

Add a User to a Profile

olsadmintool adduser

Add Policy Administrators

olsadmintool addadmin

Add Policy Creator

olsadmintool addpolcreator

Alter a Compartment

olsadmintool altercompartment

Alter a Group

olsadmintool altergroup

Alter a Group's Parent

olsadmintool altergroupparent

Alter a Label

olsadmintool alterlabel

Alter a Level

olsadmintool alterlevel

Alter a Level

olsadmintool alterpolicy

Cancel Audit Options

olsadmintool noaudit

Create a Compartment

olsadmintool createcompartment

Create a Group

olsadmintool creategroup

Create a Label

olsadmintool createlabel

Create a Level

olsadmintool createlevel

Create a Profile

olsadmintool createprofile

Create Policy

olsadmintool createpolicy

Describe a Profile

olsadmintool describeprofile

Drop a Compartment

olsadmintool dropcompartment

Drop a Group

olsadmintool dropgroup

Drop a Label

olsadmintool droplabel

Drop a Level

olsadmintool droplevel

Drop a Policy

olsadmintool droppolicy

Drop a Profile

olsadmintool dropprofile

Drop a User

olsadmintool dropuser

Drop Policy Administrator

olsadmintool dropadmin

Drop Policy Creator

olsadmintool droppolcreator

Get Help for an olsadmintool Command

olsadmintool command name --help

List Profiles

olsadmintool listprofile

Set Audit Options

olsadmintool audit

Command Explanations

In the command explanations that follow, some parameters are optional, which is indicated by enclosing such a parameter within brackets. The two most common examples are [ -b admin context ] and [-p port], indicating that it is optional to specify either the administrative context for the command or the port through which to connect to Oracle Internet Directory. (Default port is 389.)

The use of two dashes (--, no space) is required for all parameters other than b, h, p, D, and w, which are preceded by a single dash. The double dash indicates the need to specify the full or long version of the name or parameter being used. If any such name or parameter contains spaces, it must be enclosed by double quotation marks, for example, "this is an extremely long name or parameter."

Each command appears in this listing on multiple lines for readability, but in reality, would be given out as a single long string on the command line.

Add a User to a Profile

olsadmintool adduser --polname <policy name> --profname <profilename> --userdn
<enterprise user DN>[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN>
-w <bind password>

Description of the adduser command Use the adduser command to add an enterprise user to a profile within a policy. Provide the profile and policy names and the user DN.Foot 1  Enterprise users are normal Oracle Internet Directory users with the additional capability of connecting to the database. Users added to a profile must be enterprise users.

Example of the adduser command 

olsadmintool adduser --polname tradesecret --profname topsales --userdn "cn=perot"
-b "cn=EDS" -h ford -p 1890 -D cn=lbacsys -w lbacsyspwrd

Note:

If you have users in Oracle Internet Directory that have been imported from a third party directory, then you need to set the objectclass attribute for these users to orcluser before running the olsadmintool adduser command.

Add Policy Administrators

olsadmintool addadmin --polname <policy name> --admindn <admin DN>
[ -b <admin context>] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the addadmin command 

Use the addadmin command to add an enterprise user to the administrative group for a policy, so that the user is able to create, modify, or delete the specified policy's metadata. Provide the policy name and the new administrator's DN. This group should contain only enterprise users.

Example of the addadmin command 

olsadmintool addadmin --polname defense --admindn "cn=scott,c=us"
-h yippee -D cn=lbacsys -w lbacsys

Add Policy Creator

olsadmintool addpolcreator --userdn <user DN>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the addpolcreator command 

Use the addpolcreator command to enable the specified user to create policies. Provide the DN for the user.

Example of the addpolcreator command

olsadmintool addpolcreator --userdn "cn=scott" -h yippee -D cn=lbacsys -w lbacsys

Alter a Compartment

olsadmintool altercompartment --polname <policy name> --shortname
<short compartment name> --longname <new long compartment name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the altercompartment command Use the altercompartment command to change the long name of a compartment. Provide the name of the policy, the short name of the compartment, and the new long name of the compartment.

Example of the altercompartment command 

olsadmintool altercompartment --polname defense --shortname A --longname "Allied
Forces" -h yippee -D cn=defense_admin -w Easy2rem

Alter a Group

olsadmintool altergroup --polname <policy name> --shortname <short group name>
--longname <"new long group name">
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the altergroup command Use the altergroup command to change the long name for a group component or parent group. Provide the name of the policy, the short name of the group, and the long name of the group.

Example of the altergroup command 

olsadmintool altergroup --polname defense --shortname US --longname "United States
of America"  -h yippee -D cn=defense_admin -w Easy2rem

Alter a Group's Parent

olsadmintool altergroupparent --polname <policy name> --shortname
<short group name> [--parentname <new parent group name> ] [--clearparent]
--longname <"new long group name"> [--parentname <new short group name> ]
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the altergroupparent command Use the altergroupparent command to change or remove the parent group of a group. Provide the name of the policy, the short name of the group, and either the short name of the parent group or the clearparent flag, but not both.

Examples of the altergroupparent command 

olsadmintool altergroupparent --polname defense --shortname US --parentname
"Earth" -h yippee -p 5678 -D cn=defense_admin -w Easy2rem
or
olsadmintool altergroupparent --polname defense --shortname US --clearparent
-h yippee -p 5678 -D cn=defense_admin -w Easy2rem

Alter a Label

olsadmintool alterlabel --polname <policy name> --tag <tag number>
--value <new label value>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the alterlabel command Use the alterlabel command to change the character string defining the label associated with a label tag. Provide the policy name, the numeric tag of the label, and the new character string representing the label.

Example of the alterlabel command 

olsadmintool alterlabel --polname defense --tag 100 --value "TS:A:US" -h yippee
-D cn=defense_admin -w Easy2rem

Alter a Level

olsadmintool alterlevel --polname <policy name> --shortname <short level name>
--longname <"new long level name">
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the alterlevel command Use the alterlevel command to change the long name of a level. Provide the name of the policy, the short name of the level, and the new long name of the level.

Example of the alterlevel command 

olsadmintool alterlevel --polname defense --shortname TS
--longname "VERY TOP SECRET" -h yippee -D cn=defense_admin -w Easy2rem

Alter Policy

olsadmintool alterpolicy --name <policy name> --options <new options>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

where <new options> can be any combination of the following entries:
INVERSE_GROUP, HIDE, LABEL_DEFAULT, LABEL_UPDATE, CHECK_CONTROL,
READ_CONTROL,WRITE_CONTROL,INSERT_CONTROL, DELETE_CONTROL,
UPDATE_CONTROL, ALL_CONTROL, or NO_CONTROL

Description of the alterpolicy command Use the alterpolicy command to alter the options of a policy. Provide the name of the policy and the new options.

Example of the alterpolicy command 

olsadmintool alterpolicy --name defense --options "READ_CONTROL,INSERT_CONTROL"
-h yippee -D cn=defense_admin -w Easy2rem

Cancel Audit Options

olsadmintool noaudit --polname <policy name> --options <audit option name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

where <audit option name> can be any combination of APPLY, REMOVE, SET, PRIVILEGE

Description of the noaudit command Use the noaudit command to cancel the audit options for a policy. Provide the policy name and the options that are no longer to be audited.

Example of the noaudit command 

olsadmintool noaudit --polname defense --options "APPLY,PRIVILEGES" -h yippee
-D cn=defense_admin -w Easy2rem

Create a Compartment

olsadmintool createcompartment --polname <policy name> --tag <tag number>
--shortname <short compartment name> --longname <"long compartment name">
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the createcompartment command Use the createcompartment command to create a new compartment component. Provide the name of the policy, the tag numeric value of the compartment, the short name of the compartment, and the long name of the compartment.

Example of the createcompartment command 

olsadmintool createcompartment --polname defense --tag 100 --shortname A
--longname Alpha -h yippee -D cn=defense_admin -w Easy2rem

Create a Group

olsadmintool creategroup --polname <policy name> --tag <tag number>
--shortname <short group name> --longname <"long group name">
[--parentname <parent group name>]
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the creategroup command Use the creategroup command to create a new group component. Provide the name of the policy, the tag numeric value of the group, the short name of the group, the long name of the group, and the parent group name (optional).

Example of the creategroup command 

olsadmintool creategroup --polname defense --tag 55 --shortname US
--longname "United States" -h yippee -D cn=defense_admin -w Easy2rem

Create a Label

olsadmintool createlabel --polname <policy name> --tag <tag number>
--value <label value>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the createlabel command Use the createlabel command to create a valid data label. Provide the policy name, the numeric tag of the label to be created, and the character string representation of the label.

Example of the createlabel command 

olsadmintool createlabel --polname defense --tag 100 --value "TS:A,B:US,CA"
-h yippee -D cn=defense_admin -w Easy2rem

Create a Level

olsadmintool createlevel --polname <policy name> --tag <tag number>
--shortname <short level name> --longname <"long level name">
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the createlevel command Use the createlevel command to create a new level component. Provide the name of the policy, the tag numeric value, the short name of the level, and the long name of the level.

Example of the createlevel command 

olsadmintool createlevel --polname defense --tag 100 --shortname TS
--longname "TOP SECRET" -h yippee -D cn=defense_admin -w Easy2rem

Create a Profile

olsadmintool createprofile --polname <policy name> --profname <profile name>
--maxreadlabel <max read label> --maxwritelabel <max write label>
--minwritelabel <min write label> --defreadlabel <default read label>
--defrowlabel <default row label> --privileges <privileges separated by comma>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the createprofile command Use the createprofile command to create a new profile. Provide the policy name, the profile name, and either privileges, labels, or both privileges and labels. (A user profile can have either null label information or null privilege information, but not both null at the same time.) For labels, specify the maximum label users in this profile can use to read data, the maximum label users in this profile can use to write data, the minimum label users in this profile can use to write data, the default label for reading, the default row label for writing. For privileges, enclose in quotation markets list of privileges, separated by commas, for members of this profile.

Example of the createprofile command 

olsadmintool createprofile --polname topsecret --profname topsales
--maxreadlabel "TS:A,B:US,CA" --maxwritelabel "TS:A,B:US,CA"
--minwritelabel "C" --defreadlabel "TS:A,B:US,CA"
--defrowlabel "C:A,B:US,CA"
--privileges "READ,COMPACCESS,WRITEACROSS"
-b EDS -h ford -p 1890 -D cn=lbacsys -w lbacsyspwrd

Create Policy

olsadmintool createpolicy --name <policy name> --colname <column name>
--options <options separated by commas>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

where <new options> can be any combination of the following entries:
INVERSE_GROUP, HIDE, LABEL_DEFAULT, LABEL_UPDATE, CHECK_CONTROL, READ_CONTROL,
WRITE_CONTROL,INSERT_CONTROL, DELETE_CONTROL, UPDATE_CONTROL, ALL_CONTROL,
or NO_CONTROL

Description of the createpolicy command Use the createpolicy command to create a policy. Provide the name of the policy, the name of its label column, and the options.

Example of the createpolicy command 

olsadmintool createpolicy --name defense --colname defense_col
--options "READ_CONTROL,UPDATE_CONTROL" -h yippee -p 389 -D cn=defense_admin
-w Easy2rem

Describe a Profile

olsadmintool describeprofile --polname <policy name> --profname <profile name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the describeprofile command 

 Use the describeprofile command to see the contents of the specified profile in the specified policy. Provide the policy name and the name of the profile.

Example of the describeprofile command 

olsadmintool describeprofile --polname defense --profname contractors
-h yippee -D cn=defense_admin -w Easy2rem

Drop a Compartment

olsadmintool dropcompartment --polname <policy name>
--shortname <short compartment name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the dropcompartment command Use the dropcompartment command to remove a compartment component. Provide the name of the policy and the short name of the compartment.

Example of the dropcompartment command 

olsadmintool dropcompartment --polname defense --shortname A
-h yippee -D cn=defense_admin -w Easy2rem

Drop a Group

olsadmintool dropgroup --polname <policy name> --shortname <short group name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the dropgroup command Use the dropgroup command to remove a group component. Provide the policy name and the short group name.

Example of the dropgroup command 

olsadmintool dropgroup --polname defense --shortname US
-h yippee -D cn=defense_admin -w Easy2rem

Drop a Label

olsadmintool droplabel --polname <policy name> --value <label value>
-h yippee [-p <port>] -D <bind DN> -w <bind password>

Description of the droplabel command Use the droplabel command to drop a label from the policy. Provide the policy name and the string representation of the label.

Example of the droplabel command 

olsadmintool droplabel --polname defense --value "TS:A:US"
h yippee -D cn=defense_admin -w Easy2rem

Drop a Level

olsadmintool droplevel --polname <policy name> --shortname <short level name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the droplevel command Use the droplevel command to remove a level component from a specified policy. Provide the name of the policy and the short name of the level.

Example of the droplevel command 

olsadmintool droplevel --polname defense --shortname TS
-h yippee -D cn=defense_admin -w Easy2rem

Drop a Policy

olsadmintool droppolicy --name <policy name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the droppolicy command Use the droppolicy command to drop a policy. Provide the name of the policy to be dropped. For directory-enabled installations of Oracle Label Security, refer to "Subscribing Policies in Directory-Enabled Label Security".

Example of the droppolicy command 

olsadmintool droppolicy --name defense -h yippee -D cn=defense_admin -w Easy2rem

Drop a Profile

olsadmintool dropprofile --polname <policy name> --profname <profile name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the dropprofile command Use the dropprofile command to remove the specified profile. Provide the policy name and the name of the profile to be dropped.

Note:

Dropping a profile removes the authorization on that policy for all the users in the dropped profile. The users will be unable to see data protected by that policy.

Example of the dropprofile command 

olsadmintool dropprofile --name defense --profname employees
-h yippee -D cn=defense_admin -w Easy2rem

Drop a User

olsadmintool dropuser --polname <policy name> --profname <profilename>
--userdn <enterprise user DN>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the dropuser command Use the dropuser command to drop a user from the specified profile in the specified policy. Provide the policy name, the name of the profile, and the DN of the user.

Example of the dropuser command 

olsadmintool dropuser --polname defense --profname contractors
--userdn "cn=hanssen,c=us" -h yippee -D cn=defense_admin -w Easy2rem

Drop Policy Administrator

olsadmintool dropadmin --polname <policy name> --admindn <admin DN>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the dropadmin command Use the dropadmin command to remove an enterprise user from the administrative group of a policy, so that the user is no longer able to create, modify, or delete the specified policy's metadata. Provide the policy name and the DN of the administrator to be removed from the administrative group.

Example of the dropadmin command 

olsadmintool dropadmin --polname defense --admindn "cn=scott,c=us"
-h yippee -D cn=lbacsys -w lbacsys

Drop Policy Creator

olsadmintool droppolcreator --userdn <user DN>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the droppolcreator command Use the droppolcreator command to cancel the ability of the specified user to create policies. Provide the user's DN.

Example of the droppolcreator command 

olsadmintool droppolcreator --userdn "cn-scott,c=us"
-b UA -h yippee -p 1890 -D <bind DN> -w <bind password>

Get Help for an olsadmintool Command

olsadmintool <command name> --help

List Profiles

olsadmintool listprofile --polname <policy name>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Description of the listprofile command Use the listprofile command to see a list of all profiles in a given policy. Provide the policy name.

Example of the listprofile command 

olsadmintool listprofile --polname defense -b CIA
-h yippee -D cn=defense_admin -w Easy2rem

Set Audit Options

olsadmintool audit --polname <policy name> --options <audit option name>
--type <audit option type> --success <audit success type>
[ -b <admin context> ] -h <OID host> [-p <port>] -D <bind DN> -w <bind password>

where <audit option name> can be any combination of APPLY, REMOVE, SET, PRIVILEGE,
type can be "session" or "access", and success can be "successful",
"not successful" or "both".

Description of the audit command Use the audit command to set the audit options for a policy. Provide the policy name, the options to be audited, the type of audit, and the type of success to be audited.

Example of the audit command 

olsadmintool audit --polname defense --options "APPLY,PRIVILEGE" --type session
--success success -h yippee -D cn=defense_admin -w Easy2rem

Relating Parameters to Commands for olsadmintool

All olsadmintool commands must specify connection parameters: the OID host, the bind DN, the bind password, and optionally, the port through which the connection to Oracle Internet Directory is to be made. (The default port is 389.)

All olsadmintool commands may specify, as needed, the subscriber/administrative-context using the -b flag.

The fact that specifying a parameter is optional, such as a port or an administrative context, is shown by enclosing the parameter within brackets. The two most common examples are [ -b admin context] and [-p port].

Since every command must specify a host, bind DN, and password, and may, if needed, also specify an administrative context, Table C-3, "Summary: olsadmintool Command Parameters" uses the abbreviation CON to represent all of these connection parameters as a group:

[ -b <admin context> ] h <OID host> [-p <port>] -D <bind DN> -w <bind password>

Summaries

Table C-3, "Summary: olsadmintool Command Parameters" summarizes the commands in the following categories:

Policies: creating, altering, or dropping policies or their components, that is, levels, groups, and compartments

Data labels: creating, altering, or dropping them

Administrators and policy creators: adding or dropping them

Users: adding or dropping users from a profile

Auditing options: setting the options for what to audit for a policy

Profiles: creating, listing, describing, or dropping them

Default read or row labels: setting them

In Table C-3, "Summary: olsadmintool Command Parameters" and Table C-4, "Summary of Profile and Default Command Parameters", the column headings show only the parameters, not the keywords that must precede them. For example, Table C-3, "Summary: olsadmintool Command Parameters" shows policyname and column-name as parameters for the createpolicy command, without showing the keywords that must precede them (--name and --colname). These keywords are shown as required in each of the individual command descriptions, such as at Create Policy.

Table C-3, "Summary: olsadmintool Command Parameters" explains the individual parameters that are used as column headings in the summaries of Table C-3, "Summary: olsadmintool Command Parameters" and Table C-4, "Summary of Profile and Default Command Parameters".

In all these tables:

X means required, and O means unused or omitted.

OptionsP means policy enforcement options, that is, any combination of the following entries, separated by a comma:

INVERSE_GROUP

HIDE

LABEL_DEFAULT

LABEL_UPDATE

CHECK_CONTROL

READ_CONTROL

WRITE_CONTROL

INSERT_CONTROL

DELETE_CONTROL

UPDATE_CONTROL

ALL_CONTROL

NO_CONTROL

OptionsA means audit options, that is, any comma-separated combination of the following entries: SET, APPLY, REMOVE, or PRIVILEGE.

Table C-3 Summary: olsadmintool Command Parameters

Command Category
Commands & Parameters

Policies

Command

policy
name

column-
name

optionsP

CON

olsadmintool createpolicy

X

X

X

X

olsadmintool alterpolicy

X

O

X

X

olsadmintool droppolicy

X

O

O

X

Within a Policy, Create:

Command

policy
name

tag

short
name

long
name

CON

parent
name

a level

olsadmintool createlevel

X

X

X

X

X

O

a group

olsadmintool creategroup

X

X

X

X

X

[ X ]

a compartment

olsadmintool createcompartment

X

X

X

X

X

O

Within a Policy, Alter:

a level

olsadmintool alterlevel

X

O

u

u

u

O

a group or group parent

olsadmintool altergroup

X

O

X

X

X

O

olsadmintool altergroupparent

X

O

X

O

X

[X]

Command

policy
name

tag

short
name

long
name

CON

parent
name

a compartment

olsadmintool altercompartment

X

O

X

X

X

O

Within a Policy, Drop:

level

olsadmintool droplevel

X

O

X

O

X

O

group

olsadmintool dropgroup

X

O

X

O

X

O

compartment

olsadmintool dropcompartment

X

O

X

O

X

O

Data Labels

Command

policy
name

tag

value

CON

Create label

olsadmintool createlabel

X

X

X

X

Alter data label

olsadmintool alterlabel

X

X

X

X

Drop data label

olsadmintool droplabel

X

O

X

X

Policy Administrators

Command

policy
name

userDN

CON

Add an Admin

olsadmintool addadmin

X

X

X

Drop an Admin

olsadmintool dropadmin

X

X

X

Policy Creation

olsadmintool addpolcreator

O

X

X

olsadmintool droppolcreator

O

X

X

Users

Command

policy
name

profile
name

userDN

CON

Add a User

olsadmintool adduser

X

X

X

X

Drop a User

olsadmintool dropuser

X

X

X

X

Auditing

olsadmintool audit

X

optionsA

type

success

CON

olsadmintool noaudit

X

X

X

X

X

Help on olsadmintool

olsadmintool <commandname>
-- help

O

O

O

O

O

Table C-4 Summary of Profile and Default Command Parameters

Profile Action
Profile Command
Policy
Name
Profile
Name
Max
Read
Label
Max
Write
Label
Min
Write
Label
Def
Read
Label
Def
Row
Label
Priv's
CON

Create a ProfileFoot 1 

olsadmintool createprofile

X

X

X

X

X

X

X

X

X

List Profiles

olsadmintool

list profile

X

O

O

O

O

O

O

O

X

Describe a Profile

olsadmintool describe profile

X

X

O

O

O

O

O

O

X

Drop a Profile

olsadmintool drop profile

X

X

O

O

O

O

O

O

X

Footnote 1 In createprofile, specifying both privileges and labels is not required: a profile can specify labels, privileges, or both.

Examples of Using olsadmintool

The subsections that follow illustrate using the olsadmintool commands in typical tasks needed to set up Oracle Label Security in an Oracle Internet Directory environment. Each command appears in this listing on multiple lines for readability, but in reality, would be given out as a single long string on the command line. The summarized results of carrying out all these commands appear in Results of These Examples, which follows the last example.

Make Other Users Policy Creators

Create Policies with Valid Options

Create Policy Administrators

Create Some Compartments

Create Some Groups

Create Some Labels

Create a Profile

Add a User to the Profile

Add Another User to the Profile

Set Some Audit Options

Make Other Users Policy Creators

ORACLE_HOME/bin/olsadmintool addpolcreator --userdn "cn=snamudur,c=us"
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=lbacsys,c=us" -w lbacsys

Create Policies with Valid Options

ORACLE_HOME/bin/olsadmintool createpolicy --name Policy1 --colname pol1
--options READ_CONTROL,WRITE_CONTROL -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 -D "cn=snamudur,c=us" -w snamudur

ORACLE_HOME/bin/olsadmintool createpolicy --name Policy2 --colname pol2
--options READ_CONTROL -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 -D "cn=lbacsys,c=us" -w lbacsys

Create Policy Administrators

ORACLE_HOME/bin/olsadmintool addadmin --polname Policy1
--admindn "cn=shwong,c=us" -b "ou=Americas,o=Oracle,c=US" -h yippee -p 389
-D "cn=snamudur,c=us" -w snamudur

ORACLE_HOME/bin/olsadmintool addadmin --polname Policy2
--admindn "cn=shwong,c=us" -b "ou=Americas,o=Oracle,c=US" -h yippee -p 389
-D "cn=lbacsys,c=us" -w lbacsys

Create Some Levels

ORACLE_HOME/bin/olsadmintool createlevel --polname Policy1 --tag 100
--shortname TS --longname "TOP SECRET" -b "ou=Americas,o=Oracle, c=US"
-h yippee -p 389 -D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool createlevel --polname Policy1 --tag 99
--shortname S --longname SECRET -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 -D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool createlevel --polname Policy1 --tag 98
--shortname U --longname UNCLASSIFIED -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Create Some Compartments

ORACLE_HOME/bin/olsadmintool createcompartment --polname Policy1 --tag 100
--shortname A --longname ALPHA -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool createcompartment --polname Policy1 --tag 99
--shortname B --longname BETA -b "ou=Americas,o=Oracle,c=US"
-h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Create Some Groups

ORACLE_HOME/bin/olsadmintool creategroup --polname Policy1 --tag 100
--shortname G1 --longname GROUP1
-b "ou=Americas,o=Oracle,c=US"  -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool creategroup --polname Policy1 --tag 99
--shortname G2 --longname GROUP2
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool creategroup --polname Policy1 --tag 98
--shortname G3 --longname GROUP3
-b "ou=Americas,o=Oracle,c=US"  -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Create Some Labels

ORACLE_HOME/bin/olsadmintool createlabel --polname Policy1
--tag 100 --value TS:A:G1
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

ORACLE_HOME/bin/olsadmintool createlabel --polname Policy1 --tag 101
--value TS:A,B:G2
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Create a Profile

ORACLE_HOME/bin/olsadmintool createprofile --polname Policy1 --profname Profile1
--maxreadlabel TS:A:G1 --maxwritelabel TS:A:G1 --minwritelabel U::
--defreadlabel U:A:G1 --defrowlabel U:A:G1 --privileges WRITEUP,READ
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Add a User to the Profile

ORACLE_HOME/bin/olsadmintool adduser --polname Policy1 --profname Profile1
--userdn cn=nina,ou=Asia,o=microsoft,l=seattle,st=WA,c=US
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Add Another User to the Profile

ORACLE_HOME/bin/olsadmintool adduser --polname Policy1 --profname Profile1
--userdn cn=daniel,ou=France,o=oracle,l=madison,st=WI,c=US
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Set Some Audit Options

ORACLE_HOME/bin/olsadmintool audit --polname Policy1 --option "SET,APPLY"
--type SESSION --success BOTH
-b "ou=Americas,o=Oracle,c=US" -h yippee -p 389 -D "cn=shwong,c=us" -w shwong

Results of These Examples

As a result of running the sets of olsadmintool commands outlined, this sample Oracle Label Security site has the following structure:

Policy creators: User snamudur

Policies: Policy1 and Policy2

Policy Administrators: User shwong

Levels, Compartments, and Groups: Refer to Table C-5, "Label Component Definitions from Using olsadmintool Commands".

Table C-5 Label Component Definitions from Using olsadmintool Commands

Label Component
Tag
Short Name
Long Name

Level

100

TS

TOP SECRET

99

S

SECRET

98

U

UNCLASSIFIED

Compartment

100

A

ALPHA

99

B

BETA

Group

100

G1

GROUP1

99

G2

GROUP2

98

G3

GROUP3

Data labels: Tag 100 for TS:A:G1 and tag 101 for TS:A,B:G2

Users: Nina, from the Asia group of Microsoft, based in Seattle, Washington, managed under the Americas organization of the US Oracle organization, and Daniel, from the France group of Oracle in Madison, Wisconsin, managed under the same organization.

Profiles: Refer to Table C-6, "Contents of Profile1 from Using olsadmintool Commands".

Table C-6 Contents of Profile1 from Using olsadmintool Commands

Profile Element
Contents
Long-name Expansion or Meaning

MaxReadLabel

TS:A:G1

TOP SECRET:ALPHA:GROUP1

MaxWriteLabel

TS:A:G1

TOP SECRET:ALPHA:GROUP1

MinWriteLabel

U::

UNCLASSIFIED (not restricted to any compartments or groups)

DefReadLabel

U:A:G1

UNCLASSIFIED:ALPHA:GROUP1

DefRowLabel

U:A:G1

UNCLASSIFIED:ALPHA:GROUP1

Privileges

WRITE_UP, READ

User can read any row and raise the level of rows the user writes.

Auditing options: SET, APPLY, SESSION, and BOTH

Footnote Legend

Footnote 1: Command FootnoteEvery command must include the directory host name, the bind DN, and the bind password. Any command may, as needed, also supply the subscriber administrative context (optional), the directory port number (also optional), or both. See also Table C-3, "Summary: olsadmintool Command Parameters" for additional details on these parameters.

D Oracle Label Security in an Oracle RAC Environment

This appendix discusses using Oracle Label Security in an Oracle Real Application Clusters (Oracle RAC) environment. It includes the following sections:

Using Oracle Label Security Policy Functions in an Oracle RAC Environment

Using Transparent Application Failover in Oracle Label Security

Using Oracle Label Security Policy Functions in an Oracle RAC Environment

Policy changes made on one instance are available to other instances in the Oracle RAC immediately. It is not necessary to restart the other instances to pick up the changes.

Important changes made on one database instance are automatically propagated to the other instances. One example would be creating a new policy. Another would be altering the policy options.

Propagating such changes ensures two valuable protections:

That all users of the table are subject to the same policy

That if any instance fails, continuation of its work by other instances will use the same policies and parameters that were in force immediately prior to that failure. So, if a policy had been enabled or disabled, it would be seen as such in all instances.

If an administrator changes policy information in one instance by using the policy functions listed in Table D-1, Oracle Label Security stores the relevant information about whatever that function call changed. The new information is immediately available to the other active instances in the Oracle RAC, enabling uniformity among users of the affected policies.

Table D-1 Policy Functions Preserving Status in an Oracle RAC Environment

Policy Functions
Description

SA_SYSDBA.CREATE_POLICY

Creates a new policy

SA_SYSDBA.DROP_POLICY

Drops an existing policy

SA_SYSDBA.ENABLE_POLICY

Enables an existing policy

SA_SYSDBA.DISABLE_POLICY

Disables an existing policy

SA_SYSDBA.ALTER_POLICY

Alters an existing policy

Using Transparent Application Failover in Oracle Label Security

Session information is preserved on Transparent Application Failover. Any changes to the session's information by way of session functions listed in Table D-2 are preserved on Transparent Application Failover.

For example, suppose a user Scott is logged on with default label Top Secret. If he calls sa_session.set_label() to change his session label to Secret, and a failover to another instance occurs, he will see no change but his session label remains Secret.

Preserving current user session information means that the access permissions and restrictions on what data that user can see or affect remain as they were. Despite the failover, the user can see and affect only the tables and rows accessible before the failover. If preservation were not the case, failing over to another instance could cause or enable the user to see a different set of data.

Whenever one of the session functions listed in Table D-2 is used, Oracle Label Security stores the relevant information about whatever was changed by that function call.

Table D-2 Session Functions Preserving Status in an Oracle RAC Environment

Session Functions
Description

SA_SESSION.SET_LABEL

Lets the user set a new level and new compartments and groups to which he or she has read access

SA_SESSION.SET_ROW_LABEL

Lets the user set the default row label that will be applied to new rows

SA_SESSION.SAVE_DEFAULT_LABELS

Lets the user store the current session label and row label as the default for future sessions

SA_SESSION.RESTORE_DEFAULT_LABELS

Lets the user reset the current session label and row label to the stored default settings

SA_SESSION.SET_ACCESS_PROFILE

Sets the Oracle Label Security authorizations and privileges of the database session to those of the specified user

E Oracle Label Security PL/SQL Packages

This appendix provides the syntax for the Oracle Label Security PL/SQL packages.

SA_AUDIT_ADMIN Oracle Label Security Auditing PL/SQL Package

SA_COMPONENTS Label Components PL/SQL Package

SA_LABEL_ADMIN Label Management PL/SQL Package

SA_POLICY_ADMIN Policy Administration PL/SQL Package

SA_SESSION Session Management PL/SQL Package

SA_SYSDBA Policy Management PL/SQL Package

SA_USER_ADMIN User, Levels, Groups, and Compartments PL/SQL Package

SA_UTL PL/SQL Utility Functions and Procedures

See Also:

"Using Dominance Functions" for additional standalone Oracle Label Security functions

SA_AUDIT_ADMIN Oracle Label Security Auditing PL/SQL Package

If you are not using unified auditing, then you can use the packages that are described in this section to configure auditing that is specific to Oracle Label Security. If you are using unified auditing, then see Oracle Database Security Guide for information about creating unified audit policies for Oracle Label Security. In a unified auditing environment, no new audit records will be generated as a result of setting the procedures that are described in this section.

After you have enabled systemwide auditing, you can use SA_AUDIT_ADMIN PL/SQL package procedures to enable or disable Oracle Label Security auditing. To use this package, you must be granted the policy_DBA role (for example, HR_OLS_POL_DBA for a role for the hr_ols_pol policy) and the EXECUTE privilege for the SA_AUDIT_ADMIN package.

Table E-1 lists the SA_AUDIT_ADMIN PL/SQL package procedures.

Table E-1 SA_AUDIT_ADMIN PL/SQL Package Contents

Procedure
Description

SA_AUDIT_ADMIN.AUDIT Procedure

Enables policy-specific auditing. Auditing of each policy is independent of the others

SA_AUDIT_ADMIN.AUDIT_LABEL Procedure

Shows whether labels are being recorded in audit records for the policy

SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED Function

Shows whether labels are being recorded in audit records for the policy

SA_AUDIT_ADMIN.CREATE_VIEW Procedure

Creates an audit trail view named DBA_policyname_AUDIT_TRAIL, which contains the specified policy's label column as well as all the entries in the audit trail written on behalf of this policy

SA_AUDIT_ADMIN.DROP_VIEW Procedure

Drops the audit trail view (created by the SA_AUDIT_ADMIN.CREATE_VIEW procedure) for the specified policy

SA_AUDIT_ADMIN.NOAUDIT Procedure

Disables Oracle Label Security policy-specific auditing

SA_AUDIT_ADMIN.NOAUDIT_LABEL Procedure

Disables the auditing of policy labels

See Also:

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

SA_AUDIT_ADMIN.AUDIT Procedure

The SA_AUDIT_ADMIN.AUDIT procedure enables policy-specific auditing. Auditing of each policy is independent of the others. The audit records capture Oracle Label Security administrative actions and the use of Oracle Label Security privileges that were used during logons, DML executions, and trusted stored procedure invocations.

Syntax

SA_AUDIT_ADMIN.AUDIT (
     policy_name     IN VARCHAR2,
     users           IN VARCHAR2 DEFAULT NULL,
     audit_option    IN VARCHAR2 DEFAULT NULL,
     audit_type      IN VARCHAR2 DEFAULT NULL,
     success         IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-2 SA_AUDIT_ADMIN.AUDIT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

users

Optional. A comma-delimited list of user names to audit, as follows:

If you are auditing OLS administrative actions, then ensure that the users you enter have the policy_DBA role and the EXECUTE privilege for the Oracle Label Security packages.

If you are auditing the use of OLS privileges, then these users do not need to be OLS administrators.

If you do not specify any users, then all users are audited.

To find users who have privileges to modify Oracle Label Security policies, query the USER_NAME column of the DBA_SA_USERS view.

audit_option

Optional. A comma-delimited list of options to be audited. Options are as follows:

APPLY: Audits application of specified Oracle Label Security policies to tables and schemas

REMOVE: Audits removal of specified Oracle Label Security policies from tables and schemas

SET: Audits the setting of user authorizations, and user and program privileges

PRIVILEGES: Audits use of all policy-specific privileges

If not specified, then all default options (that is, options not including privileges) are audited. Audit options for privileged operations should be set explicitly by specifying the PRIVILEGES option, which sets audit options for all privileges.

audit_type

Optional. BY ACCESS or BY SESSION. If not specified, then audit records are written BY SESSION.

success

Optional. SUCCESSFUL if the action was successful, or NOT SUCCESSFUL. If not specified, then audit is written for both.

Examples

The following example audits any failed APPLY and REMOVE attempts by the users psmith and rlayton.

BEGIN
 SA_AUDIT_ADMIN.AUDIT(
  policy_name      => 'hr_ols_pol',
  users            => 'jjones, rlayton',
  audit_option     => 'apply, remove',
  audit_type       => 'by access',
  success          => 'not successful');
END;
/

If the you do not specify any audit options, then all options except the privilege-related ones are audited. You must specify the auditing of privileges explicitly. For example, if you enter the following statement, then the default options are set for the hr_ols_pol policy:

EXEC SA_AUDIT_ADMIN.AUDIT ('hr_ols_pol');

When you enable auditing, it will be performed on all users by session, whether their actions are successful or not.

When you set auditing parameters and options, the new values apply only to subsequent sessions, not to the current session.

Consider also a case in which one SA_AUDIT_ADMIN.AUDIT call (with no users specified) enables auditing for APPLY operations for all users, and then a second call enables auditing of REMOVE operations for a specific user. For example:

EXEC SA_AUDIT_ADMIN.AUDIT ('hr_ols_pol', null, 'apply');
EXEC SA_AUDIT_ADMIN.AUDIT ('hr_ols_pol', 'scott', 'remove');

In this case, SCOTT is audited for both APPLY and REMOVE operations.

SA_AUDIT_ADMIN.AUDIT_LABEL Procedure

Use the SA_AUDIT_ADMIN.AUDIT_LABEL procedure to record policy labels during auditing. It causes the user's session label to be stored in the audit table.

Syntax

SA_AUDIT_ADMIN.AUDIT_LABEL (
     policy_name     IN VARCHAR2);

Parameter

Table E-3 SA_AUDIT_ADMIN.AUDIT_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example writes output indicating whether the Oracle Label Security labels are being audited for the hr_ols_pol policy.

BEGIN
 SA_AUDIT_ADMIN.AUDIT_LABEL(
  policy_name      => 'hr_ols_pol');
END;
/

SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED Function

The SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED function shows whether labels are being recorded in audit records for the policy.

Syntax

SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED (
  policy_name IN VARCHAR2)
RETURN BOOLEAN;

Parameters

Table E-4 SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example writes output indicating whether the Oracle Label Security labels are being audited for the hr_ols_pol policy.

SET SERVEROUTPUT ON
BEGIN
 IF SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED('hr_ols_pol')
  THEN DBMS_OUTPUT.PUT_LINE('OLS hr_ols_pol labels are being audited.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('OLS hr_ols_pol labels not being audited.');
 END IF;
END;
/

SA_AUDIT_ADMIN.CREATE_VIEW Procedure

The SA_AUDIT_ADMIN.CREATE_VIEW procedure creates an audit trail view named DBA_policyname_AUDIT_TRAIL, which contains the specified policy's label column as well as all the entries in the audit trail written on behalf of this policy. If the view name exceeds the database limit of 30 characters, then the user can optionally specify a shorter view name.

See Also:

"Oracle Label Security User-Created Auditing View" to find the columns that are contained in the DBA_policyname_AUDIT_TRAIL view

Syntax

SA_AUDIT_ADMIN.CREATE_VIEW (
     policy_name     IN VARCHAR2,
     view_name       IN VARCHAR2    DEFAULT NULL);

Parameters

Table E-5 SA_AUDIT_ADMIN.CREATE_VIEW Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

view_name

Optional. Specifies the name of the view name. If you omit this setting, then the name defaults to DBA_policyname_AUDIT_TRAIL.

Examples

The following example creates a view called hr_ols_pol_view for the hr_ols_pol policy.

BEGIN
 SA_AUDIT_ADMIN.CREATE_VIEW(
  policy_name      => 'hr_ols_pol',
  view_name        => 'hr_ols_pol_view');
END;
/

SA_AUDIT_ADMIN.DROP_VIEW Procedure

The SA_AUDIT_ADMIN.DROP_VIEW procedure drops the audit trail view for the specified policy.

Syntax

SA_AUDIT_ADMIN.DROP_VIEW (
     policy_name     IN VARCHAR2,
     view_name       IN VARCHAR2    DEFAULT NULL);

Parameters

Table E-6 SA_AUDIT_ADMIN.DROP_VIEW Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

view_name

Specifies an existing view's name. You can find this view by first querying the ALL_SA_POLICIES data dictionary view to find the name of the policy on which the view was based, and then querying ALL_VIEWS data dictionary view to find any views that have the name of the policy.

Example

The following example drops the view called hr_ols_pol_view from the hr_ols_pol policy.

BEGIN
 SA_AUDIT_ADMIN.DROP_VIEW(
  policy_name      => 'hr_ols_pol',
  view_name        => 'hr_ols_pol_view');
END;
/

SA_AUDIT_ADMIN.NOAUDIT Procedure

The SA_AUDIT_ADMIN.NOAUDIT procedure disables Oracle Label Security policy-specific auditing.

Syntax

SA_AUDIT_ADMIN.NOAUDIT (
     policy_name     IN VARCHAR2,
     users           IN VARCHAR2 DEFAULT NULL,
     audit_option    IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-7 SA_AUDIT_ADMIN.NO_AUDIT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

users

Optional. A comma-delimited list of users who were audited. If not specified, then auditing is disabled for all users.

To find users who have privileges to modify Oracle Label Security policies, query the USER_NAME column of the ALL_SA_AUDIT_OPTIONS view.

audit_option

Optional. A comma-delimited list of options to be disabled. Options are as follows:

APPLY: Audits application of specified Oracle Label Security policies to tables and schemas

REMOVE: Audits removal of specified Oracle Label Security policies from tables and schemas

SET: Audits the setting of user authorizations, and user and program privileges

PRIVILEGES: Audits use of all policy-specific privileges

If not specified, then all default options are disabled. Privileges must be disabled explicitly.

Examples

The following example disables auditing for failed APPLY and REMOVE attempts by the users psmith and rlayton.

BEGIN
 SA_AUDIT_ADMIN.NOAUDIT(
  policy_name      => 'hr_ols_pol',
  users            => 'jjones',
  audit_option     => 'apply, remove');
END;
/

You can disable auditing for all enabled options, or only for a subset of enabled options. All auditing for the specified options is disabled for all specified users (or all users, if the users parameter is NULL). For example, the following statement disables auditing of the APPLY and REMOVE operations for users John, Mary, and Scott:

EXEC SA_AUDIT_ADMIN.NOAUDIT ('HR', 'JOHN, MARY, SCOTT', 'APPLY, REMOVE');

Consider also a case in which one AUDIT call enables auditing for a specific user, and a second call (with no user specified) enables auditing for all users. For example:

EXEC SA_AUDIT_ADMIN.AUDIT ('HR', 'SCOTT');
EXEC SA_AUDIT_ADMIN.AUDIT ('HR');

In this case, a subsequent call to NOAUDIT with no users specified (such as the following statement) does not reverse the auditing that was set for SCOTT explicitly in the first call. So, auditing continues to be performed on SCOTT.

EXEC SA_AUDIT_ADMIN.NOAUDIT ('HR');

In this way, even if SA_AUDIT_ADMIN.NOAUDIT is set for all users, Oracle Label Security still audits any users for whom auditing was explicitly set.

Auditing of privileged operations must be specified explicitly. If you run SA_AUDIT_ADMIN.NOAUDIT with no options, the Oracle Label Security will nonetheless continue to audit privileged operations. For example, if auditing is enabled and you enter

EXEC SA_AUDIT_ADMIN.NOAUDIT ('HR');

then auditing will continue to be performed on the privileged operations (such as WRITEDOWN).

SA_AUDIT_ADMIN.NOAUDIT parameters and options that you set apply only to subsequent sessions, not to current sessions.

If you try to enable an audit option that has already been set, or if you try to disable an audit option that has not been set, then Oracle Label Security processes the statement without indicating an error. An attempt to specify an invalid option results in an error message. You can find the status of audit options by querying the ALL_SA_AUDIT_OPTIONS data dictionary view.

SA_AUDIT_ADMIN.NOAUDIT_LABEL Procedure

The SA_AUDIT_ADMIN.NOAUDIT_LABEL procedure disables the auditing of policy labels.

Syntax

SA_AUDIT_ADMIN.NOAUDIT_LABEL (
   policy_name     IN VARCHAR2);

Parameters

Table E-8 SA_AUDIT_ADMIN.NO_AUDIT_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example disables auditing for the hr_ols_pol policy.

BEGIN
 SA_AUDIT_ADMIN.NOAUDIT_LABEL(
  policy_name      => 'hr_ols_pol');
END;
/

SA_COMPONENTS Label Components PL/SQL Package

Table E-9 lists the SA_COMPONENTS PL/SQL package procedures, which you can use to manage the component definitions of an Oracle Label Security label. To use this package, you must be granted the policy_DBA role (for example, HR_OLS_POL_DBA for a role for the hr_ols_pol policy) and the EXECUTE privilege on the SA_COMPONENTS package.

Table E-9 SA_COMPONENTS PL/SQL Package Contents

Procedure
Description

SA_COMPONENTS.ALTER_COMPARTMENT Procedure

Modifies a compartment

SA_COMPONENTS.ALTER_GROUP Procedure

Modifies a group

SA_COMPONENTS.ALTER_GROUP_PARENT Procedure

Modifies a group parent

SA_COMPONENTS.ALTER_LEVEL Procedure

Modifies a level

SA_COMPONENTS.CREATE_COMPARTMENT Procedure

Creates a compartment

SA_COMPONENTS.CREATE_GROUP Procedure

Creates a group

SA_COMPONENTS.CREATE_LEVEL Procedure

Creates a level

SA_COMPONENTS.DROP_COMPARTMENT Procedure

Removes a compartment

SA_COMPONENTS.DROP_GROUP Procedure

Removes a group

SA_COMPONENTS.DROP_LEVEL Procedure

Removes a level

See Also:

Chapter 2, "Understanding Data Labels and User Labels"

"Step 2: Create Data Labels for the Label Security Policy"

SA_COMPONENTS.ALTER_COMPARTMENT Procedure

Use the SA_COMPONENTS.ALTER_COMPARTMENT procedure to change the short name and long name associated with a compartment.

Once set, the comp_num parameter cannot be changed. If the comp_num parameter is used in any existing label, then its short name cannot be changed but its long name can be changed.

Syntax

SA_COMPONENTS.ALTER_COMPARTMENT (
   policy_name       IN VARCHAR2,
   comp_num          IN NUMBER(38),
   new_short_name    IN VARCHAR2,
   new_long_name     IN VARCHAR2);

SA_COMPONENTS.ALTER_COMPARTMENT (
   policy_name       IN VARCHAR2,
   short_name        IN VARCHAR2 DEFAULT NULL,
   new_long_name     IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-10 SA_COMPONENTS.ALTER_COMPARTMENT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

comp_num

Specifies the number of the compartment to be altered. To find a list of existing compartment numbers, query the COMP_NUM column of the ALL_SA_COMPARTMENTS view.

short_name

Specifies the short name of the compartment to be altered (up to 30 characters). To find the current compartment, query the SHORT_NAME column of the ALL_SA_COMPARTMENTS view.

new_short_name

Specifies the new short name of the compartment (up to 30 characters)

new_long_name

Specifies the new long name of the compartment (up to 80 characters).

Example

The following example modifies the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.ALTER_COMPARTMENT (
   policy_name         => 'hr_ols_pol',
   comp_num            => '48',
   new_short_name      => 'FIN',
   new_long_name       => 'FINANCE');
END;
/

SA_COMPONENTS.ALTER_GROUP Procedure

Use the SA_COMPONENTS.ALTER_GROUP procedure to change the short name and long name associated with a group.

Once set, the group_num parameter cannot be changed. If the group is used in any existing label, then its short name cannot be changed, but its long name can be changed.

Syntax

SA_COMPONENTS.ALTER_GROUP (
   policy_name    IN VARCHAR2,
   group_num      IN NUMBER(38),
   new_short_name IN VARCHAR2 DEFAULT NULL,
   new_long_name  IN VARCHAR2 DEFAULT NULL);

SA_COMPONENTS.ALTER_GROUP (
   policy_name    IN VARCHAR2,
   short_name     IN VARCHAR2,
   new_long_name  IN VARCHAR2);

Parameters

Table E-11 SA_COMPONENTS.ALTER_GROUP Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

group_num

Specifies the existing group number to be altered. To find existing group numbers, query the GROUP_NUM column of the ALL_SA_GROUPS view.

short_name

Specifies the existing group short name to be altered. To find existing short names, query the SHORT_NAME column of the ALL_SA_GROUPS view.

new_short_name

Specifies the new short name for the group (up to 30 characters)

new_long_name

Specifies the new long name for the group (up to 80 characters)

Example

The following example modifies the long_name setting for the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.ALTER_GROUP (
   policy_name     => 'hr_ols_pol',
   short_name      => 'ER_FIN',
   new_long_name   => 'ER_FINANCES');
END;
/

SA_COMPONENTS.ALTER_GROUP_PARENT Procedure

The SA_COMPONENTS.ALTER_GROUP_PARENT procedure changes the parent group associated with a particular group.

Syntax

SA_COMPONENTS.ALTER_GROUP_PARENT (
   policy_name     IN VARCHAR2,
   group_num       IN NUMBER(38),
   new_parent_num  IN NUMBER(38));

SA_COMPONENTS.ALTER_GROUP_PARENT (
   policy_name     IN VARCHAR2,
   group_num       IN NUMBER(38),
   new_parent_name IN VARCHAR2);

SA_COMPONENTS.ALTER_GROUP_PARENT (
   policy_name     IN VARCHAR2,
   short_name      IN VARCHAR2,
   new_parent_name IN VARCHAR2);

Parameters

Table E-12 SA_COMPONENTS.ALTER_GROUP_PARENT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

group_num

Specifies the existing group number to be altered. To find existing group numbers, query the GROUP_NUM column of the ALL_SA_GROUPS view.

short_name

Specifies the existing group short name to be altered. To find existing short names, query the SHORT_NAME column of the ALL_SA_GROUPS view.

new_parent_num

Specifies the number of an existing group as the parent group. To find existing parent groups, query the PARENT_NUM column of the ALL_SA_GROUPS view.

new_parent_name

Specifies the short name of an existing group as the parent group. To find existing groups, query the SHORT_NAME column of the ALL_SA_GROUPS view.

Example

The following example modifies the parent name for the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.ALTER_GROUP_PARENT (
   policy_name         => 'hr_ols_pol',
   group_num           => 2100,
   new_parent_name     => 'ER');
END;
/

SA_COMPONENTS.ALTER_LEVEL Procedure

Use the SA_COMPONENTS.ALTER_LEVEL procedure to change the short name and long name associated with a level.

Once they are defined, level numbers cannot be changed. If a level is used in any existing label, then its short name cannot be changed, but its long name can be changed.

Syntax

SA_COMPONENTS.ALTER_LEVEL (
   policy_name     IN VARCHAR2,
   level_num       IN NUMBER(38),
   new_short_name  IN VARCHAR2 DEFAULT NULL,
   new_long_name   IN VARCHAR2 DEFAULT NULL);

SA_COMPONENTS.ALTER_LEVEL (
   policy_name     IN VARCHAR2,
   short_name      IN VARCHAR2,
   new_long_name   IN VARCHAR2);

Parameters

Table E-13 SA_COMPONENTS.ALTER_LEVEL Parameters

Parameter
Description

policy_name

Specifies the policy, which much exist. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

level_num

Specifies the number of the level to be altered. To find existing levels, query the LEVEL_NUM column of the ALL_SA_LEVELS view.

short_name

Specifies the existing short name of the level. To find existing level short names, query the SHORT_NAME column of the ALL_SA_LEVELS view.

new_short_name

Specifies the new short name for the level (up to 30 characters)

new_long_name

Specifies the new long name for the level (up to 80 characters)

Example

The following example modifies the short and long names for the hr_ols_pol policy level.

BEGIN
 SA_COMPONENTS.ALTER_LEVEL (
   policy_name     => 'hr_ols_pol',
   level_num       => 40,
   new_short_name  => 'TS',
   new_long_name   => 'TOP_SECRET');
END;
/

SA_COMPONENTS.CREATE_COMPARTMENT Procedure

Use the SA_COMPONENTS.CREATE_COMPARTMENT procedure to create a compartment and specify its short name and long name. The comp_num parameter determines the order in which compartments are listed in the character string representation of labels.

Syntax

SA_COMPONENTS.CREATE_COMPARTMENT (
   policy_name IN VARCHAR2,
   comp_num    IN NUMBER(38),
   short_name  IN VARCHAR2,
   long_name   IN VARCHAR2);

Parameters

Table E-14 SA_COMPONENTS.CREATE_COMPARTMENT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

comp_num

Specifies the compartment number (0-9999)

short_name

Specifies the short name for the compartment (up to 30 characters)

long_name

Specifies the long name for the compartment (up to 80 characters)

Example

The following example creates a compartment for the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.CREATE_COMPARTMENT (
   policy_name     => 'hr_ols_pol',
   comp_num        => '48',
   short_name      => 'FIN',
   long_name       => 'FINANCE');
END;
/

SA_COMPONENTS.CREATE_GROUP Procedure

Use the SA_COMPONENTS.CREATE_GROUP procedure to create a group and specify its short name and long name, and optionally a parent group.

Syntax

SA_COMPONENTS.CREATE_GROUP (
   policy_name IN VARCHAR2,
   group_num   IN NUMBER(38),
   short_name  IN VARCHAR2,
   long_name   IN VARCHAR2,
   parent_name IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-15 SA_COMPONENTS.CREATE_GROUP Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

group_num

Specifies the group number (0-9999)

short_name

Specifies the short name for the group (up to 30 characters)

long_name

Specifies the long name for the group (up to 80 characters)

parent_name

Specifies the short name of an existing group as the parent group. If NULL, then the group is a top-level group.

Note that the group number affects the order in which groups will be displayed when labels are selected.

Examples

In the following examples, the first creates a parent group, ER, and the second creates a second group that is part of the parent group.

BEGIN
  SA_COMPONENTS.CREATE_GROUP (
   policy_name     => 'hr_ols_pol',
   group_num       => 2000,
   short_name      => 'ER',
   long_name       => 'EAST_REGION');
END;
/

BEGIN
  SA_COMPONENTS.CREATE_GROUP (
   policy_name     => 'hr_ols_pol',
   group_num       => 2100,
   short_name      => 'ER_FIN',
   long_name       => 'ER_FINANCES',
   parent_name     => 'ER');
END;
/

See Also:

"Group Components"

SA_COMPONENTS.CREATE_LEVEL Procedure

Use the SA_COMPONENTS.CREATE_LEVEL procedure to create a level and specify its short name and long name. The numeric values assigned to the level_num parameter determine the sensitivity ranking (that is, a lower number indicates less sensitive data).

Syntax

SA_COMPONENTS.CREATE_LEVEL (
   policy_name       IN VARCHAR2,
   level_num         IN NUMBER(38),
   short_name        IN VARCHAR2,
   long_name         IN VARCHAR2);

Parameters

Table E-16 SA_COMPONENTS.CREATE_LEVEL Parameters

Parameter
Description

policy_name

Specifies the policy, which must exist. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

level_num

Specifies the level number (0-9999)

short_name

Specifies the short name for the level (up to 30 characters)

long_name

Specifies the long name for the level (up to 80 characters)

Example

The following example creates a level for the hr_ols_pol policy.

BEGIN
 SA_COMPONENTS.CREATE_LEVEL (
   policy_name   => 'hr_ols_pol',
   level_num     => 40,
   short_name    => 'HS',
   long_name     => 'HIGHLY_SENSITIVE');
END;
/

SA_COMPONENTS.DROP_COMPARTMENT Procedure

Use the SA_COMPONENTS.DROP_COMPARTMENT procedure to remove a compartment. If the compartment is used in any existing label, then it cannot be dropped. You can find all existing labels by querying the LABEL column of the ALL_SA_DATA_LABELS data dictionary view.

Syntax

SA_COMPONENTS.DROP_COMPARTMENT (
   policy_name IN VARCHAR2,
   comp_num    IN INTEGER);

SA_COMPONENTS.DROP_COMPARTMENT (
   policy_name IN VARCHAR2,
   short_name  IN VARCHAR2);

Parameters

Table E-17 SA_COMPONENTS.DROP_COMPARTMENT Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

comp_num

Specifies the number of an existing compartment for the policy. To find existing compartment numbers, query the COMP_NUM column of the DBA_SA_COMPARTMENTS view.

short_name

Specifies the short name of an existing compartment for the policy. To find existing compartment short names, query the SHORT_NAME column of the DBA_SA_COMPARTMENTS view.

Example

The following example removes the FIN compartment from the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.DROP_COMPARTMENT (
   policy_name     => 'hr_ols_pol',
   short_name      => 'FIN');
END;
/

SA_COMPONENTS.DROP_GROUP Procedure

Use the SA_COMPONENTS.DROP_GROUP procedure to remove a group. If the group is used in an existing label, it cannot be dropped.

Syntax

SA_COMPONENTS.DROP_GROUP (
   policy_name IN VARCHAR2,
   group_num   IN NUMBER(38));

SA_COMPONENTS.DROP_GROUP (
   policy_name IN VARCHAR2,
   short_name  IN VARCHAR2);

Parameters

Table E-18 SA_COMPONENTS.DROP_GROUP Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

group_num

Specifies the number of an existing group for the policy. To find existing group numbers, query the GROUP_NUM column of the ALL_SA_GROUPS view.

short_name

Specifies the short name of an existing group. To find existing group short names, query the SHORT_NAME column of the ALL_SA_GROUPS view.

Example

The following example removes a group based on the group number for the hr_ols_pol policy.

BEGIN
  SA_COMPONENTS.DROP_GROUP (
   policy_name     => 'hr_ols_pol',
   group_num       => 2000);
END;
/

SA_COMPONENTS.DROP_LEVEL Procedure

Use the SA_COMPONENTS.DROP_LEVEL procedure to remove a level. If the level is used in any existing label, then it cannot be dropped.

Syntax

SA_COMPONENTS.DROP_LEVEL (
   policy_name IN VARCHAR2,
   level_num   IN NUMBER(38));

SA_COMPONENTS.DROP_LEVEL (
   policy_name IN VARCHAR2,
   short_name  IN VARCHAR2);

Parameters

Table E-19 SA_COMPONENTS.DROP_LEVEL Parameters

Parameter
Description

policy_name

Specifies the policy, which much exist. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

level_num

Specifies the number of an existing level for the policy. To find existing level numbers, query the LEVEL_NUM column of the ALL_SA_LEVELS view.

short_name

Specifies the short name for the level (up to 30 characters). To find existing level short names, query the SHORT_NAME column of the ALL_SA_LEVELS view.

Example

The following example drops the level 40 from the hr_ols_pol policy.

BEGIN
 SA_COMPONENTS.DROP_LEVEL (
   policy_name     => 'hr_ols_pol',
   level_num       => 40);
END;
/

SA_LABEL_ADMIN Label Management PL/SQL Package

The SA_LABEL_ADMIN PL/SQL package provides an administrative interface to manage the labels used by a policy. To use this package, you must be granted the policy_DBA role (for example, HR_OLS_POL_DBA for a role for the hr_ols_pol policy) and the EXECUTE privilege on the SA_LABEL_ADMIN package.

Table E-20 lists the SA_LABEL_ADMIN package procedures.

Table E-20 SA_LABEL_ADMIN PL/SQL Package Contents

Procedure
Description

SA_LABEL_ADMIN.ALTER_LABEL Procedure

Alters an existing label

SA_LABEL_ADMIN.CREATE_LABEL Procedure

Creates a data label

SA_LABEL_ADMIN.DROP_LABEL Procedure

Removes a label

See Also:

"Creating Data Labels for the Policy Using Cloud Control"

SA_LABEL_ADMIN.ALTER_LABEL Procedure

The SA_LABEL_ADMIN.ALTER_LABEL procedure changes the character string label definition associated with a label tag. Note that the label tag itself cannot be changed.

If you change the character string associated with a label tag, then the sensitivity of the data in the rows changes accordingly. For example, if the label character string TS:A with an associated label tag value of 4001 is changed to the label TS:B, then access to the data changes accordingly. This is true even when the label tag value (4001) has not changed. In this way, you can change the data's sensitivity without the need to update all the rows.

Ensure that when you specify a label to alter, you can refer to it either by its label tag or by its character string value.

Syntax

SA_LABEL_ADMIN.ALTER_LABEL (
   policy_name       IN VARCHAR2,
   label_tag         IN BINARY_INTEGER,
   new_label_value   IN VARCHAR2 DEFAULT NULL,
   new_data_label    IN BOOLEAN  DEFAULT NULL);

SA_LABEL_ADMIN.ALTER_LABEL (
   policy_name       IN VARCHAR2,
   label_value       IN VARCHAR2,
   new_label_value   IN VARCHAR2 DEFAULT NULL,
   new_data_label    IN BOOLEAN  DEFAULT NULL);

Parameters

Table E-21 SA_LABEL_ADMIN.ALTER_LABEL Parameters

Parameter
Description

policy_name

Specifies the name of an existing policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label_tag

Identifies the integer tag assigned to the label to be altered. To find existing label tags, query the LABEL_TAG column of the ALL_SA_LABELS view.

label_value

Identifies the existing character string representation of the label to be altered. To find the existing label values, query the LABEL column of the ALL_SA_LABELS view.

new_label_value

Specifies the new character string representation of the label value. If NULL, the existing value is not changed.

new_data_label

TRUE if the label can be used to label row data. If NULL, the existing value is not changed.

Example

The following example modifies the label_tag and label_value settings of hr_ols_pol policy.

BEGIN
  SA_LABEL_ADMIN.ALTER_LABEL (
   policy_name       => 'hr_ols_pol',
   label_tag         => 1111,
   new_label_value   => 'HS',
   new_data_label    => TRUE);
END;
/

SA_LABEL_ADMIN.CREATE_LABEL Procedure

The SA_LABEL_ADMIN.CREATE_LABEL procedure creates data labels.

Syntax

SA_LABEL_ADMIN.CREATE_LABEL (
   policy_name IN VARCHAR2,
   label_tag   IN BINARY_INTEGER,
   label_value IN VARCHAR2,
   data_label  IN BOOLEAN DEFAULT TRUE);

Parameters

Table E-22 SA_LABEL_ADMIN.CREATE_LABEL Parameters

Parameter
Description

policy_name

Specifies the name of an existing policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label_tag

Specifies a unique integer value representing the sort order of the label, relative to other policy labels (0-99999999). This value must be 1 to 8 digits long.

label_value

Specifies the character string representation of the label to be created. Use the short name of the level, compartment, and group. You can find these values by querying the SHORT_NAME column of the ALL_SA_LEVELS, ALL_SA_COMPARTMENTS, and ALL_SA_GROUPS views.

data_label

TRUE if the label can be used to label row data. Use this to define the label as valid for data.

When you identify valid labels, you specify which of all the possible combinations of levels, compartments, and groups can potentially be used to label data in tables.

Example

The following example creates a label for the hr_ols_pol policy.

BEGIN
  SA_LABEL_ADMIN.CREATE_LABEL (
   policy_name     => 'hr_ols_pol',
   label_tag       => 1111,
   label_value     => 'HS:FIN',
   data_label      => TRUE);
END;
/

Note:

If you create a new label by using the TO_DATA_LABEL procedure, then a system-generated label tag of 10 digits is generated automatically.

However, when Oracle Label Security is installed to work with Oracle Internet Directory, dynamic label generation is not permitted, because labels are managed centrally in Oracle Internet Directory, using olsadmintool commands. Refer to Appendix C, "Command-line Tools for Label Security Using Oracle Internet Directory".

So, when Oracle Label Security is directory-enabled, the TO_DATA_LABEL function is not available and will generate an error message if used.

See Also:

"About Associating the Policy Components with a Named Data Label"

"The Policy Label Column and Label Tags"

SA_LABEL_ADMIN.DROP_LABEL Procedure

The SA_LABEL_ADMIN.DROP_LABEL procedure deletes a specified policy label. Any subsequent reference to the label (in data rows, or in user or program unit labels) will raise an invalid label error.

Use this procedure only while setting up labels, prior to data population. If you should inadvertently drop a label that is being used, you can recover it by disabling the policy, fixing the problem, and then re-enabling the policy.

Syntax

SA_LABEL_ADMIN.DROP_LABEL (
   policy_name       IN VARCHAR2,
   label_tag         IN BINARY_INTEGER);

SA_LABEL_ADMIN.DROP_LABEL (
   policy_name       IN VARCHAR2,
   label_value       IN VARCHAR2);

Parameters

Table E-23 SA_LABEL_ADMIN.DROP_LABEL Parameters

Parameter
Description

policy_name

Specifies the name of an existing policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label_tag

Specifies the integer tag assigned to the label to be dropped. To find existing label tags, query the LABEL_TAG column of the ALL_SA_LABELS view.

label_value

Specifies the string value of the label to be dropped. To find existing label values, query the LABEL column of the ALL_SA_LABELS view.

Caution:

Do not drop a label that is in use anywhere in the database.

Example

The following example drops the hr_ols_pol policy label based on its label_tag setting.

BEGIN
  SA_LABEL_ADMIN.DROP_LABEL (
   policy_name     => 'hr_ols_pol',
   label_tag       => 1111);
END;
/

SA_POLICY_ADMIN Policy Administration PL/SQL Package

Table E-24 describes the SA_POLICY_ADMIN PL/SQL package procedures, which you can use to manage Oracle Label Security policies as a whole. To use this package, you must be granted the policy_DBA role (for example, HR_OLS_POL_DBA for a role for the hr_ols_pol policy) and the EXECUTE privilege for the SA_POLICY_ADMIN package.

Table E-24 SA_POLICY_ADMIN PL/SQL Package Contents

Procedure
Description

SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY Procedure

Changes the default enforcement options for the policy

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure

Applies the specified policy to all of the existing tables in a schema (that is, to those that do not already have the policy applied) and enables the policy for these tables

SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure

Adds the specified policy to a table

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY Procedure

Disables the enforcement of the policy for all of the tables in the specified schema, without changing the enforcement options, labeling function, or predicate values

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY Procedure

Disables the enforcement of the policy for the specified table without changing the enforcement options, labeling function, or predicate values

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY Procedure

Reenables the current enforcement options, labeling function, and predicate for the tables in the specified schema by re-applying the RLS predicate and DML triggers

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY Procedure

Reenables the current enforcement options, labeling function, and predicate for the specified table by reapplying the RLS predicate and DML triggers

SA_POLICY_ADMIN.POLICY_SUBSCRIBE Procedure

For an Oracle Internet Directory configuration, subscribes to the policy for usage in APPLY_TABLE_POLICY and APPLY_SCHEMA_POLICY

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE Procedure

For an Oracle Internet Directory, unsubscribes from the policy for usage in APPLY_TABLE_POLICY and APPLY_SCHEMA_POLICY

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY Procedure

Removes the specified policy from a schema

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY Procedure

Removes the specified policy from a table

SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY Procedure

The SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY procedure changes the default enforcement options for the policy. Any new tables created in the schema will automatically have the new enforcement options applied. The existing tables in the schema are not affected.

To change enforcement options on a table (rather than a schema), you must first drop the policy from the table, make the change, and then reapply the policy.

If you alter the enforcement options on a schema, then this will take effect the next time a table is created in the schema. As a result, different tables within a schema may have different policy enforcement options in force.

Syntax

SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY (
  policy_name         IN VARCHAR2,
  schema_name         IN VARCHAR2,
  default_options     IN VARCHAR2);

Parameters

Table E-25 SA_POLICY_ADMIN.ALTER_SCHEMA Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table. To find existing schemas associated with this policy, query the POLICY_NAME and SCHEMA_NAME columns of the ALL_SA_TABLE_POLICIES view.

default_options

The default options to be used for new tables in the schema. Separate each option with a comma.

See Table 8-2 for a listing of the default enforcement options.

Examples

The following example adds the UPDATE_CONTROL default option to the HR schema.

BEGIN
 SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY(
  policy_name      => 'hr_ols_pol',
  schema_name      => 'HR',
  default_options  => 'read_control, write_control, update_control');
END;
/

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure

The SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY procedure applies the specified policy to all of the existing tables in a schema (that is, to those which do not already have the policy applied) and enables the policy for these tables. Then, whenever a new table is created in the schema, the policy is automatically applied to that table, using the schema's default options. No changes are made to existing tables in the schema that already have the policy applied.

Syntax

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY (
  policy_name        IN VARCHAR2,
  schema_name        IN VARCHAR2,
  default_options    IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-26 SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table to protect

default_options

The default options to be used for tables in the schema. Separate each option with a comma. If the default_options parameter is NULL, then the policy's default options will be used to apply the policy to the tables in the schema.

See Table 8-2 for a listing of the default enforcement options.

Example

The following example applies the READ_CONTROL and WRITE_CONTROL options to the HR schema.

BEGIN
 SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY(
  policy_name      => 'hr_ols_pol',
  schema_name      => 'HR',
  default_options  => 'read_control, write_control');
END;
/

SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure

The SA_POLICY_ADMIN.APPLY_TABLE_POLICY procedure adds the specified policy to a table. A policy label column is added to the table if it does not exist, and is set to NULL. When a policy is applied, it is automatically enabled. To change the table options, labeling function, or predicate, you must first remove the policy, and then reapply it.

Syntax

SA_POLICY_ADMIN.APPLY_TABLE_POLICY (
  policy_name       IN VARCHAR2,
  schema_name       IN VARCHAR2,
  table_name        IN VARCHAR2,
  table_options     IN VARCHAR2 DEFAULT NULL,
  label_function    IN VARCHAR2 DEFAULT NULL,
  predicate         IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-27 SA_POLICY_ADMIN.APPLY_TABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table that the policy protects

table_name

The table to be protected by the policy

table_options

A comma-delimited list of policy enforcement options to be used for the table. If NULL, then the policy's default options are used.

See Table 8-2 for a listing of the default enforcement options.

label_function

A string calling a function to return a label value to use as the default. For example, my_label(:new.dept,:new.status) computes the label based on the new values of the DEPT and STATUS columns in the row.

predicate

An additional predicate to combine (using AND or OR) with the label-based predicate for READ_CONTROL

Example

The following statement applies the hr_ols_pol policy to the EMPLOYEES table in the HR schema.

BEGIN
 SA_POLICY_ADMIN.APPLY_TABLE_POLICY(
  policy_name    => 'hr_ols_pol',
  schema_name    => 'HR',
  table_name     => 'EMPLOYEES',
  table_options  => NULL,
  label_function => 'hs(:new.dept,:new.status)',
  predicate      => 'no_control');
END;
/

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY Procedure

The SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY procedure disables the enforcement of the policy for all of the tables in the specified schema, without changing the enforcement options, labeling function, or predicate values. It removes the row level security predicate and DML triggers from all the tables in the schema.

Syntax

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY (
  policy_name    IN VARCHAR2,
  schema_name    IN VARCHAR2);

Parameters

Table E-28 SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table for this policy. To find this schema, query the POLICY_NAME and SCHEMA_NAME columns of the ALL_SA_TABLE_POLICIES view.

Example

The following example disables the hr_ols_pol policy for the HR schema.

BEGIN
 SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY(
  policy_name      => 'hr_ols_pol',
  schema_name      => 'HR');
END;
/

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY Procedure

The SA_POLICY_ADMIN.DISABLE_TABLE_POLICY procedure disables the enforcement of the policy for the specified table without changing the enforcement options, labeling function, or predicate values. It removes the row level security predicate and DML triggers from the table.

Syntax

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY (
  policy_name      IN VARCHAR2,
  schema_name      IN VARCHAR2,
  table_name       IN VARCHAR2);

Parameters

Table E-29 SA_POLICY_ADMIN.DISABLE_TABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table. To find this schema, query the POLICY_NAME and SCHEMA_NAME columns of the ALL_SA_TABLE_POLICIES view.

table_name

The table in the schema specified by schema_name. To find this table, query the POLICY_NAME, SCHEMA_NAME, and TABLE_NAME columns of the ALL_SA_TABLE_POLICIES view.

Example

The following statement disables the hr_ols_pos policy on the EMPLOYEES table in the HR schema:

BEGIN
 SA_POLICY_ADMIN.DISABLE_TABLE_POLICY(
  policy_name   => 'hr_ols_pol',
  schema_name   => 'HR',
  table_name    => 'EMPLOYEES');
END;
/

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY Procedure

The SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY procedure reenables the current enforcement options, labeling function, and predicate for the tables in the specified schema by re-applying the row level security predicate and DML triggers. The result is similar to enabling a policy for a table, but it covers all the tables in the schema.

Syntax

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY (
  policy_name    IN VARCHAR2,
  schema_name    IN VARCHAR2);

Parameters

Table E-30 SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies and their status, query the POLICY_NAME and STATUS columns of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table. To find this schema, query the POLICY_NAME and SCHEMA_NAME columns of the ALL_SA_TABLE_POLICIES view.

Example

The following example enables the hr_ols_pol policy for the HR schema.

BEGIN
 SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY(
  policy_name      => 'hr_ols_pol',
  schema_name      => 'HR');
END;
/

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY Procedure

The SA_POLICY_ADMIN.ENABLE_TABLE_POLICY procedure reenables the current enforcement options, labeling function, and predicate for the specified table by reapplying the row level security predicate and DML triggers.

Syntax

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY (
  policy_name     IN VARCHAR2,
  schema_name     IN VARCHAR2,
  table_name      IN VARCHAR2);

Parameters

Table E-31 SA_POLICY_ADMIN.ENABLE_TABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. POLICY_NAME and STATUS columns of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table. To find this schema, query the POLICY_NAME and SCHEMA_NAME columns of the ALL_SA_TABLE_POLICIES view.

table_name

The table in the schema specified by schema_name. To find this table, query the POLICY_NAME, SCHEMA_NAME, and TABLE_NAME columns of the ALL_SA_TABLE_POLICIES view.

Example

The following statement reenables the hr_ols_pol policy on the EMPLOYEES table in the HR schema:

BEGIN
 SA_POLICY_ADMIN.ENABLE_TABLE_POLICY(
  policy_name   => 'hr_ols_pol',
  schema_name   => 'HR',
  table_name    => 'EMPLOYEES');
END;
/

SA_POLICY_ADMIN.POLICY_SUBSCRIBE Procedure

In an Oracle Internet Directory-enabled Oracle Label Security configuration, the SA_POLICY_ADMIN.POLICY_SUBSCRIBE procedure subscribes to the policy for usage in SA_POLICY_ADMIN.APPLY_TABLE_POLICY and SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY. You must call this procedure for a policy before that policy can be applied to a table or schema. Subscribing is needed only once, not for each use of the policy in a table or schema.

You cannot drop any subscribed policy unless it has been removed from any table or schema to which it was applied, and then unsubscribed.

Syntax

SA_POLICY.POLICY_SUBSCRIBE(
  policy_name     IN VARCHAR2);

Parameter

Table E-32 SA_POLICY_ADMIN.POLICY_SUBSCRIBE Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Note:

This procedure must be used before policy usage only in the case of Oracle Internet Directory-enabled Oracle Label Security configuration. In the standalone Oracle Label Security case, the policy can be used in APPLY_TABLE_POLICY and APPLY_SCHEMA_POLICY directly without the need to subscribe.

Example

The following statement subscribes the database to the hr_ols_pol policy so that it can used by applying on tables and schema.

BEGIN
 SA_POLICY_ADMIN.POLICY_SUBSCRIBE(
  policy_name   => 'hr_ols_pol');
END;
/

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE Procedure

In an Oracle Internet Directory enabled Oracle Label Security configuration, the SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE procedure unsubscribes to the policy. You can use this procedure only if the policy is not in use; that is, it has not been applied to any table or schema. (If it has been applied to tables or schemas, then it must be removed from all of them before it can be unsubscribed.) A policy can be dropped in Oracle Internet Directory only if is not subscribed in any of the databases that have registered with that Oracle Internet Directory. (See "Drop a Policy" for more information.)

You cannot drop any subscribed policy unless it has been removed from any table or schema to which it was applied, and then unsubscribed.

Syntax

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE(
  policy_name  IN VARCHAR2);

Parameter

Table E-33 SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following statement unsubscribes the database to the hr_ols_pol policy.

BEGIN
 SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE(
  policy_name   => 'hr_ols_pol');
END;
/

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY Procedure

The SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY procedure removes the specified policy from a schema. The policy will be removed from all the tables in the schema and, optionally, the label column for the policy will be dropped from all the tables.

Syntax

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY (
  policy_name     IN VARCHAR2,
  schema_name     IN VARCHAR2,
  drop_column     IN BOOLEAN DEFAULT FALSE);

Parameters

Table E-34 SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table associated with this policy. To find this schema, query the SCHEMA_NAME of the ALL_SA_SCHEMA_POLICIES view.

drop_column

If TRUE, then the policy's column will be dropped from the tables, otherwise, the column will remain.

Example

The following example drops the human_resource policy's column from the HR schema.

BEGIN
 SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY(
  policy_name      => 'hr_ols_pol',
  schema_name      => 'HR',
  drop_column      => TRUE);
END;
/

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY Procedure

The SA_POLICY_ADMIN.REMOVE_TABLE_POLICY procedure removes the specified policy from a table. The policy predicate and any DML triggers will be removed from the table, and the policy label column can optionally be dropped. Policies can be removed from tables belonging to a schema that is protected by the policy.

Syntax

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY (
policy_name        IN VARCHAR2,
schema_name        IN VARCHAR2,
table_name         IN VARCHAR2,
drop_column        IN BOOLEAN DEFAULT FALSE);

Parameters

Table E-35 SA_POLICY_ADMIN.REMOVE_TABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The schema that contains the table associated with this policy. To find this schema, query the SCHEMA_NAME of the ALL_SA_SCHEMA_POLICIES view.

table_name

The table in the schema specified by schema_name. To find this table query the POLICY_NAME, SCHEMA_NAME, and TABLE_NAME columns of the ALL_SA_TABLE_POLICIES view.

drop_column

Whether the column is to be dropped: if TRUE, then the policy's column will be dropped from the table, otherwise, it will remain

Example

The following statement removes the hr_ols_pol policy from the EMPLOYEES table in the HR schema:

BEGIN
 SA_POLICY_ADMIN.REMOVE_TABLE_POLICY(
  policy_name    => 'hr_ols_pol',
  schema_name    => 'HR',
  table_name     => 'EMPLOYEES',
  drop_column    => TRUE);
END;
/

SA_SESSION Session Management PL/SQL Package

Users can change labels during a session within the authorizations set by the administrator. You do not need special privileges to use this package.

Table E-36 lists the SA_SESSION PL/SQL package procedures and functions.

Table E-36 SA_SESSSION PL/SQL Package Contents

Function
Description

SA_SESSION.COMP_READ Function

Returns a comma-delimited list of compartments that the user is authorized to read

SA_SESSION.COMP_WRITE Function

Returns a comma-delimited list of compartments that the user is authorized to write.

SA_SESSION.GROUP_READ Function

Returns a comma-delimited list of groups that the user is authorized to read

SA_SESSION.GROUP_WRITE Function

Returns a comma-delimited list of groups that the user is authorized to write.

SA_SESSION.LABEL Function

Returns the label that is associated with the specified Oracle Label Security policy

SA_SESSION.MAX_LEVEL Function

Returns the maximum Oracle Label Security level authorized for the session

SA_SESSION.MAX_READ_LABEL Function

Returns the label string that was used to initialize the user's maximum authorized read label

SA_SESSION.MAX_WRITE_LABEL Function

Returns the label string that was used to initialize the user's minimum authorized write label

SA_SESSION.MIN_LEVEL Function

Returns the minimum level authorized for the session

SA_SESSION.MIN_WRITE_LABEL Function

Returns the minimum write privileges for a label

SA_SESSION.PRIVS Function

Returns the set of current session privileges, in a comma-delimited list

SA_SESSION.RESTORE_DEFAULT_LABELS Procedure

Resets the current session label and row label to the stored default settings

SA_SESSION.ROW_LABEL Function

Returns the name of the row label that is associated with the policy for the current session.

SA_SESSION.SA_USER_NAME Function

Returns the user name associated with the current Oracle Label Security session

SA_SESSION.SAVE_DEFAULT_LABELS Procedure

Lets the user store the current session label and row label as the default for future sessions

SA_SESSION.SET_ACCESS_PROFILE Procedure

Sets the Oracle Label Security authorizations and privileges of the database session to those of the specified user

SA_SESSION.SET_LABEL Procedure

Sets a new level and new compartments and groups to which he or she has read access

SA_SESSION.SET_ROW_LABEL Procedure

Set the default row label that will be applied to new rows

See Also:

"SA_UTL PL/SQL Utility Functions and Procedures" for additional functions that return numeric label tags and BOOLEAN values

SA_SESSION.COMP_READ Function

The SA_SESSION.COMP_READ function returns a comma-delimited list of compartments that the user is authorized to read.

Syntax

SA_SESSION.COMP_READ (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-37 SA_SESSION.COMP_READ Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the compartments that the user can read for the hr_ols_pol policy.

SELECT SA_SESSION.COMP_READ ('hr_ols_pol') FROM DUAL;

SA_SESSION.COMP_WRITE Function

The SA_SESSION.COMP_WRITE function returns a comma-delimited list of compartments to which the user is authorized to write. This function is a subset of SA_SESSION.COMP_READ.

Syntax

SA_SESSION.COMP_WRITE (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-38 SA_SESSION.COMP_WRITE Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the compartments that the user can modify for the hr_ols_pol policy.

SELECT SA_SESSION.COMP_WRITE ('hr_ols_pol') FROM DUAL;

SA_SESSION.GROUP_READ Function

The SA_SESSION.GROUP_READ function returns a comma-delimited list of groups that the user is authorized to read.

Syntax

SA_SESSION.GROUP_READ (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-39 SA_SESSION.GROUP_READ Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the list of groups that a user can read for the hr_ols_pol policy.

SELECT SA_SESSION.GROUP_WRITE ('hr_ols_pol') FROM DUAL;

SA_SESSION.GROUP_WRITE Function

The SA_SESSION.GROUP_WRITE function returns a comma-delimited list of groups that the user is authorized to write. This function is a subset of SA_SESSION.GROUP_READ.

Syntax

SA_SESSION.GROUP_WRITE (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-40 SA_SESSION.GROUP_WRITE Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the groups the user is authorized to modify for the hr_ols_pol policy.

SELECT SA_SESSION.GROUP_WRITE ('hr_ols_pol') FROM DUAL;

SA_SESSION.LABEL Function

The SA_SESSION.LABEL function returns the label that is associated with the specified policy for the current session.

Syntax

SA_SESSION.LABEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-41 SA_SESSION.LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the label that is associated with the hr_ols_pol policy.

SELECT SA_SESSION.LABEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.MAX_LEVEL Function

The SA_SESSION.MAX_LEVEL function returns the maximum Oracle Label Security level authorized for the session.

Syntax

SA_SESSION.MAX_LEVEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-42 SA_SESSION.MAX_LEVEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the maximum Oracle Label Security level that is authorized for the hr_ols_pol policy.

SELECT SA_SESSION.MAX_LEVEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.MAX_READ_LABEL Function

The SA_SESSION.MAX_READ_LABEL function returns the label string that was used to initialize the user's maximum authorized read label. It is composed of the user's maximum level, compartments authorized for read access, and groups authorized for read access.

Syntax

SA_SESSION.MAX_READ_LABEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-43 SA_SESSION.MAX_READ_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the maximum read label privileges for the hr_ols_pol policy.

SELECT SA_SESSION.MAX_READ_LABEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.MAX_WRITE_LABEL Function

The SA_SESSION.MAX_WRITE_LABEL function returns the label string that was used to initialize the user's maximum authorized write label. It is composed of the user's maximum level, compartments authorized for write access, and groups authorized for write access.

Syntax

SA_SESSION.MAX_WRITE_LABEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-44 SA_SESSION.MAX_WRITE_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the maximum write label privileges for the hr_ols_pol policy.

SELECT SA_SESSION.MAX_WRITE_LABEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.MIN_LEVEL Function

The SA_SESSION.MIN_LEVEL function returns the minimum Oracle Label Security level authorized for the session.

Syntax

SA_SESSION.MIN_LEVEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-45 SA_SESSION.MIN_LEVEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the current minimum level for the hr_ols_pol policy.

SELECT SA_SESSION.MIN_LEVEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.MIN_WRITE_LABEL Function

The SA_SESSION.MIN_WRITE_LABEL function retrieves the label string that was used to initialize the user's minimum authorized write label. It contains only the level, with no compartments or groups.

Syntax

SA_SESSION.MIN_WRITE_LABEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-46 SA_SESSION.MIN_WRITE_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the maximum write label privileges for the hr_ols_pol policy.

SELECT SA_SESSION.MIN_WRITE_LABEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.PRIVS Function

The SA_SESSION.PRIVS function returns the set of current session privileges, in a comma-delimited list.

Syntax

SA_SESSION.PRIVS (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-47 SA_SESSION.Privs Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the current session privileges for the hr_ols_pol policy.

SELECT SA_SESSION.PRIVS ('hr_ols_pol') FROM DUAL;

SA_SESSION.RESTORE_DEFAULT_LABELS Procedure

The SA_SESSION.RESTORE_DEFAULT_LABELS procedure restores the session label and row label to those stored in the data dictionary. This command is useful to reset values after a SA_SESSION.SET_LABEL command has been processed.

Syntax

SA_SESSION.RESTORE_DEFAULT_LABELS (
 policy_name in VARCHAR2);

Parameter

Table E-48 SA_SESSION.RESTORE_DEFAULT_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example restores the default labels for the hr_ols_pol policy.

BEGIN
 SA_SESSION.RESTORE_DEFAULT_LABELS (
  policy_name         => 'hr_ols_pol');
END;
/

SA_SESSION.ROW_LABEL Function

The SA_SESSION.ROW_LABEL function returns the name of the row label that is associated with the policy for the current session.

Syntax

SA_SESSION.ROW_LABEL (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-49 SA_SESSION.ROW_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns the row label that is associated with the hr_ols_pol policy.

SELECT SA_SESSION.ROW_LABEL ('hr_ols_pol') FROM DUAL;

SA_SESSION.SET_LABEL Procedure

Use the SA_SESSION.SET_LABEL procedure to set the label of the current database session.

You can set the session label to:

Any level equal to or less than the maximum, and equal to or greater than the minimum level

Include any compartments in the authorized compartment list

Include any groups in the authorized group list. (Subgroups of authorized groups are implicitly included in the authorized list.)

Note that if you change the session label, this change may affect the value of the session's row label. The session's row label contains the subset of compartments and groups for which the user has write access. This may or may not be equivalent to the session label. For example, if you use the SA_SESSION.SET_LABEL procedure to set your current session label to C:A,B:US and you have write access only on the A compartment, then your row label would be set to C:A.

Syntax

SA_SESSION.SET_LABEL (
 policy_name IN VARCHAR2,
 label       IN VARCHAR2);

Parameters

Table E-50 SA_SESSION.SET_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The value to set as the label

Example

The following example sets the label for the hr_ols_pol policy.

BEGIN
 SA_SESSION.SET_LABEL (
  policy_name         => 'hr_ols_pol',
  label               => 'C:A,B:US');
END;
/

See Also:

"SA_USER_ADMIN.SET_DEFAULT_LABEL Procedure"

SA_SESSION.SA_USER_NAME Function

The SA_SESSION.SA_USER_NAME function returns the name of the current Oracle Label Security user, as set by the SA_SESSION.SET_ACCESS_PROFILE procedure (or as established at login). This is how you can determine the identity of the current user in relation to Oracle Label Security, rather than in relation to your Oracle login name.

Syntax

SA_SESSION.SA_USER_NAME (
  policy_name IN VARCHAR2)
RETURN VARCHAR2;

Parameter

Table E-51 SA_SESSION.SA_USER_NAME Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example finds the name of the Oracle Label Security user for the hr_ols_pol policy.

SELECT SA_SESSION.SA_USER_NAME ('hr_ols_pol') FROM DUAL;

SA_SESSION.SAVE_DEFAULT_LABELS Procedure

The SA_SESSION.SAVE_DEFAULT_LABELS procedure stores the current session label and row label as your initial session label and default row label. It permits you to change your defaults to reflect your current session label and row label. The saved labels will be used as the initial default settings for future sessions.

When you log in to a database, your default session label and row label are used to initialize the session label and row label. When the administrator originally authorized your Oracle Label Security labels, he or she also defined your default level, default compartments, and default groups. If you change your session label and row label, and want to save these values as the default labels, you can use the SA_SESSION.SAVE_DEFAULT_LABELS procedure.

This procedure is useful if you have multiple sessions and want to be sure that all additional sessions have the same labels. You can save the current labels as the default, and all future sessions will have these as the initial labels.

Consider a situation in which you connect to the database through Oracle Forms and want to run a report. By saving the current session labels as the default before you call Oracle Reports, you ensure that Oracle Reports will initialize at the same labels as are being used by Oracle Forms.

Syntax

SA_SESSION.SAVE_DEFAULT_LABELS (
  policy_name IN VARCHAR2);

Parameter

Table E-52 SA_SESSION.SAVE_DEFAULT_LABELS Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example saves the label defaults for the hr_ols_pol policy.

BEGIN
 SA_SESSION.SAVE_DEFAULT_LABELS (
  policy_name       => 'hr_ols_pol');
END;
/

Note:

The SA_SESSION.SAVE_DEFAULT_LABELS procedure overrides the settings established by the administrator.

SA_SESSION.SET_ACCESS_PROFILE Procedure

The SA_SESSION.SET_ACCESS_PROFILE procedure sets the Oracle Label Security authorizations and privileges of the database session to those of the specified user. (Note that the originating user retains the PROFILE_ACCESS privilege.)

The user executing the SA_SESSION.SET_ACCESS_PROFILE procedure must have the PROFILE_ACCESS privilege. Note that the logged-in database user (the Oracle user ID) does not change. That user assumes only the authorizations and privileges of the specified user. By contrast, the Oracle Label Security user name is changed.

This administrative procedure is useful for various tasks:

With SA_SESSION.SET_ACCESS_PROFILE, you can see the result of the authorization and privilege settings for a particular user.

Applications need to have proxy accounts connect as (and assume the identity of) application users, for purposes of accessing labeled data. With the SA_SESSION.SET_ACCESS_PROFILE privilege, the proxy account can act on behalf of the application users.

Syntax

SA_SESSION.SET_ACCESS_PROFILE (
  policy_name IN VARCHAR2
  user_name   IN VARCHAR2);

Parameters

Table E-53 SA_SESSION.SET_ACCESS_PROFILE Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Name of the user whose authorizations and privileges should be assumed (typically, the user associated with this policy). To find this user, query the USER_NAME and POLICY_NAME columns of the DBA_SA_USERS view.

Example

The following example enables user psmith to have Oracle Label Security authorizations and privileges for the database session.

BEGIN
 SA_SESSION.SET_ACCESS_PROFILE (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jjones');
END;
/

SA_SESSION.SET_ROW_LABEL Procedure

Use the SA_SESSION.SET_ROW_LABEL procedure to set the default row label value for the current database session. The compartments and groups in the label must be a subset of the compartments and groups in the session label to which the user has write access. When the LABEL_DEFAULT option is set, this row label value is used on insert if the user does not explicitly specify the label.

If the SA_SESSION.SET_ROW_LABEL procedure is not used to set the default row label value, then this value is automatically derived from the session label. It contains the level of the session label and the subset of the compartments and groups in the session label for which the user has write authorization.

The row label is automatically reset if the session label changes. For example, if you change your session level from HIGHLY_SENSITIVE to SENSITIVE, then the level component of the row label automatically changes to SENSITIVE.

The user can set the row label independently, but only to include:

A level that is less than or equal to the level of the session label, and greater than or equal to the user's minimum level

A subset of the compartments and groups from the session label, for which the user is authorized to have write access

If the user tries to set the row label to an invalid value, then the operation is not permitted and the row label value is unchanged.

Syntax

SA_SESSION.SET_ROW_LABEL (
 policy_name   IN VARCHAR2,
 row_label     IN VARCHAR2);

Parameters

Table E-54 SA_SESSION.SET_ROW_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The value to set as the default row label

Example

The following example sets the row label for the hr_ols_pol policy.

BEGIN
 SA_SESSION.SET_ROW_LABEL (
  policy_name     => 'hr_ols_pol',
  label           => 'HR');
END;
/

See Also:

"SA_USER_ADMIN.SET_ROW_LABEL Procedure"

SA_SYSDBA Policy Management PL/SQL Package

Table E-55 lists the procedures of the SA_SYSDBA package, which you can use to manage Oracle Label Security policies. To use this package, you must be granted the LBAC_DBA role and the EXECUTE privilege on the SA_SYSDBA package.

Table E-55 SA_SYSDBA PL/SQL Package Contents

Procedure
Description

SA_SYSDBA.ALTER_POLICY Procedure

Modifies an Oracle Label Security policy

SA_SYSDBA.CREATE_POLICY Procedure

Creates an Oracle Label Security policy

SA_SYSDBA.DISABLE_POLICY Procedure

Disables an Oracle Label Security policy

SA_SYSDBA.DROP_POLICY Procedure

Drops an Oracle Label Security policy

SA_SYSDBA.ENABLE_POLICY Procedure

Enables an Oracle Label Security policy

See Also:

"Step 1: Create the Label Security Policy Container"

"Organizing the Duties of Oracle Label Security Administrators"

SA_SYSDBA.ALTER_POLICY Procedure

Use the SA_SYSDBA.ALTER_POLICY procedure to set and modify column names associated with the policy.

SA_SYSDBA.ALTER_POLICY can only be used to change column name for policies that are not applied on any user tables or schemas. Otherwise, this error appears:

12474, 00000, "cannot change column name for a policy in use"

Syntax

SA_SYSDBA.ALTER_POLICY (
   policy_name       IN  VARCHAR2,
   default_options   IN  VARCHAR2 DEFAULT NULL,
   column_name       IN  VARCHAR2 DEFAULT NULL);

Parameters

Table E-56 SA_SYSDBA.ALTER_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

default_options

Specifies the default enforcement options to be used when the policy is applied and no table- or schema-specific options are specified. Includes enforcement options and the option to hide the label column. Separate each option with a comma.

See Table 8-2 for a listing of the default enforcement options.

column_name

Specifies the column name associated with the policy. To find this column name, query the COLUMN_NAME column of the ALL_SA_POLICIES view.

Example

The following example updates the hr_ols_pol policy to use a different set of default options. Because the name of the column does not need to change, the column_name parameter is omitted.

BEGIN
 SA_SYSDBA.ALTER_POLICY (
  policy_name      => 'hr_ols_pol',
  default_options  => 'read_control, delete_control');
END;
/

SA_SYSDBA.CREATE_POLICY Procedure

Use the SA_SYSDBA.CREATE_POLICY procedure to create a new Oracle Label Security policy, define a policy-specific column name, and specify a set of default policy options. After you create the policy, a role for it is created and granted to you. The format of the role name is policy_DBA (for example, my_ols_pol_DBA).

Syntax

SA_SYSDBA.CREATE_POLICY (
   policy_name       IN VARCHAR2,
   column_name       IN VARCHAR2 DEFAULT NULL,
   default_options   IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-57 SA_SYSDBA.CREATE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy name, which must be unique within the database. It can have a maximum of 30 characters, but only the first 26 characters in the policy_name are significant. Two policies may not have the same first 26 characters in the policy_name.

To find a list of existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

column_name

Specifies the name of the column to be added to tables protected by the policy. If NULL, then the name policy_name_COL is used. Two Oracle Label Security policies cannot share the same column name.

default_options

Specifies the default options to be used when the policy is applied and no table- or schema-specific options are specified. Includes enforcement options and the option to hide the label column. Separate each option with a comma.

See Table 8-2 for a listing of the default enforcement options.

Example

The following example creates a policy container whose default options are READ_CONTROL and WRITE_CONTROL. The WRITE_CONTROL option encompasses the INSERT_CONTROL, UPDATE_CONTROL, and DELETE_CONTROL options.

BEGIN
 SA_SYSDBA.CREATE_POLICY (
  policy_name      => 'hr_ols_pol',
  column_name      => 'ols_col',
  default_options  => 'read_control, write_control');
END;
/

See Also:

Regarding policy enforcement options for tables: "SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure"

Regarding HIDE, "Choosing Policy Options" and "The HIDE Policy Column Option".

"SA_SYSDBA.CREATE_POLICY with Inverse Groups"

"Organizing the Duties of Oracle Label Security Administrators" for information about the policy_DBA role

SA_SYSDBA.DISABLE_POLICY Procedure

Use the SA_SYSDBA.DISABLE_POLICY procedure to turn off enforcement of a policy, without removing it from the database. The policy is not enforced for all subsequent access to the database.

To disable a policy means that no access control is enforced on the tables and schemas protected by the policy. The administrator can continue to perform administrative operations while the policy is disabled.

Note:

This feature is extremely powerful, and should be used with caution. When a policy is disabled, anyone who connects to the database can access all the data normally protected by the policy. So, your site should establish guidelines for use of this feature.

Normally, a policy should not be disabled in order to manage data. At times, however, an administrator may need to disable a policy to perform application debugging tasks. In this case, the database should be run in single-user mode. In a development environment, for example, you may need to observe data processing operations without the policy turned on. When you reenable the policy, all of the selected enforcement options become effective again.

Syntax

SA_SYSDBA.DISABLE_POLICY (
 policy_name IN VARCHAR2);

Parameters

Table E-58 SA_SYSDBA.DISABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies and their status, query the POLICY_NAME and STATUS columns of the ALL_SA_POLICIES data dictionary view.

Example

The following example disables the hr_ols_pol policy:

EXEC SA_SYSDBA.DISABLE_POLICY ('hr_ols_pol');

SA_SYSDBA.DROP_POLICY Procedure

Use the SA_SYSDBA.DROP_POLICY procedure to delete the policy and all of its associated user labels and data labels from the database. It purges the policy and these associations from the system entirely. You can optionally drop the label column from all tables controlled by the policy. The policy does not need to be disabled before you drop it.

Syntax

SA_SYSDBA.DROP_POLICY (
   policy_name IN VARCHAR2,
   drop_column  BOOLEAN DEFAULT FALSE);

Parameters

Table E-59 SA_SYSDBA.DROP_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy to be dropped. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

drop_column

Indicates that the policy column should be dropped from protected tables (TRUE)

Example

The following example deletes the hr_ols_pol policy.

EXEC SA_SYSDBA.DROP_POLICY ('hr_ols_pol');

SA_SYSDBA.ENABLE_POLICY Procedure

Use the SA_SYSDBA.ENABLE_POLICY procedure to enforce access control on the tables and schemas protected by the policy. A policy is automatically enabled when it is created. After creation or enablement, the policy is enforced for all subsequent access to tables protected by the policy.

Syntax

SA_SYSDBA.ENABLE_POLICY (policy_name IN VARCHAR2);

Parameters

Table E-60 SA_SYSDBA.ENABLE_POLICY Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies and their status, query the POLICY_NAME and STATUS columns of the ALL_SA_POLICIES data dictionary view.

Example

The following example enables the hr_ols_pol policy.

EXEC SA_SYSDBA.ENABLE_POLICY('hr_ols_pol');

SA_USER_ADMIN User, Levels, Groups, and Compartments PL/SQL Package

Table E-61 lists the SA_USER_ADMIN PL/SQL package procedures, which enable you to manage user labels by label component. To use this package, you must be granted the policy_DBA role (for example, HR_OLS_POL_DBA for a role for the hr_ols_pol policy) and the EXECUTE privilege on the SA_USER_ADMIN package.

Table E-61 SA_USER_ADMIN PL/SQL Package Contents

Procedure or Function
Description

SA_USER_ADMIN.ADD_COMPARTMENTS Procedure

Adds compartments to a user's authorizations, indicating whether the compartments are authorized for write as well as read

SA_USER_ADMIN.ADD_GROUPS Procedure

Adds groups to a user, indicating whether the groups are authorized for write as well as read

SA_USER_ADMIN.ALTER_COMPARTMENTS Procedure

Changes the write access, the default label indicator, and the row label indicator for each of the compartments in the list

SA_USER_ADMIN.ALTER_GROUPS Procedure

Changes the write access, the default label indicator, and the row label indicator for each of the groups in the list

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS Procedure

Drops all compartments from a user's authorizations

SA_USER_ADMIN.DROP_ALL_GROUPS Procedure

Drops all groups from a user's authorizations

SA_USER_ADMIN.DROP_COMPARTMENTS Procedure

Drops the specified compartments from a user's authorizations

SA_USER_ADMIN.DROP_GROUPS Procedure

Drops the specified groups from a user's authorizations

SA_USER_ADMIN.DROP_USER_ACCESS Procedure

Removes all Oracle Label Security authorizations and privileges from the specified user

SA_USER_ADMIN.SET_COMPARTMENTS Procedure

Assigns compartments to a user and identifies default values for the user's session label and row label

SA_USER_ADMIN.SET_DEFAULT_LABEL Procedure

Sets the user's initial session label to the one specified

SA_USER_ADMIN.SET_GROUPS Procedure

Assigns groups to a user and identifies default values for the user's session label and row label

SA_USER_ADMIN.SET_LEVELS Procedure

Assigns minimum and maximum levels to a user and identifies default values for the user's session label and row label

SA_USER_ADMIN.SET_PROG_PRIVS Procedure

Sets policy-specific privileges for program units

SA_USER_ADMIN.SET_ROW_LABEL Procedure

Sets the user's initial row label to the one specified

SA_USER_ADMIN.SET_USER_LABELS Procedure

Sets the user's levels, compartments, and groups using a set of labels, instead of the individual components

SA_USER_ADMIN.SET_USER_PRIVS Procedure

Sets policy-specific privileges for users

SA_USER_ADMIN.ADD_COMPARTMENTS Procedure

The SA_USER_ADMIN.ADD_COMPARTMENTS procedure adds (assign) compartments to a user's authorizations, indicating whether the compartments are authorized for write and read privileges. This procedure is useful if you have already used the SA_USER_ADMIN.SET_COMPARTMENTS procedure for the user but then decide that you want to grant this user authorization for additional compartments, or to update the current set of compartments. You also can use it in place of SA_USER_ADMIN.SET_COMPARTMENTS.

Syntax

SA_USER_ADMIN.ADD_COMPARTMENTS (
policy_name    IN VARCHAR2,
user_name      IN VARCHAR2,
comps          IN VARCHAR2,
access_mode    IN VARCHAR2 DEFAULT NULL,
in_def         IN VARCHAR2 DEFAULT NULL,
in_row         IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-62 SA_USER_ADMIN.ADD_COMPARTMENTS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. This user can be either a new user or a user who has already been authorized for this policy's compartments. To find an existing user, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS view.

comps

A comma-delimited list of compartments to add, by short name only. To find existing compartments, query the SHORT_NAME column of the ALL_SA_COMPARTMENTS view.

access_mode

One of two public variables that contain string values that can specify the type of access authorized. The variable names, values, and meaning are as follows:

SA_UTL.READ_ONLY indicates no write access

SA_UTL.READ_WRITE indicates that write is authorized

If access_mode is NULL, then it is set to SA_UTL.READ_ONLY.

in_def

Specifies whether these compartments should be in the default compartments (Y/N)

If in_def is NULL, then it is set to Y.

in_row

Specifies whether these compartments should be in the row label (Y/N)

If in_row is NULL, then it is set to N.

Example

The following example adds compartments to the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.ADD_COMPARTMENTS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  comps          => 'FIN',
  access_mode    => SA_UTL.READ_ONLY,
  in_def         => 'y',
  in_row         => 'y');
END;
/

SA_USER_ADMIN.ADD_GROUPS Procedure

The SA_USER_ADMIN.ADD_GROUPS procedure adds (assign) groups to a user, indicating whether the groups are authorized for write and read privileges. This procedure is useful if you have already used the SA_USER_ADMIN.SET_GROUPS procedure for the user but then decide that you want to grant this user authorization for additional groups or to update the current set of groups. You also can use it in place of SA_USER_ADMIN.SET_GROUPS.

Syntax

SA_USER_ADMIN.ADD_GROUPS (
  policy_name       IN VARCHAR2,
  user_name         IN VARCHAR2,
  groups            IN VARCHAR2,
  access_mode       IN VARCHAR2 DEFAULT NULL,
  in_def            IN VARCHAR2 DEFAULT NULL,
  in_row            IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-63 SA_USER_ADMIN.ADD_GROUPS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user. This user can be either a new user or a user who has already been authorized for this policy's groups. To find an existing user, query the USER_NAME column of the DBA_SA_USER_GROUPS view.

groups

A comma-delimited list of groups to add, by short name only. To find a list of existing groups, query the SHORT_NAME column of the ALL_SA_GROUPS view.

access_mode

One of two public variables that contain string values that can specify the type of access authorized. The variable names, values, and meaning are as follows:

SA_UTL.READ_ONLY indicates no write access

SA_UTL.READ_WRITE indicates that write is authorized

If access_mode is NULL, then access_mode is set to SA_UTL.READ_ONLY.

in_def

Specifies whether these groups should be in the default groups (Y/N)

If in_def is NULL, then it is set to Y.

in_row

Specifies whether these groups should be in the row label (Y/N)

If in_row is NULL, then it is set to N.

Example

The following example adds several groups to the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.ADD_GROUPS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  groups         => 'ER_FIN, SR_FIN, NR_FIN, WR_FIN',
  access_mode    => SA_UTL.READ_WRITE,
  in_def         => 'y',
  in_row         => 'y');
END;
/

SA_USER_ADMIN.ALTER_COMPARTMENTS Procedure

The SA_USER_ADMIN.ALTER_COMPARTMENTS procedure changes the write access, the default label indicator, and the row label indicator for each of the compartments in the list.

Syntax

SA_USER_ADMIN.ALTER_COMPARTMENTS (
  policy_name  IN VARCHAR2,
  user_name    IN VARCHAR2,
  comps        IN VARCHAR2,
  access_mode  IN VARCHAR2 DEFAULT NULL,
  in_def       IN VARCHAR2 DEFAULT NULL,
  in_row       IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-64 SA_USER_ADMIN.ALTER_COMPARTMENTS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the compartment. To find authorized users, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS view.

comps

A comma-delimited list of compartments to modify, using the short name only. To find existing compartments, query the SHORT_NAME column of the ALL_SA_COMPARTMENTS view.

access_mode

One of two public variables that contain string values that can specify the type of access authorized. The variable names, values, and meaning are as follows:

SA_UTL.READ_ONLY indicates no write access

SA_UTL.READ_WRITE indicates that write is authorized

If access_mode is NULL, then access_mode for the compartment is unaltered.

in_def

Specifies whether these compartments should be in the default compartments (Y/N)

If in_def is NULL, then in_def for the compartment is unaltered.

in_row

Specifies whether these compartments should be in the row label (Y/N)

If in_row is NULL, then in_row for the compartment is unaltered.

If in_def is N, then in_row cannot be Y. This is because the row label compartments must be a subset of the session label compartments.

Example

The following example modifies compartments for the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.ALTER_COMPARTMENTS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  comps          => 'FIN',
  access_mode    => SA_UTL.READ_ONLY,
  in_def         => 'y',
  in_row         => 'y');
END;
/

SA_USER_ADMIN.ALTER_GROUPS Procedure

The SA_USER_ADMIN.ALTER_GROUPS procedure changes the write access, the default label indicator, and the row label indicator for each of the groups in the list.

Syntax

SA_USER_ADMIN.ALTER_GROUPS (
  policy_name      IN VARCHAR2,
  user_name        IN VARCHAR2,
  groups           IN VARCHAR2,
  access_mode      IN VARCHAR2 DEFAULT NULL,
  in_def           IN VARCHAR2 DEFAULT NULL,
  in_row           IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-65 SA_USER_ADMIN.ALTER_GROUPS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the group. To find existing users, query the USER_NAME and GRP columns of the DBA_SA_USER_GROUPS view.

groups

A comma-delimited list of groups to alter, by short name only. To find existing groups, query the SHORT_NAME column of the ALL_SA_GROUPS view.

access_mode

Two public variables contain string values that can specify the type of access authorized. The variable names, values, and meaning are as follows:

SA_UTL.READ_ONLY indicates no write access

SA_UTL.READ_WRITE indicates that write is authorized

If access_mode is NULL, then access_mode for the group is unaltered.

in_def

Specifies whether these groups should be in the default groups (Y/N)

If in_def is NULL, then in_def for the group is unaltered.

in_row

Specifies whether these groups should be in the row label ((Y/N)

If in_row is NULL, then in_row for the group is unaltered.

If in_def is N, then in_row cannot be Y. This is because the row label groups must be a subset of the session label groups.

Example

The following example sets the access mode for the existing groups to be read only.

BEGIN
 SA_USER_ADMIN.ALTER_GROUPS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  groups         => 'ER',
  access_mode    => SA_UTL.READ_ONLY);
END;
/

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS Procedure

The SA_USER_ADMIN.DROP_ALL_COMPARTMENTS procedure drops all compartments from a user's authorizations.

Syntax

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS (
 policy_name  IN VARCHAR2,
 user_name    IN VARCHAR2);

Parameters

Table E-66 SA_USER_ADMIN.DROP_ALL_COMPARTMENTS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the compartment. To find existing users, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS view.

Example

The following example drops all compartments for the hr_ols_pol policy for user jjones.

BEGIN
 SA_USER_ADMIN.DROP_ALL_COMPARTMENTS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones');
END;
/

SA_USER_ADMIN.DROP_ALL_GROUPS Procedure

The SA_USER_ADMIN.DROP_ALL_GROUPS procedure drops all groups from a user's authorizations.

Syntax

SA_USER_ADMIN.DROP_ALL_GROUPS (
  policy_name IN VARCHAR2,
  user_name   IN VARCHAR2);

Parameters

Table E-67 SA_USER_ADMIN.DROP_ALL_GROUPS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the group. To find existing users, query the USER_NAME and GRP columns of the DBA_SA_USER_GROUPS view.

Example

The following example drops all groups from the hr_ols_pol policy for user jjones.

BEGIN
 SA_USER_ADMIN.DROP_ALL_GROUPS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones');
END;
/

SA_USER_ADMIN.DROP_COMPARTMENTS Procedure

The SA_USER_ADMIN.DROP_COMPARTMENTS procedure drops the specified compartments from a user's authorizations.

Syntax

SA_USER_ADMIN.DROP_COMPARTMENTS (
  policy_name     IN VARCHAR2,
  user_name       IN VARCHAR2,
  comps           IN VARCHAR2);

Parameters

Table E-68 SA_USER_ADMIN.DROP_COMPARTMENTS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the compartment. To find existing users, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS view.

comps

A comma-delimited list of compartments to drop. To find all comps for this policy, query the POLICY_NAME and COMP columns of the DBA_SA_USER_COMPARTMENTS view.

Example

The following example drops the FINANCIAL compartment from the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.DROP_COMPARTMENTS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  comps          => 'HR');
END;
/

SA_USER_ADMIN.DROP_GROUPS Procedure

The SA_USER_ADMIN.DROP_GROUPS procedure drops the specified groups from a user's authorizations.

Syntax

SA_USER_ADMIN.DROP_GROUPS (
  policy_name IN VARCHAR2,
  user_name   IN VARCHAR2,
  groups      IN VARCHAR2);

Parameters

Table E-69 SA_USER_ADMIN.DROP_GROUPS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized for the group. To find existing users, query the USER_NAME and GRP columns of the DBA_SA_USER_GROUPS view.

groups

A comma-delimited list of groups to drop, by short name only. To find a list of groups, query the SHORT_NAME column of the ALL_SA_GROUPS view.

Example

The following example drops the NR_FIN group from the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.DROP_GROUPS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  groups         => 'ER');
END;
/

SA_USER_ADMIN.DROP_USER_ACCESS Procedure

Use the SA_USER_ADMIN.DROP_USER_ACCESS procedure to remove all Oracle Label Security authorizations and privileges from the specified user.

Syntax

SA_USER_ADMIN.DROP_USER_ACCESS (
  policy_name      IN VARCHAR2,
  user_name        IN VARCHAR2);

Parameters

Table E-70 SA_USER_ADMIN.DROP_USER_ACCESS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. To find all users associated with this policy, query the USER_NAME and POLICY_NAME columns of the DBA_SA_USER_PRIVS view.

Examples

The following example removes user jjones's authorization for the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.DROP_USER_ACCESS (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jjones');
END;
/

SA_USER_ADMIN.SET_COMPARTMENTS Procedure

The SA_USER_ADMIN.SET_COMPARTMENTS procedure assigns compartments to a user and identifies default values for the user's session label and row label. After you have set the compartment, you can configure additional compartments by using the SA_USER_ADMIN.ADD_COMPARTMENTS procedure. (See "SA_USER_ADMIN.ADD_COMPARTMENTS Procedure".)

All users must have their levels set before their authorized compartments can be established.

The write compartments, if specified, must be a subset of the read compartments. (The write compartments are those to which the user should have write access.)

Syntax

SA_USER_ADMIN.SET_COMPARTMENTS (
  policy_name   IN VARCHAR2,
  user_name     IN VARCHAR2,
  read_comps    IN VARCHAR2,
  write_comps   IN VARCHAR2 DEFAULT NULL,
  def_comps     IN VARCHAR2 DEFAULT NULL,
  row_comps     IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-71 SA_USER_ADMIN.SET_COMPARTMENTS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name to assign compartments

read_comps

A comma-delimited list of compartments authorized for read access, by short name only

To find all compartments, query the SHORT_NAME column of the ALL_SA_COMPARTMENTS view.

write_comps

A comma-delimited list of compartments authorized for write access (subset of read_comps), by short name only. If write_comps are NULL, then they are set to the read_comps.

def_comps

Specifies the default compartments, by short name only. This must be a subset of read_comps. If the def_comps are NULL, then they are set to the read_comps.

row_comps

Specifies the row compartments, by short name only. This must be a subset of write_comps and def_comps. If the row_comps are NULL, then they are set to the components in def_comps that are authorized for write access.

Example

The following example sets compartments for the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.SET_COMPARTMENTS (
  policy_name   => 'hr_ols_pol',
  user_name     => 'jjones',
  read_comps    => 'FIN',
  write_comps   => 'FIN',
  def_comps     => 'FIN',
  row_comps     => 'FIN');
END;
/

SA_USER_ADMIN.SET_DEFAULT_LABEL Procedure

The SA_USER_ADMIN.SET_DEFAULT_LABEL procedure sets the user's initial session label to the one specified.

As long as the row label will still be dominated by the new write label, you can set the session label to:

Any level equal to or less than his maximum, and equal to or greater than his minimum label

Include any compartments in the authorized compartment list

Include any groups in the authorized group list. (Subgroups of authorized groups are implicitly included in the authorized list.)

The row label must be dominated by the new write label that will result from resetting the session label. If this condition is not true, then the SET_DEFAULT_LABEL procedure will fail.

For example, suppose the current row label is S:A,B, and that you have write access to both compartments. If you attempt to set the new default label to C:A,B, then the SET_LABEL procedure will fail. This is because the new write label would be C:A,B, which does not dominate the current row label.

To successfully reset the session label in this case, you must first lower the row label to a value that will be dominated by the resulting session label.

Syntax

SA_USER_ADMIN.SET_DEFAULT_LABELS (
  policy_name  IN VARCHAR2,
  user_name    IN VARCHAR2,
  def_label    IN VARCHAR2);

Parameters

Table E-72 SA_USER_ADMIN.SET_DEFAULT_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user who has been authorized with label components. To find this user, query the USER_NAME column of the ALL_SA_USER_LABELS view.

def_label

Specifies the label string to be used to initialize the user's default labels. This label may contain any compartments and groups that are authorized for read access. To find existing labels, query the LABEL column of the ALL_SA_LABELS view.

Example

The following example sets the default label for hr_ols_pol for user jjones.

BEGIN
 SA_USER_ADMIN.SET_DEFAULT_LABEL (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jjones',
  def_label         => 'HS');
END;
/

See Also:

"SA_SESSION Session Management PL/SQL Package"

"Session Labels and Inverse Groups"

SA_USER_ADMIN.SET_GROUPS Procedure

The SA_USER_ADMIN.SET_GROUPS procedure assigns groups to a user and identifies default values for the user's session label and row label. All users must have their levels set before their authorized groups can be established. You can find information about a user's level authorization by querying the DBA_SA_USER_LEVELS data dictionary view.

Syntax

SA_USER_ADMIN.SET_GROUPS (policy_name IN VARCHAR2,
  user_name        IN VARCHAR2,
  read_groups      IN VARCHAR2,
  write_groups     IN VARCHAR2 DEFAULT NULL,
  def_group        IN VARCHAR2 DEFAULT NULL,
  row_groups       IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-73 SA_USER_ADMIN.SET_GROUPS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. This user is a first-time user for group authorization, but the user must already be authorized for levels. To find users who have been authorized for levels, query the USER_NAME column of the DBA_SA_USER_LEVELS view.

read_groups

A comma-delimited list of groups authorized for read, by short name only.

To find existing groups, query the SHORT_NAME column of the ALL_SA_GROUPS view.

write_groups

A comma-delimited list of groups authorized for write, by short name only. This must be a subset of read_groups. If set to NULL, then this setting defaults to read_groups.

def_groups

Specifies the default groups, by short name only. This must be a subset of read_groups. If set to NULL, then this setting defaults to read_groups.

row_groups

Specifies the row groups, by short name only. This must be a subset of write_groups and def_groups. If set to NULL, then this setting defaults to the groups in def_groups that are authorized for write access.

Example

The following example defines groups for the hr_ols_pol policy.

BEGIN
 SA_USER_ADMIN.SET_GROUPS (
  policy_name    => 'hr_ols_pol',
  user_name      => 'jjones',
  read_groups    => 'ER_FIN',
  write_groups   => 'ER_FIN',
  def_groups     => 'ER_FIN',
  row_groups     => 'ER_FIN');
END;
/

SA_USER_ADMIN.SET_LEVELS Procedure

The SA_USER_ADMIN.SET_LEVELS procedure assigns a minimum and maximum level to a user and identifies default values for the user's session label and row label.

Syntax

SA_USER_ADMIN.SET_LEVELS (policy_name IN VARCHAR2,
   user_name        IN VARCHAR2,
   max_level        IN VARCHAR2,
   min_level        IN VARCHAR2 DEFAULT NULL,
   def_level        IN VARCHAR2 DEFAULT NULL,
   row_level        IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-74 SA_USER_ADMIN.SET_LEVELS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. This user does not need to have any Oracle Label Security authorizations before you run this procedure.

max_level

The highest level for read and write access, by short name only.

To find existing levels, query the SHORT_NAME column of the ALL_SA_LEVELS view.

min_level

The lowest level for write access, by short name only. If set to NULL, then the default is the lowest level for the policy.

def_level

Specifies the default level (equal to or greater than the minimum level, and equal to or less than the maximum level). Use the short name only. If set to NULL, then the default is the max_level.

row_level

Specifies the row level (equal to or greater than the minimum level, and equal to or less than the default level). Use the short name only. If set to NULL, then it is set to the def_level.

Example

The following example sets levels for the hr_ols_pol policy.

BEGIN
  SA_USER_ADMIN.SET_LEVELS (
   policy_name     => 'hr_ols_pol',
   user_name       => 'jjones',
   max_level       => 'PUB',
   min_level       => 'HS');
END;
/

SA_USER_ADMIN.SET_PROG_PRIVS Procedure

The SA_USER_ADMIN.SET_PROG_PRIVS procedure sets policy-specific privileges for program units. If the privileges parameter is NULL, then the program unit's privileges for the policy are removed.

To grant privileges to a stored program unit, you must have the policy_DBA role, and the EXECUTE permission on the SA_USER_ADMIN.SA_USER_ADMIN package. You can use either the SA_USER_ADMIN package or Oracle Enterprise Manager to manage Oracle Label Security privileges.

Syntax

SA_USER_ADMIN.SET_PROG_PRIVS (
  policy_name           IN VARCHAR2,
  schema_name           IN VARCHAR2,
  program_unit_name     IN VARCHAR2,
  privileges            IN VARCHAR2);

Parameters

Table E-75 SA_SESSION.SET_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

schema_name

The name of the schema that contains the program unit

program_unit_name

Specifies the program unit to be granted privileges

privileges

A comma-delimited character string of policy-specific privileges. If you set privileges to NULL, then the program unit's privileges for the policy are removed.

See "About Granting Privileges to Users and Trusted Program Units for the Policy" for list of available privileges to grant.

Example

The following example gives the READ privilege to the SUM_PURCHASES function (described in "Trusted Stored Program Unit Example"):

BEGIN
 SA_USER_ADMIN.SET_PROG_PRIVS (
  policy_name         => 'hr_ols_pol',
  schema_name         => 'HR',
  program_unit_name   => 'check_emp_hours',
  privileges          => 'READ');
END;
/

When the check_emp_hours procedure is then called, it runs with the READ privilege as well as the current user's Oracle Label Security privileges. Using this technique, the user can be allowed to find the value of the total employee hours that were logged, without learning what hours any individual employee logged.

SA_USER_ADMIN.SET_ROW_LABEL Procedure

Use the SA_USER_ADMIN.SET_ROW_LABEL procedure to set the user's initial row label to the one specified.

The user can set the row label independently, but only to:

A level that is less than or equal to the level of the session label, and greater than or equal to the user's minimum level

Include a subset of the compartments and groups from the session label, for which the user is authorized to have write access

If you try to set the row label to an invalid value, then the operation is disallowed, and the row label value is unchanged.

Syntax

SA_USER_ADMIN.SET_ROW_LABEL (
  policy_name   IN VARCHAR2,
  user_name     IN VARCHAR2,
  row_label     IN VARCHAR2);

Parameters

Table E-76 SA_USER_ADMIN.SET_ROW_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. This user must have the sufficient compartment, group, and level authorizations. To find this user, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS, DBA_SA_USER_GROUPS, and DBA_SA_USER_LEVELS views.

row_label

Specifies the label string to be used to initialize the user's row label. The label must contain only those compartments and groups from the default label that are authorized for write access. To find existing compartments and groups, query the ALL_SA_COMPARTMENTS and ALL_SA_GROUPS views.

Example

The following example sets the row label for the hr_ols_pol policy for user jjones.

BEGIN
 SA_USER_ADMIN.SET_ROW_LABEL (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jjones',
  row_label         => 'HS');
END;
/

See Also:

"SA_SESSION.SET_ROW_LABEL Procedure"

SA_USER_ADMIN.SET_USER_LABELS Procedure

The SA_USER_ADMIN.SET_USER_LABELS procedure sets the user's levels, compartments, and groups using a set of labels, instead of the individual components.

Syntax

SA_USER_ADMIN.SET_USER_LABELS (
  policy_name      IN VARCHAR2,
  user_name        IN VARCHAR2,
  max_read_label   IN VARCHAR2,
  max_write_label  IN VARCHAR2 DEFAULT NULL,
  min_write_label  IN VARCHAR2 DEFAULT NULL,
  def_label        IN VARCHAR2 DEFAULT NULL,
  row_label        IN VARCHAR2 DEFAULT NULL);

Parameters

Table E-77 SA_USER_ADMIN.SET_USER_LABELS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

Specifies the user name. This user does not need any Oracle Label Security authorizations before you run this procedure.

max_read_label

Specifies the label string to be used to initialize the user's maximum authorized read label. Composed of the user's maximum level, compartments authorized for read access, and groups authorized for read access.

To find information for these settings, query the DBA_SA_USERS data dictionary view.

max_write_label

Specifies the label string to be used to initialize the user's maximum authorized write label. Composed of the user's maximum level, compartments authorized for write access, and groups authorized for write access. If max_write_label is not specified, then it is set to max_read_label.

min_write_label

Specifies the label string to be used to initialize the user's minimum authorized write label. Contains only the level, with no compartments or groups. If min_write_label is not specified, then it is set to the lowest defined level for the policy, with no compartments or groups.

def_label

Specifies the label string to be used to initialize the user's session label, including level, compartments, and groups (a subset of max_read_label). If default_label is not specified, then it is set to max_read_label.

row_label

Specifies the label string to be used to initialize the program's row label. Includes level, components, and groups: subsets of max_write_label and def_label. If row_label is not specified, then it is set to def_label, with only the compartments and groups authorized for write access.

Example

The following example sets user labels for the hr_ols_pol policy for user jjones.

BEGIN
 SA_USER_ADMIN.SET_USER_LABELS (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jjones',
  max_read_label    => 'HS:FIN',
  max_write_label   => 'HS',
  def_label         => 'HS',
  row_label         => 'HS');
END;
/

See Also:

"SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

SA_USER_ADMIN.SET_USER_PRIVS Procedure

The SA_USER_ADMIN.SET_USER_PRIVS procedure sets policy-specific privileges for users. These privileges do not become effective until the next time the user logs into the database. The new set of privileges replaces any existing privileges. A NULL value for the privileges parameter removes the user's privileges for the policy.

To assign policy privileges to users, you must have the EXECUTE privilege for the SA_USER_ADMIN package, and must have been granted the policy_DBA role.

Syntax

SA_USER_ADMIN.SET_USER_PRIVS (
  policy_name     IN VARCHAR2,
  user_name       IN VARCHAR2,
  privileges      IN VARCHAR2);

Parameters

Table E-78 SA_USER_ADMIN.SET_USER_PRIVS Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

user_name

The name of the user to be granted privileges. This user should already have been authorized for policy levels, compartments, and groups. To find this user, query the USER_NAME column of the DBA_SA_USER_COMPARTMENTS, DBA_SA_USER_GROUPS, and DBA_SA_USER_LABELS views.

privileges

A character string of policy-specific privileges separated by commas. See "About Granting Privileges to Users and Trusted Program Units for the Policy" for list of available privileges to grant.

Example

The following example grants user jgodfrey full privileges for the hr_ols_pol policy settings.

BEGIN
 SA_USER_ADMIN.SET_USER_PRIVS (
  policy_name       => 'hr_ols_pol',
  user_name         => 'jgodfrey',
  privileges        => 'FULL');
END;
/

See Also:

"About Granting Privileges to Users and Trusted Program Units for the Policy"

"SA_USER_ADMIN.SET_PROG_PRIVS Procedure"

SA_UTL PL/SQL Utility Functions and Procedures

The SA_UTL PL/SQL package contains functions and procedures for use within PL/SQL programs to return information about the current values of the session security attributes, as numeric label values. These APIs are primarily for use in trusted stored program units. You do not need special privileges to use this package.

Table E-79 lists the SA_UTL PL/SQL package functions and procedures.

Table E-79 SA_UTL PL/SQL PL/SQL Package Contents

Function or Procedure
Description

SA_UTL.CHECK_LABEL_CHANGE Function

Checks if the user can change the data label for a policy protected table row

SA_UTL.CHECK_READ Function

Checks if the user can read a policy-protected table row

SA_UTL.CHECK_WRITE Function

Checks if the user can insert, update, or delete data in a policy protected table row

SA_UTL.DATA_LABEL Function

Returns TRUE if the label is a data label

SA_UTL.GREATEST_LBOUND Function

Returns a label that is the greatest lower bound of the two label arguments

SA_UTL.LEAST_UBOUND Function

Returns a label that is the least upper bound of the label arguments

SA_UTL.NUMERIC_LABEL Function

Returns the current session label

SA_UTL.NUMERIC_ROW_LABEL Function

Returns the current row label

SA_UTL.SET_LABEL Procedure

Sets the label of the current database session

SA_UTL.SET_ROW_LABEL Procedure

Set the row label of the current database session

See Also:

"Setting and Returning Label Information"

SA_UTL.CHECK_LABEL_CHANGE Function

The SA_UTL.CHECK_LABEL_CHANGE function checks if the user can change the data label for a policy protected table row. This function returns 1 if the user can change the data label. It returns 0 if the user cannot change the data label. The input values are the policy name, the current data label, and the new data label.

Syntax

SA_UTL.CHECK_LABEL_CHANGE (
  policy_name     IN VARCHAR2,
  current_label   IN NUMBER,
  new_label       IN NUMBER)
RETURN NUMBER;

Note:

You must have update privileges on the table to write any data into the table.

Parameters

Table E-80 SA_UTL.CHECK_LABEL_CHANGE Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

current_label

The current value of the label. To find existing label values, query the LABEL column of the ALL_SA_LABELS view.

new_label

The new value for the label

Example

The following example indicates if users can change data labels in policy-protected rows.

SET SERVEROUTPUT ON
BEGIN
  IF SA_UTL.CHECK_LABEL_CHANGE('hr_ols_pol',2000, 2200) = 1
   THEN DBMS_OUTPUT.PUT_LINE('Users can chagne data labels in policy-protected rows.');
  ELSE
   DBMS_OUTPUT.PUT_LINE('Users cannot change data labels in policy-protected rows.');
  END IF;
END;
/

SA_UTL.CHECK_READ Function

The SA_UTL.CHECK_READ function checks if a user can read a policy-protected table row. This function returns 1 if the user can read the table row. It returns 0 if the user cannot read the table row.

Note:

The user must have the SELECT privilege on the table to read any data from the table.

Syntax

SA_UTL.CHECK_READ (
  policy_name     IN VARCHAR2,
  label           IN NUMBER)
RETURN NUMBER;

Parameters

Table E-81 SA_UTL.CHECK_READ Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The label to be checked. To find existing label values, query the LABEL column of the ALL_SA_LABELS view.

Example

The following example indicates if users can read a policy-protected row.

SET SERVEROUTPUT ON
BEGIN
  IF SA_UTL.CHECK_READ('hr_ols_pol',2000) = 1
   THEN DBMS_OUTPUT.PUT_LINE('Users can read policy-protected rows.');
  ELSE
   DBMS_OUTPUT.PUT_LINE('Users cannot read policy-protected rows.');
  END IF;
END;
/

SA_UTL.CHECK_WRITE Function

The SA_UTL.CHECK_WRITE function to checks if the user can insert, update, or delete data in a policy protected table row. The user should already have the UPDATE privilege on the table to write any data into the table. This function returns 1 if the user can write to the table row. It returns 0 if the user cannot write to the table row. The input values are the policy name and the row data label.

Syntax

SA_UTL.CHECK_WRITE (
  policy_name     IN VARCHAR2,
  label           IN NUMBER)
RETURN NUMBER;

Parameters

Table E-82 SA_UTL.CHECK_WRITE Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The label to be checked. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

Example

The following example indicates if users can write to policy-protected rows.

SET SERVEROUTPUT ON
BEGIN
  IF SA_UTL.CHECK_WRITE('hr_ols_pol',2000) = 1
   THEN DBMS_OUTPUT.PUT_LINE('Users can write to policy-protected rows.');
  ELSE
   DBMS_OUTPUT.PUT_LINE('Users cannot write to policy-protected rows.');
  END IF;
END;
/

SA_UTL.DATA_LABEL Function

The SA_UTL.DATA_LABEL function returns TRUE if the label is a data label.

Syntax

SA_UTL.DATA_LABEL(
 label IN NUMBER)
RETURN BOOLEAN;

Parameters

Table E-83 SA_UTL.DATA_LABEL Parameter

Parameter
Description

label

The label to be checked. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

Example

The following example indicates if the label 2000 is a data label.

SET SERVEROUTPUT ON
BEGIN
 IF SA_UTL.DATA_LABEL(2000)
  THEN DBMS_OUTPUT.PUT_LINE('Label 2000 is a data label.');
 ELSE
  DBMS_OUTPUT.PUT_LINE('Label 2000 is not a data label.');
 END IF;
END;
/

SA_UTL.GREATEST_LBOUND Function

The SA_UTL.GREATEST_LBOUND function returns a label that is the greatest lower bound of the two label arguments.

Syntax

SA_UTL.GREATEST_LBOUND (
 label1 IN NUMBER,
 label2 IN NUMBER)
RETURN NUMBER;

Parameters

Table E-84 SA_UTL.GREATEST_LBOUND Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Examples

The following example compares existing label tags 3110 and 3111.

SELECT SA_UTL.GREATEST_LBOUND(3110,3111) FROM DUAL;

SA_UTL.GREATEST_LBOUND(3110,3111)
---------------------------------
                             3111

SA_UTL.LEAST_UBOUND Function

The SA_UTL.LEAST_UBOUND function returns a label that is the least upper bound of the label arguments.

Syntax

SA_UTL.LEAST_UBOUND (
 label1 IN NUMBER,
 label2 IN NUMBER)
RETURN NUMBER;

Parameters

Table E-85 SA_UTL.LEAST_UBOUND Parameters

Parameter
Description

label1

The first label to check. To find existing label values, query the LABEL and TAG columns of the ALL_SA_LABELS view.

label2

The second label to check

Example

The following example compares existing labels 3110 and 3111.

SELECT SA_UTL.LEAST_UBOUND(3110,3111) FROM DUAL;

SA_UTL.LEAST_UOUND(3110,3111)
-----------------------------
                         3110

See Also:

"Determining Upper and Lower Bounds of Labels". The functions described here are the same as those described in Chapter 6, except that these return a number instead of a character string.

SA_UTL.NUMERIC_LABEL Function

The SA_UTL.NUMERIC_LABEL function returns the current session label. It takes a policy name as the input parameter and returns a NUMBER value.

Syntax

SA_UTL.NUMERIC_LABEL (
  policy_name)
RETURN NUMBER;

Parameters

Table E-86 SA_UTL.NUMERIC_LABEL Parameter

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Example

The following example returns a the session numeric label for the user who is currently connected to the database instance.

SET SERVEROUTPUT ON
DECLARE
 num_label number;
BEGIN
 num_label := SA_UTL.NUMERIC_LABEL('hr_ols_pol');
 DBMS_OUTPUT.PUT_LINE('Numeric label: '||num_label);
END;
/

SA_UTL.NUMERIC_ROW_LABEL Function

The SA_UTL.NUMERIC_ROW_LABEL function returns the current row label. It takes a policy name as the input parameter and returns a NUMBER value.

Syntax

SA_UTL.NUMERIC_ROW_LABEL (
  policy_name)
RETURN NUMBER;

Parameters

Table E-87 SA_UTL.NUMERIC_ROW_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

Examples

The following example returns the session numeric row label for the user who is currently connected to the database instance.

SET SERVEROUTPUT ON
DECLARE
 num_row number;
BEGIN
 num_row := SA_UTL.NUMERIC_ROW_LABEL('hr_ols_pol');
 DBMS_OUTPUT.PUT_LINE('Numeric row label: '||num_row);
END;
/

SA_UTL.SET_LABEL Procedure

The SA_UTL.SET_LABEL procedure sets the label of the current database session. The session's write label and row label are set to the subset of the label's compartments and groups that are authorized for write access.

Syntax

SA_UTL.SET_LABEL (
 policy_name IN VARCHAR2,
 label       IN LBAC_LABEL);

Parameters

Table E-88 SA_UTL.SET_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The label to set as the session label. To find existing label values, query the LABEL column of the ALL_SA_LABELS view.

You must pass this parameter through as an output of the TO_LBAC_DATA_LABEL function, which converts a label in character form to an LBAC_LABEL type. (The example in the next section shows how to do this.)

See also "Understanding Labeling Functions in Oracle Label Security Policies".

Example

The following example sets the label for the hr_ols_pol policy.

BEGIN
  SA_UTL.SET_LABEL (
    policy_name => 'hr_ols_pol',
    label       => to_lbac_data_label('hr_ols_pol','hs:pii'));
END;
/

SA_UTL.SET_ROW_LABEL Procedure

The SA_UTL.SET_ROW_LABEL procedure sets the row label of the current database session. The compartments and groups in the label must be a subset of compartments and groups in the session label that are authorized for write access.

Syntax

SA_UTL.SET_ROW_LABEL (
 policy_name IN VARCHAR2,
 label       IN BINARY_INTEGER);

Parameters

Table E-89 SA_UTL.SET_ROW_LABEL Parameters

Parameter
Description

policy_name

Specifies the policy. To find existing policies, query the POLICY_NAME column of the ALL_SA_POLICIES data dictionary view.

label

The label to set as the session default row label. To find existing label values, query the LABEL column of the ALL_SA_LABELS view.

Example

The following example sets the row label for the hr_ols_pol policy to 3000.

BEGIN
 SA_UTL.SET_ROW_LABEL (
  policy_name         => 'hr_ols_pol',
  label               => 1111);
END;
/

See Also:

"SA_SESSION Session Management PL/SQL Package"

F Oracle Label Security Reference

This appendix provides the following reference information:

Oracle Label Security Data Dictionary Tables and Views

Oracle Database Data Dictionary Tables

Oracle Label Security Data Dictionary Views

Oracle Label Security User-Created Auditing View

Restrictions in Oracle Label Security

CREATE TABLE AS SELECT Restriction in Oracle Label Security

Label Tag Restriction

Export Restriction in Oracle Label Security

Oracle Label Security Removal Restriction

Shared Schema Support

Hidden Columns Restriction

Oracle Label Security Data Dictionary Tables and Views

Oracle Database Data Dictionary Tables

Oracle Label Security Data Dictionary Views

Oracle Label Security User-Created Auditing View

Oracle Database Data Dictionary Tables

Oracle Label Security does not label the Oracle data dictionary tables. Access is controlled by standard Oracle Database system and object privileges. For a description of all data dictionary tables and views, refer to the Oracle Database Reference.

Oracle Label Security Data Dictionary Views

Oracle Label Security maintains an independent set of data dictionary tables. These tables are exempt from any policy enforcement. This section lists the views that can display information related to Oracle Label Security.

Note that access to the DBA views is granted by default to the SELECT_CATALOG_ROLE, a standard Oracle Database role that lets you examine the Oracle Database data dictionary.

ALL_SA_AUDIT_OPTIONS View

The ALL_SA_AUDIT_OPTIONS data dictionary view shows the Oracle Label Security auditing options for the current user, configured using SA_AUDIT_ADMIN.AUDIT procedure. (See "SA_AUDIT_ADMIN.AUDIT Procedure".) The view displays whether auditing is configured to generate audit records per session (BY SESSION) or per access (BY ACCESS) and for successful or unsuccessful operations. Possible values are as follows:

A dash (-) indicates that the audit option is not set.

The S character indicates that the audit option is set BY SESSION.

The A character indicates that the audit option is set BY ACCESS.

Each audit option has two possible settings, WHENEVER SUCCESSFUL and WHENEVER NOT SUCCESSFUL, separated by a slash (/).

For example, in the following output, user jjones is audited with the BY ACCESS audit type for successful actions involving policy-specific privileges. User rlayton is audited with the BY SESSION audit type: audit records are written for failed attempts to remove policies and for successful attempts at setting user authorizations.

SELECT * FROM DBA_SA_AUDIT_OPTIONS;

POLICY_NAME      USER_NAME     APY  REM   SET_  PRV
-----------      ------------  ---  ----  ----  ---
HR_OLS_POL       JJONES        -/-   -/-  -/-   A/-
HR_OLS_POL       RLAYTON       -/-  -/S   S/-   -/-

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
USER_NAME | VARCHAR2(128) | NOT NULL | Name of the user associated with the policy
APY | VARCHAR2(3) |  | Audit option; refers to the application of specified Oracle Label Security policies to tables and schemas
REM | VARCHAR2(3) |  | Audit option; refers to the removal of specified Oracle Label Security policies from tables and schemas
SET_ | VARCHAR2(3) |  | Audit option; refers to the setting of user authorizations, and user and program privileges
PRV | VARCHAR2(3) |  | Audit option; refers to the use of all policy-specific privileges

ALL_SA_COMPARTMENTS View

The ALL_SA_COMPARTMENTS data dictionary view shows for the current user information about Oracle Label Security policy compartments, based on the settings used in the SA_COMPONENTS.CREATE_COMPARTMENT procedure. (See "SA_COMPONENTS.CREATE_COMPARTMENT Procedure".)

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
COMP_NUM | NUMBER(4) | NOT NULL | Compartment number in the range of (0-9999)
SHORT_NAME | VARCHAR2(30) | NOT NULL | Short name for the compartment
LONG_NAME | VARCHAR2(80) | NOT NULL | Long name for the compartment

ALL_SA_DATA_LABELS View

The ALL_SA_DATA_LABELS data dictionary view shows for the current user the label and label tag for the specified Oracle Label Security policy, based on settings from the SA_LABEL_ADMIN.CREATE_LABEL procedure. (See "SA_LABEL_ADMIN.CREATE_LABEL Procedure".)

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
LABEL | VARCHAR2(4000) |  | Short name of the level, compartment, or group that was specified as the label value
LABEL_TAG | NUMBER |  | Integer that represents the sort order of the label, relative to other policy labels (0-99999999)

ALL_SA_GROUPS View

The ALL_SA_GROUPS data dictionary view shows for the current user information about Oracle Label Security policy groups, based on the SA_COMPONENTS.CREATE_GROUP and SA_COMPONENTS.ALTER_GROUP_PARENT procedures. (See"SA_COMPONENTS.CREATE_GROUP Procedure" and "SA_COMPONENTS.ALTER_GROUP_PARENT Procedure".)

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
GROUP_NUM | NUMBER(4) | NOT NULL | Group number (0-9999)
SHORT_NAME | VARCHAR2(30) | NOT NULL | Short name of the group
LONG_NAME | VARCHAR2(80) | NOT NULL | Long name of the group
PARENT_NUM | NUMBER(4) |  | Numerical ID for the associated parent group
PARENT_NAME | VARCHAR2(30) |  | Name of the group assigned as the parent for the group

ALL_SA_LABELS View

The ALL_SA_LABELS data dictionary view shows for the current user information about the tags and types of labels, based on the SA_LABEL_ADMIN.CREATE_LABEL and SA_LABEL_ADMIN.ALTER_LABEL procedures. (See "SA_LABEL_ADMIN.CREATE_LABEL Procedure" and "SA_LABEL_ADMIN.ALTER_LABEL Procedure".) Access to ALL_SA_LABELS is PUBLIC. However, only the labels authorized for read access by the session are visible.

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
LABEL | VARCHAR2(4000) | NOT NULL | Short name of the level associated with this label
LABEL_TAG | NUMBER(30) | NOT NULL | Integer tag assigned to the label
LABEL_TYPE | VARCHAR2(15) |  | Type of label

ALL_SA_LEVELS View

The ALL_SA_LEVELS data dictionary view shows for the current user information about levels, based on the SA_COMPONENTS.CREATE_LEVEL procedure. (See "SA_COMPONENTS.CREATE_LEVEL Procedure".)

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
LEVEL_NUM | NUMBER(4) | NOT NULL | Level number (0-9999)
SHORT_NAME | VARCHAR2(30) | NOT NULL | Short name for the level
LONG_NAME | VARCHAR2(80) | NOT NULL | Long name for the level

ALL_SA_POLICIES View

The ALL_SA_POLICIES data dictionary view shows for the current user information about Oracle Label Security policies, based on the SA_SYSDBA.CREATE_POLICY procedure, and whether the policy has been enabled or disabled. (See "SA_SYSDBA.CREATE_POLICY Procedure".)

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

COLUMN_NAME
VARCHAR2(128)
NOT NULL
Name of the column that was added to tables protected by the policy

STATUS
VARCHAR2(8)

Whether the policy has been enabled or disabled

POLICY_OPTIONS
VARCHAR2(4000)

Options that were set for this policy

See Table 8-2 for a listing of the possible enforcement options.

ALL_SA_PROG_PRIVS View

The ALL_SA_PROG_PRIVS data dictionary view shows for the current user information about the policy-specific privileges for program units, based on the SA_USER_ADMIN.SET_PROG_PRIVS procedure. (See "SA_USER_ADMIN.SET_PROG_PRIVS Procedure".)

Column
Datatype
Null
Description

SCHEMA_NAME
VARCHAR2(128)
NOT NULL
Name of the schema that contains the program unit

PROGRAM_NAME
VARCHAR(128)
NOT NULL
Program unit that was granted privileges

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

PROGRAM_PRIVILEGES
VARCHAR2(4000)

Policy-specific privileges.

See "About Granting Privileges to Users and Trusted Program Units for the Policy" for list of possible privileges.

ALL_SA_SCHEMA_POLICIES View

The ALL_SA_SCHEMA_POLICIES data dictionary view shows for the current user information about policies that have been applied to all tables in the schema, based on the SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY procedure. (See "SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY Procedure".) It also indicates if the schema enforcement options have been enabled or disabled.

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

SCHEMA_NAME
VARCHAR2(128)
NOT NULL
Name of the schema associated with this policy

STATUS
VARCHAR2(8)

Whether the policy has been enabled or disabled for the schema (by the SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY or SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY for procedure)

SCHEMA_OPTIONS
VARCHAR2(4000)

Options that have been applied.

See Table 8-2 for a listing of the default enforcement options.

ALL_SA_TABLE_POLICIES View

The ALL_SA_TABLE_POLICIES data dictionary view shows for the current user information about a policy that has been added to a specific database table, based on the settings from the SA_POLICY_ADMIN.APPLY_TABLE_POLICY procedure. (See "SA_POLICY_ADMIN.APPLY_TABLE_POLICY Procedure".)

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

SCHEMA_NAME
VARCHAR2(128)
NOT NULL
Schema that contains the table that the policy protects

TABLE_NAME
VARCHAR2(128)
NOT NULL
Table to be protected by the policy

STATUS
VARCHAR2(8)

Whether the policy has been enabled or disabled for the table (by the SA_POLICY_ADMIN.APPLY_TABLE_POLICY or SA_POLICY_ADMIN.DISABLE_TABLE_POLICY for procedure)

TABLE_OPTIONS
VARCHAR2(4000)

Policy enforcement options to be used for the table

See Table 8-2 for a listing of the default enforcement options.

FUNCTION
VARCHAR2(1024)

Name of the function to return a label value to use as the default

PREDICATE
VARCHAR2(256)

Predicate to combine (using AND or OR) with the label-based predicate for READ_CONTROL

ALL_SA_USERS View

The ALL_SA_USERS data dictionary view shows for the current user information about the privileges that Oracle Label Security users have, based on the SA_USER_ADMIN.SET_USER_LABELS and SA_USER_ADMIN.SET_USER_PRIVS procedure procedures. (See "SA_USER_ADMIN.SET_USER_LABELS Procedure" and "SA_USER_ADMIN.SET_USER_PRIVS Procedure".)

Column
Type
Null
Description

USER_NAME
VARCHAR2(1024)
NOT NULL
Name of the user

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

USER_PRIVILEGES
VARCHAR2(4000)

Policy-specific privileges granted to the user.

See "About Granting Privileges to Users and Trusted Program Units for the Policy" for list of possible privileges.

MAX_READ_LABEL
VARCHAR2(4000)

Label string to initialize the user's maximum authorized read label

MAX_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's maximum authorized write label

MIN_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's minimum authorized write label

DEFAULT_READ_LABEL
VARCHAR2(4000)

Label string to initialize the user's session label, including level, compartments, and groups, for read access

DEFAULT_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's session label, including level, compartments, and groups, for write access

DEFAULT_ROW_LABEL
VARCHAR2(4000)

Label string to initialize the program's row label; includes level, components, and groups

USER_LABELS
VARCHAR2(4000)

Retained solely for backward compatibility and will be removed in the next release

ALL_SA_USER_LABELS View

The ALL_SA_USER_LABELS data dictionary view shows for the current user label-specific information about users, based on the SA_USER_ADMIN.SET_USER_LABELS. (See "SA_USER_ADMIN.SET_USER_LABELS Procedure".)

Column
Datatype
Null
Description

USER_NAME
VARCHAR2(1024)
NOT NULL
Name of the user

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

LABELS
VARCHAR2(4000)

Retained solely for backward compatibility and will be removed in the next release

MAX_READ_LABEL
VARCHAR2(4000)
NOT NULL
Label string to initialize the user's maximum authorized read label

MAX_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's maximum authorized write label

MIN_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's minimum authorized write label

DEFAULT_READ_LABEL
VARCHAR2(4000)

Label string to initialize the user's session label, including level, compartments, and groups, for read access

DEFAULT_WRITE_LABEL
VARCHAR2(4000)

Label string to initialize the user's session label, including level, compartments, and groups, for write access

DEFAULT_ROW_LABEL
VARCHAR2(4000)

Label string to initialize the program's row label; includes level, components, and groups

ALL_SA_USER_LEVELS View

The ALL_SA_USER_LEVELS data dictionary view shows for the current user the minimum and maximum levels that have been assigned to users and lists the default values for the user's session label and row label, based on the SA_USER_ADMIN.SET_LEVELS procedure. (See "SA_USER_ADMIN.SET_LEVELS Procedure".)

Column | Datatype | Null | Description
POLICY_NAME | VARCHAR2(30) | NOT NULL | Name of the Oracle Label Security policy
USER_NAME | VARCHAR2(1024) | NOT NULL | Name of the user
MAX_LEVEL | VARCHAR2(30) | NOT NULL | Short name of the highest level for read and write access
MIN_LEVEL | VARCHAR2(30) | NOT NULL | Short name of the lowest level for read and write access
DEF_LEVEL | VARCHAR2(30) | NOT NULL | Short name of the default level
ROW_LEVEL | VARCHAR2(30) | NOT NULL | Short name of the row level

ALL_SA_USER_PRIVS View

The ALL_SA_USER_PRIVS data dictionary view shows for the current user the policy-specific privileges that have been granted to users, based on the SA_USER_ADMIN.SET_USER_PRIVS procedure. (See "SA_USER_ADMIN.SET_USER_PRIVS Procedure".)

Column
Datatype
Null
Description

USER_NAME
VARCHAR2(1024)
NOT NULL
Name of the user

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

USER_PRIVILEGES
VARCHAR2(4000)

Policy-specific privileges granted to the user

See "About Granting Privileges to Users and Trusted Program Units for the Policy" for available privileges

DBA_SA_AUDIT_OPTIONS View

The DBA_SA_AUDIT_OPTIONS data dictionary view data dictionary view shows for the entire database the Oracle Label Security audit options. Its columns are the same as ALL_SA_AUDIT_OPTIONS.

See Also:

"ALL_SA_AUDIT_OPTIONS View"

DBA_SA_COMPARTMENTS View

The ALL_SA_COMPARTMENTS data dictionary view shows for the entire database information about Oracle Label Security policy compartments. Its columns are the same as ALL_SA_COMPARTMENTS.

See Also:

"ALL_SA_COMPARTMENTS View"

DBA_SA_DATA_LABELS View

The ALL_SA_DATA_LABELS data dictionary view shows for the entire database the label and label tag for the specified Oracle Label Security policy. Its columns are the same as ALL_SA_DATA_LABELS.

See Also:

"ALL_SA_DATA_LABELS View"

DBA_SA_GROUPS View

The ALL_SA_GROUPS data dictionary view shows for the entire database information about Oracle Label Security policy groups. Its columns are the same as ALL_SA_GROUPS.

See Also:

"ALL_SA_GROUPS View"

DBA_SA_GROUP_HIERARCHY View

The DBA_SA_GROUP_HIERARCHY data dictionary view shows the hierarchy of groups (that is, parent-child relationships) in a policy.

Column
Type
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

HIERARCHY_LEVEL
NUMBER

Indicates the level of a particular group in a group hierarchy. A group with no parent group will have HIERARCHY_LEVEL 1. Its child group will have HIERARCHY_LEVEL 2 and so on.

For example, consider these groups in the following order:

G1, G4

G2, G5

G3

Here, G1 and G4 have HIERARCHY_LEVEL 1; G2 and G5 have HIERARCHY_LEVEL 2, and G3 has HIERARCHY_LEVEL 3.

The parent-child relationships are:

G3 is the child group of G2, and G2 is the child group of G1.

G5 is the child group of G4.

GROUP_NAME
VARCHAR2(4000)

Short name of the group intended to indicate the hierarchy level

DBA_SA_LABELS View

The ALL_SA_LABELS data dictionary view shows for the entire database information about the tags and types of labels for a policy. Its columns are the same as ALL_SA_LABELS.

See Also:

"ALL_SA_LABELS View"

DBA_SA_LEVELS View

The ALL_SA_LEVELS data dictionary view shows for the entire database information about levels associated with a policy. Its columns are the same as ALL_SA_LEVELS.

See Also:

"ALL_SA_LABELS View"

DBA_SA_POLICIES View

The DBA_SA_POLICIES data dictionary view shows for the entire database information about Oracle Label Security policies, based on the SA_SYSDBA.CREATE_POLICY procedure, and whether the policy has been enabled or disabled and its subscription status.

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

COLUMN_NAME
VARCHAR2(128)
NOT NULL
Name of the column that was added to tables protected by the policy

STATUS
VARCHAR2(8)

Whether the policy has been enabled or disabled

POLICY_OPTIONS
VARCHAR2(4000)

Options that were set for this policy.

See Table 8-2 for a listing of the possible enforcement options.

POLICY_SUBSCRIBED
VARCHAR2(5)

Indicates the policy's subscription status, based on the SA_POLICY_ADMIN.POLICY_SUBSCRIBE or SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE procedure

DBA_SA_PROG_PRIVS View

The DBA_SA_PROG_PRIVS data dictionary view shows for the entire database information about the policy-specific privileges for program units. Its columns are the same as ALL_SA_PROG_PRIVS.

See Also:

"ALL_SA_PROG_PRIVS View"

DBA_SA_SCHEMA_POLICIES View

The DBA_SA_SCHEMA_POLICIES data dictionary view shows for the entire database information about policies that have been applied to all tables in the schema. Its columns are the same as ALL_SA_SCHEMA_POLICIES.

See Also:

"ALL_SA_SCHEMA_POLICIES View"

DBA_SA_TABLE_POLICIES View

The DBA_SA_TABLE_POLICIES data dictionary view shows for the entire database information about a policy that has been added to a specific database table. Its columns are the same as ALL_SA_TABLE_POLICIES.

See Also:

"ALL_SA_SCHEMA_POLICIES View"

DBA_SA_USERS View

The DBA_SA_USERS data dictionary view shows for the entire database information about the privileges that Oracle Label Security users have. Its columns are the same as ALL_SA_USERS.

See Also:

"ALL_SA_USERS View"

DBA_SA_USER_COMPARTMENTS View

The DBA_SA_USER_COMPARTMENTS data dictionary view shows for the entire database the user authorizations, indicating whether the compartments are authorized for write and read privileges, based on the SA_USER_ADMIN.ADD_COMPARTMENTS procedure. (See "SA_USER_ADMIN.ADD_COMPARTMENTS Procedure".)

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

USER_NAME
VARCHAR2(1024)
NOT NULL
Name of the user

COMP
VARCHAR2(30)
NOT NULL
Short name of compartments that were added

RW_ACCESS
VARCHAR2(5)

Access mode. Possible values are:

SA_UTL.READ_ONLY indicates no write access

SA_UTL.READ_WRITE indicates that write is authorized

DEF_COMP
VARCHAR2(1)
NOT NULL
Whether the compartments are in the default compartments

ROW_COMP
VARCHAR2(1)
NOT NULL
whether the compartments are in the row label

DBA_SA_USER_GROUPS View

The DBA_SA_USER_GROUPS data dictionary view shows for the entire database the groups that are associated with users, based on the SA_USER_ADMIN.ADD_GROUPS procedure. (See "SA_USER_ADMIN.ADD_GROUPS Procedure".)

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

USER_NAME
VARCHAR2(1024)
NOT NULL
Name of the user

GRP
VARCHAR2(30)
NOT NULL
Short name of groups that were added

RW_ACCESS
VARCHAR2(5)

Access mode. Possible values are:

SA_UTL.READ_ONLY indicates read-only access

SA_UTL.READ_WRITE indicates read and write access

DEF_GROUP
VARCHAR2(1)
NOT NULL
Whether the group is in a default group

ROW_GROUP
VARCHAR2(1)
NOT NULL
Whether the group is in a label

DBA_SA_USER_LABELS View

The DBA_SA_USER_LABELS data dictionary view shows for the entire database label-specific information about users. Its columns are the same as ALL_SA_USER_LABELS.

See Also:

"ALL_SA_USER_LABELS View"

DBA_SA_USER_LEVELS View

The DBA_SA_USER_LEVELS data dictionary view shows, for the entire database, the minimum and maximum levels that have been assigned to users and lists the default values for the user's session label and row label. Its columns are the same as ALL_SA_USER_LEVELS.

See Also:

"ALL_SA_USER_LEVELS View"

DBA_SA_USER_PRIVS View

The DBA_SA_USER_PRIVS data dictionary view shows for the current user the policy-specific privileges that have been granted to users. Its columns are the same as ALL_SA_USER_PRIVS.

See Also:

"ALL_SA_USER_PRIVS View"

DBA_OLS_STATUS View

The DBA_OLS_STATUS data dictionary view describes the configuration status of Oracle Label Security in the database.

Column
Null
Datatype
Description

NAME

VARCHAR2(20)
Name of the status. Values are:

OLS_CONFIGURE_STATUS

OLS_DIRECTORY_STATUS

OLS_ENABLE_STATUS

STATUS

VARCHAR2(5)
Indicates the status of the feature mentioned in the corresponding name column. For example, a TRUE value for the OLS_CONFIGURE_STATUS status says that Oracle Label Security has been configured.

DESCRIPTION

VARCHAR2(4000)
Description of the status:

OLS_CONFIGURE_STATUS:Determines if Oracle Label Security is configured.

OLS_DIRECTORY_STATUS: Determines if Oracle Internet Directory is enabled with Oracle Label Security.

OLS_ENABLE_STATUS: Determines if Oracle Label Security is enabled.

USER_SA_SESSION View

The USER_SA_SESSION data dictionary view shows the security attribute values for the current database session. Access to this view is PUBLIC.

Column
Datatype
Null
Description

POLICY_NAME
VARCHAR2(30)
NOT NULL
Name of the Oracle Label Security policy

SA_USER_NAME
VARCHAR2(4000)

Name of the current session user

PRIVS
VARCHAR2(4000)

Current session privileges

MAX_READ_LABEL
VARCHAR2(4000)

Label string that initialized the user's maximum authorized read label

MAX_WRITE_LABEL
VARCHAR2(4000)

Label string that initialized the user's maximum authorized write label

MIN_LEVEL
VARCHAR2(4000)

Minimum Oracle Label Security level authorized for the session

LABEL
VARCHAR2(4000)

Label for the current database session

COMP_WRITE
VARCHAR2(4000)

Compartments to which the user is authorized to write

GROUP_WRITE
VARCHAR2(4000)

Groups to which the user is authorized to write

ROW_LABEL
VARCHAR2(4000)

Row label that is associated with the policy for the current session

Oracle Label Security User-Created Auditing View

Using the SA_AUDIT_ADMIN.CREATE_VIEW procedure, you can create an audit trail view for a specific policy. By default, this view is named DBA_policyname_AUDIT_TRAIL.

Column
Datatype
Null
Description

USERNAME
VARCHAR2(128)

Name of the user whose actions were audited

USERHOST
VARCHAR2(128)

Client host machine name

TERMINAL
VARCHAR2(255)

Identifier of the user's terminal

TIMESTAMP
DATE

Date and time of the creation of the audit trail entry (date and time of user login for entries created by AUDIT SESSION) in the local database session time zone

OWNER
VARCHAR2(128)

Creator of the object affected by the action

OBJ_NAME
VARCHAR2(128)

Name of the object affected by the action

ACTION
NUMBER
NOT NULL
Numeric action type code. The corresponding name of the action type is in the ACTION_NAME column.

ACTION_NAME
VARCHAR2(47)

Name of the action type corresponding to the numeric code in the ACTION column

COMMENT_TEXT
VARCHAR2(4000)

Text comment on the audit trail entry, providing more information about the statement audited

Also indicates how the user was authenticated. The method can be one of the following:

DATABASE: Authentication was done by password

NETWORK: Authentication was done by Oracle Net Services or by strong authentication

SESSIONID
NUMBER
NOT NULL
Numeric ID for each Oracle session

ENTRYID
NUMBER
NOT NULL
Numeric ID for each audit trail entry in the session

STATEMENTID
NUMBER
NOT NULL
Numeric ID for each statement run

RETURNCODE
NUMBER
NOT NULL
Oracle error code generated by the action. Some useful values:

0: Action succeeded

2004: Security violation

EXTENDED_TIMESTAMP
TIMESTAMP (6) WITH TIME ZONE

Timestamp of the creation of the audit trail entry (timestamp of user login for entries created by AUDIT SESSION) in UTC (Coordinated Universal Time) time zone

OLS_COL
VARCHAR2(4000)

Name of the column that was added to the tables that Oracle Label Security protects

See Also:

"SA_AUDIT_ADMIN.CREATE_VIEW Procedure"

Restrictions in Oracle Label Security

The following restrictions exist in this Oracle Label Security release:

CREATE TABLE AS SELECT Restriction in Oracle Label Security

Label Tag Restriction

Export Restriction in Oracle Label Security

Oracle Label Security Removal Restriction

Shared Schema Support

Hidden Columns Restriction

CREATE TABLE AS SELECT Restriction in Oracle Label Security

If you attempt to perform CREATE TABLE AS SELECT in a schema that is protected by an Oracle Label Security policy, then the statement will fail.

Label Tag Restriction

Label tags must be unique across the policies in the database. When you use multiple policies in a database, you cannot use the same numeric label tag in different policies.

Export Restriction in Oracle Label Security

Before Oracle Database 12c Release 1 (12.1), the LBACSYS schema could not be exported due to the use of opaque types in Oracle Label Security. An export of the entire database (parameter FULL=Y) with Oracle Label Security installed can be done, except that the LBACSYS schema would not be exported. From Oracle Database Release 12c on, this restriction has been removed. See "Full Database Export" for additional details on the database versions that the export can be supported from.

Oracle Label Security Removal Restriction

Do not perform a DROP USER CASCADE on the LBACSYS account.

Connect to the database as user SYS, using the AS SYSDBA syntax, and run the file $ORACLE_HOME/rdbms/admin/catnools.sql to remove Oracle Label Security.

See Also:

Your platform-specific Oracle installation documentation

Shared Schema Support

User accounts defined in the Oracle Internet Directory cannot be given individual Oracle Label Security authorizations. However, authorizations can be given to the shared schema to which the directory users are mapped.

The Oracle Label Security function SET_ACCESS_PROFILE can be used programmatically to set the label authorization profile to use after a user has been authenticated and mapped to a shared schema. Oracle Label Security does not enforce a mapping between users who are given label authorizations in Oracle Label Security and actual database users.

Hidden Columns Restriction

PL/SQL does not recognize references to hidden columns in tables. A compiler error will be generated.

G Frequently Asked Questions about Oracle Label Security

This appendix attempts to answer some of the most common and frequently asked questions on Oracle Label Security.

Who Uses Oracle Label Security?

Sensitivity labels are used to categorize data in virtually every industry. These industries include health care, law enforcement, energy, retail, national security, and defense industries. The following list gives some examples of sensitivity labels:

Internal

ConfidentialPhysician OnlyHighly SensitiveWidget CorporationConfidential: Chicago OperationSensitive: Finance : EuropeTop SecretUnclassified

How can Oracle Label Security address my security needs?

Oracle Label Security can be used to label data and restrict access with a high degree of granularity. This is especially useful when multiple organizations or companies share a single application. Sensitivity labels can be used to restrict application users to an organization or to a subset of data within an organization.

Data privacy is important to consumers and regulatory measures continue to be announced. Oracle Label Security can be used to implement privacy policies on data, restricting access to only those who have a need-to-know.

Should I use Oracle Label Security to protect all my tables?

No. The traditional Oracle discretionary access control (DAC) object privileges such as SELECT, INSERT, UPDATE, and DELETE combined with database roles and stored procedures are sufficient in most cases.

What is the difference between Oracle Virtual Private Database and Oracle Label Security?

Oracle Virtual Private Database (VPD) is provided at no additional cost with the Enterprise Edition of Oracle Database. Oracle Label Security is an add-on security option for the Oracle Database Enterprise Edition.

Oracle VPD is a term used for several powerful security features like, fine grained access control (FGAC), application context and global application context. VPD policies are written using PL/SQL, and can be assigned to an individual table or view. An information request, that accesses a table or view protected by VPD, is modified according to the policy assigned to the table or view.

VPD policies can be as simple as enforcing access during business hours. VPD policies can restrict access by comparing the value of an attribute in an individual row with an application context value. Global application context allows an application context to be accessed across multiple database sessions, reducing or eliminating the need to create a separate application context for each user session.

Oracle Label Security is an out-of-the-box solution for row level security. No coding or software development is required, allowing the administrator to focus completely on the policy. Oracle Label Security provides an interface for creating policies, specifying enforcement options, defining data sensitivity labels, establishing user label authorizations, and protecting individual tables or schemes.

Data sensitivity labels provide a powerful and flexible method of restricting access to data. For example, data belonging to different organizations or companies can be separated using data sensitivity labels and selectively shared between companies by changing the data sensitivity label.

Depending on the complexity of the security policy, Oracle Virtual Private Database may be the preferred method for implementing your security policy. Oracle Label Security is best suited for situations where access control decisions need to be based on the sensitivity of the information.

Can I combine Virtual Private Database and Oracle Label Security?

Yes. The following scenarios are possible:

A WHERE clause can be appended to an OLS policy, which provides one more level of granularity. An example would be that users, regardless of their label authorizations, are only allowed to connect from a specific IP address or subnet, and during business hours only.

A VPD policy, whether column sensitive or not, can evaluate user labels and determine access to columns and rows without the need to apply data labels.

Can I use Oracle Label Security with the Oracle E-Business Suite?

Oracle Applications are using Oracle VPD to provide new functionality and security protections.

Can I use Oracle Label Security with Oracle Database Vault?

You can protect Oracle Database Vault tables using Oracle Label Security just as you would do for an Oracle Database table.

In addition, Oracle Label Security can be used together with Database Vault features. You can assign Oracle Label Security labels to Database Vault Factors. These labels are then merged with the user clearance labels, following the algorithms documented in "Merging Labels with the MERGE_LABEL Function", before access control decisions are being made by comparing the merged user labels with the row labels.

The following example on the Oracle Technology Network Web site also discusses using Oracle Label security along with Oracle Database Vault features:

http://www.oracle.com/technetwork/database/security/label-security-factors-093209.html

Does Oracle Label Security provide column-level access control?

No, Oracle Label Security is not column aware. This behavior is available with Virtual Private Database (VPD). A VPD policy can be written so that it only becomes active when a certain column is part of a SQL statement against a protected table. If the column sensitivity switch is on, then VPD either returns only those rows for which the sensitive column values are accessible to the user, or it returns all rows with all cells in the sensitive column being empty, except those values that the user is allowed to see.

The following link on the Oracle Technology Network Web site contains an example:

http://www.oracle.com/technetwork/database/security/index-088277.html

A column-sensitive VPD policy can determine access to a specific column by evaluating OLS user labels, which this example demonstrates:

http://www.oracle.com/technetwork/database/security/ols-cs1-099558.html

Can I base Secure Application Roles on Oracle Label Security?

Yes. The procedure that determines if the SET ROLE command is executed can evaluate OLS user labels. In this case, the OLS policy does not need to be applied to a table, since row labels are not part of this solution.

What are Trusted Stored Program Units?

Stored procedures, functions and packages execute with the system and object privileges (DAC) of the definer. If the invoker is a user with Oracle Label Security user clearances (labels), the procedure executes with a combination of the definer's DAC privileges and the invoker's security clearances.

Trusted stored procedures are procedures that are either granted the OLS privilege FULL or READ. When a trusted stored program unit is run, the policy privileges in force are a combination of the invoking user's privileges and the program unit's privileges.

Does VPD or OLS add an additional column to the protected table?

When you apply an Oracle Label Security (OLS) policy to a table, the policy adds an additional column to the table. The name of this column needs to be specified when the policy is initially created.

An existing column can be used to store the OLS row labels. This column must have the NUMBER(10) data type.

Virtual Private Database (VPD) does not add an additional column to the protected table.

Why should the additional OLS row label column be hidden?

Most applications were not designed with access control mechanisms in mind, so Oracle Label Security (OLS) needs to do this transparently.

When an application queries a table with a SELECT FROM tablename statement, it returns all columns, including the unhidden label column. Existing applications may not be designed to display an additional column, and malfunction. However, if the label column is hidden, then it is displayed only when its name is included in the SQL statement. A SELECT FROM tablename would return all columns as expected by the application, excluding the hidden OLS column.

Where can I find Oracle Label Security?

Oracle Label Security ships with the Oracle Database Enterprise Edition CD. Oracle Label Security is not installed as part of the default Oracle installation. You need to perform a custom installation to add Oracle Label Security to the database.

Index

A  B  C  D  E  F  G  H  I  L  M  N  O  P  R  S  T  U  V  W 

A

access control

discretionary, 3.5.4

understanding, 3

access mediation

and views, 3.5.5

enforcement options, 3.5.7

introduction, 3.1

label evaluation, 3.4

program units, 3.5.6

ADD_GROUPS procedure

inverse groups, 13.8.3

ALL_CONTROL option, 8.1.3, 8.1.3, 8.1.4, 8.1.8

ALL_SA_AUDIT_OPTIONS view, F.1.2.1, F.1.2.1

ALL_SA_COMPARTMENTS view, F.1.2.2, F.1.2.2, F.1.2.16

ALL_SA_DATA_LABELS view, F.1.2.3, F.1.2.3, F.1.2.17

ALL_SA_GROUPS view, F.1.2.4, F.1.2.4, F.1.2.18

ALL_SA_LABELS view, F.1.2.5, F.1.2.5, F.1.2.20

ALL_SA_LEVELS view, F.1.2.6, F.1.2.6, F.1.2.21

ALL_SA_POLICIES view, F.1.2.7, F.1.2.7

ALL_SA_PROG_PRIVS view, F.1.2.8, F.1.2.8

ALL_SA_SCHEMA_POLICIES view, F.1.2.9, F.1.2.9

ALL_SA_TABLE_POLICIES view, F.1.2.10, F.1.2.10

ALL_SA_USER_LABELS view, F.1.2.12, F.1.2.12

ALL_SA_USER_LEVELS view, F.1.2.13, F.1.2.13

ALL_SA_USER_PRIVS view, F.1.2.14, F.1.2.14

ALL_SA_USERS view, F.1.2.11, F.1.2.11

ALTER_GROUP_PARENT

inverse groups, 13.8.10

ALTER_GROUPS procedure

inverse groups, 13.8.4

ALTER_POLICY procedure

inverse groups, 13.8.2

ANALYZE command, 12.4.1

APPLY_SCHEMA_POLICY procedure

with inverse groups, 13.3.1

APPLY_TABLE_POLICY procedure

with inverse groups, 13.3.1

architecture, Oracle Label Security, 1.6

AS SYSDBA clause, 12.5

AUDIT_LABEL_ENABLED function, E.1.3

AUDIT_TRAIL parameter, 10.2

auditing

audit trails, 10.1, 10.2, E.1.4

creating audit view, E.1.4

disabling, E.1.7

disabling policy specific, E.1.6

dropping audit view, E.1.5

enabling

SA_AUDIT_ADMIN.AUDIT procedure, E.1.1

finding audit options, F.1.2.1

finding if labels are recorded, E.1.3

Oracle Label Security, 10.1, 10.4

recording policy labels, E.1.2

SA_AUDIT_ADMIN package, E.1

SA_AUDIT_ADMIN.AUDIT_LABEL procedure, E.1.2

SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED function, E.1.3

SA_AUDIT_ADMIN.CREATE_VIEW procedure, E.1.4

SA_AUDIT_ADMIN.DROP_VIEW procedure, E.1.5

SA_AUDIT_ADMIN.NOAUDIT procedure, E.1.6

SA_AUDIT_ADMIN.NOAUDIT_LABEL procedure, E.1.7

strategy, 10.5.1

systemwide, 10.2

types of, 5.9.8

views, E.1.4

B

B-tree indexes, 12.4.2

C

CDBs

Oracle Label Security, 1.8.2

CHAR_TO_LABEL function, 6.3.1, 6.5.1, 6.5.5

CHECK_CONTROL option

and label update, 8.4.2, 8.4.3

and labeling functions, 8.3.1

definition, 8.1.3, 8.1.4

with other options, 8.1.9

CHECK_WRITE function, E.8.3

child rows

deleting, 8.5

inserting, 8.3.3

updating, 8.4.4

Cloud Control login, 5.9.1

COMPACCESS privilege, 3.5.1, 3.5.2.3, 5.5.1

inverse groups, 13.3.5, 13.6

compartments

altering, E.2.1

creating, E.2.5

definition, 2.3.3, 5.3.4

deleting, E.2.8

example, 2.3.3, 5.3.4

finding, F.1.2.27

finding compartments user can read in session, E.5.1

finding compartments user can write to in session, E.5.2

finding user information, F.1.2.2

SA_COMPONENTS.ALTER_COMPARTMENT procedure, E.2.1

SA_COMPONENTS.CREATE_COMPARTMENT procedure, E.2.5

SA_COMPONENTS.DROP_COMPARTMENT procedure, E.2.8

SA_USER_ADMIN package, E.7

SA_USER_ADMIN.ADD_COMPARTMENTS procedure, E.7.1

SA_USER_ADMIN.ALTER_COMPARTMENTS, E.7.3

SA_USER_ADMIN.DROP_COMPARTMENTS procedure, E.7.7

SA_USER_ADMIN.SET_COMPARTMENTS procedure, E.7.10

setting authorizations, 3.3.1.2, 5.4.4

components

SA_COMPONENT package, E.2

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS procedure, E.7.5

CON, C.2

configuration of Oracle Label security

finding status, F.1.2.32

connection parameters, C.2

CREATE FUNCTION statement, 9.2.1

CREATE PACKAGE BODY statement, 9.2.1

CREATE PACKAGE statement, 9.2.1

CREATE PROCEDURE statement, 9.2.1

CREATE TABLE AS SELECT statement, F.2.1

CREATE_GROUP procedure

inverse groups, 13.8.9

CREATE_POLICY procedure

inverse groups, 13.8.1

CREATE_VIEW procedure, F.1.3

creating databases, 12.5

D

data

label-based access, 2.1, 2.1

data dictionary tables, 2.2, 12.4.1, 12.5, F.1.1

data labels

checking if label is data label, E.8.4

finding label and tag information, F.1.2.3

SA_UTL.DATA_LABEL function, E.8.4

Data Pump export

row labels, 12.1.2

Data Pump import, 12.2

database links, 11.2

databases, creating additional, 12.5

DBA_OLS_STATUS view, F.1.2.32, F.1.2.32

DBA_policyname_AUDIT_TRAIL view, F.1.3

DBA_SA_AUDIT_OPTIONS view, F.1.2.15, F.1.2.15

DBA_SA_COMPARTMENTS view, 12.2.2.2, F.1.2.16

DBA_SA_DATA_LABELS view, F.1.2.17

DBA_SA_GROUP_HIERARCHY view, F.1.2.19, F.1.2.19

DBA_SA_GROUPS view, 12.2.2.2, F.1.2.18

DBA_SA_LABELS view, 12.2.2.2, F.1.2.20

DBA_SA_LEVELS view, 12.2.2.2, F.1.2.21

DBA_SA_POLICIES view, F.1.2.22, F.1.2.22

DBA_SA_PROG_PRIVS view, F.1.2.23, F.1.2.23

DBA_SA_SCHEMA_POLICIES view, 8.1.11, F.1.2.24, F.1.2.24

DBA_SA_TABLE_POLICIES view, 8.1.11, F.1.2.25, F.1.2.25

DBA_SA_USER_COMPARTMENTS view, F.1.2.27, F.1.2.27

DBA_SA_USER_GROUPS view, F.1.2.28, F.1.2.28

DBA_SA_USER_LABELS view, F.1.2.29, F.1.2.29

DBA_SA_USER_LEVELS view, F.1.2.30, F.1.2.30

DBA_SA_USER_PRIVS view, F.1.2.31, F.1.2.31

DBA_SA_USERS view, F.1.2.26, F.1.2.26

default port, C.2

default row label, E.5.18

deinstallation, A

DELETE_CONTROL option, 8.1.3, 8.1.4, 8.5

DELETERESTRICT option, 8.5

deleting labeled data, 8.5

demobld.sql file, 1.7.1.1

disabling OLS, A.3

discretionary access control (DAC), 3.5.4

distributed databases

connecting to, 11.2

multiple policies, 3.6.2

Oracle Label Security configuration, 11.1

remote session label, 11.3

dominance

definition, 3.4.2, 3.4.2

functions

about, B.1.3.1

greatest lower bound, 6.4.4.2

inverse groups, 13.9

least upper bound, 6.4.4.1

overview, B.1.1

DOMINATED_BY function, B.1.3.9

DOMINATES function, B.1.1, B.1.3.7

DROP USER CASCADE restriction, F.2.4

dropping for specified compartments, E.7.7

duties

of security administrators, 1.4

E

enabling OLS, A.3

enforcement options

and UPDATE, 8.4.2

combinations of, 8.1.9

exemptions, 8.1.10

guidelines, 8.1.9

INVERSE_GROUP, 13.3.1

list of, 8.1.2

overview, 8.1.1

viewing, 8.1.11

EXEMPT ACCESS POLICY privilege, 8.1.10, 8.1.10

Export utility

LBACSYS restriction, F.2.3

policy enforcement, 8.1.10

row labels, 3.5.2.1, 12.2.2.2

F

FULL privilege, 3.5.1, 3.5.2.2, 3.5.2.4, 5.5.1

function call, D.1, D.2

G

granularity

to data access, 3.4.3

GREATEST_LBOUND function

inverse groups, 13.8.14

groups

altering, E.2.2

altering parent groups, E.2.3

creating group parent, E.2.6

definition, 2.3.4, 5.3.6

deleting, E.2.9

example, 2.3.4, 5.3.6

finding for entire database, F.1.2.28

finding hierarchy of parent-child relationships, F.1.2.19

finding policy groups, F.1.2.4

hierarchical, 2.3.4, 2.3.4, 2.5, 2.5, 5.3.6, 5.3.6, F.1.2.19

inverse, 13.2

parent, 2.3.4, 2.3.4, 2.3.4, 3.4.1.2, 3.4.1.2, 5.3.6, 5.3.6, 5.3.6, 13.3.4

read/write access, 3.4.1.2

SA_COMPONENTS.ALTER_GROUP procedure, E.2.2

SA_COMPONENTS.ALTER_GROUP_PARENT procedure, E.2.3

SA_COMPONENTS.CREATE_GROUP procedure, E.2.6

SA_COMPONENTS.DROP_GROUP, E.2.9

SA_SESSION.GROUP_READ function, E.5.3

SA_SESSION.GROUP_WRITE function, E.5.4

SA_USER_ADMIN package, E.7

SA_USER_ADMIN.ADD_GROUPS procedure, E.7.2

SA_USER_ADMIN.ALTER_GROUPS procedure, E.7.4

SA_USER_ADMIN.DROP_ALL_GROUPS procedure, E.7.6

SA_USER_ADMIN.DROP_GROUPS procedure, E.7.8

SA_USER_ADMIN.SET_GROUPS procedure, E.7.12

setting authorizations, 3.3.1.3, 5.4.6

H

HIDE, 6.1.1.1, E.6.1, E.6.2

HIDE option

default, E.6.2

discussion of, 8.1.5

example, 6.1.1.1

importing hidden column, 12.2.2.5

inserting data, 6.5.4

not exported, 12.1.2

per-table basis, 6.3.2.2

PL/SQL restriction, F.2.6

schema level, 8.1.2

I

impdp. See Data Pump import

Import utility

importing labeled data, 12.2.2.1.2, 12.2.2.2

importing policies, 12.1.2

importing unlabeled data, 12.2.2.4

with Oracle Label Security, 12.2.2

indexes, 12.4.2, 12.4.2

INITIAL_LABEL variable, B.3

INITIAL_ROW_LABEL variable, B.3

initialization parameters

AUDIT_TRAIL, 10.2

INSERT_CONTROL option, 8.1.3, 8.1.4, 8.3.1

inserting labeled data, 6.5, 8.3

INTO TABLE clause, 12.3.2

inverse groups

and label components, 13.3.2

COMPACCESS privilege, 13.3.5, 13.6

computed labels, 13.3.3

dominance, 13.9

implementation of, 13.3

introduction, 13.2

Max Read Groups, 13.3.3.2

Max Write Groups, 13.3.3.2

parent-child unsupported, 13.3.4

read algorithm, 13.4

session labels, 13.7

SET_DEFAULT_LABEL, 13.7.1

SET_LABEL, 13.7.2

SET_ROW_LABEL, 13.7.1, 13.7.2

user privileges, 13.3.5

write algorithm, 13.5

INVERSE_GROUP enforcement option

behavior of procedures, 13.8

implementation, 13.3.1

L

label components

defining, E.2

in distributed environment, 11.4

industry examples, 2.3.5

interrelation, 2.5

label evaluation process

COMPACCESS read, 3.5.2.3

COMPACCESS write, 3.5.2.3

inverse groups, COMPACCESS, 13.6

LABEL_UPDATE, 8.4.2

read access, 3.4.2

read access, inverse groups, 13.4

write access, 3.4.3

write access, inverse groups, 13.5

label tags

converting from string, 6.3.1

converting to string, 6.3.2

distributed environment, 11.4.1

example, 6.1.2.1

inserting data, 6.5.2

introduction, 2.4, 5.3.9

manually defined, 6.1.2.1, 6.1.2.2

strategy, 12.4.3

using in WHERE clauses, 6.4.1

LABEL_DEFAULT option

and labeling functions, 8.2.1, 8.2.2

authorizing compartments, 3.3.1.2

authorizing groups, 3.3.1.3

definition, 8.1.3

importing unlabeled data, 12.2.2.4

inserting labeled data, 6.5.3

with enforcement options, 8.1.9, 8.1.9

with SA_SESSION.SET_ROW_LABEL, E.5.18

LABEL_TO_CHAR function, 6.3.2, 6.3.2.1, 6.4.3

LABEL_UPDATE option

and labeling functions, 8.1.6.2, 8.2.2

and privileges, 8.1.6.2

and WRITE_CONTROL, 8.1.7.2

and WRITEDOWN, 3.5.3

and WRITEUP, 3.5.1, 3.5.1, 3.5.1, 3.5.3, 5.5.1, 5.5.1, 5.5.1

definition, 8.1.3, 8.1.4

evaluation process, 8.4.2

with enforcement options, 8.1.9

label-based security, 2.1

labeling functions

ALL_CONTROL and NO_CONTROL, 8.1.8

and CHECK_CONTROL, 8.3.1

and LABEL_DEFAULT, 8.1.6.2, 8.2.1

and LABEL_DEFAULTlLABEL_DEFAULT option

and labeling functions, 8.1.6.1

and LABEL_UPDATE, 8.1.6, 8.1.6.3

and LBACSYS, 8.2.2

creating, 8.2.3

example, 8.2.1

how they work, 8.2.2

importing unlabeled data, 12.2.2.4

in force, 8.1.6

inserting data, 6.5.3

introduction, 3.5.7

override manual insert, 8.3.2

specifying, 8.2.4

testing, 8.2.2

UPDATE, 8.4.3

using, 8.2.1

with enforcement options, 8.1.9, 8.1.9

labels, E.8.4, E.8.9

administering, 2.6

altering, E.3.1

and performance, 3.5.2.1

checking if a data label, E.8.4

checking if changed, E.8.1

creating, E.3.2

data and user, 2.5

deleting, E.3.3

finding greatest lower bound, E.8.5

finding least upper bound, E.8.6

finding tags and types of, F.1.2.5

merging, 6.4.5

non-comparable, B.1.2

relationships between, B.1

restoring default for session, E.5.12

SA_LABEL_ADMIN package, E.3

SA_LABEL_ADMIN.ALTER_LABEL procedure, E.3.1

SA_LABEL_ADMIN.CREATE_LABEL procedure, E.3.2

SA_LABEL_ADMIN.DROP_LABEL procedure, E.3.3

SA_SESSION.LABEL function, E.5.5

SA_SESSION.MAX_READ_LABEL function, E.5.7

SA_SESSION.MAX_WRITE_LABEL function, E.5.8

SA_SESSION.MIN_WRITE_LABEL function, E.5.10

SA_SESSION.RESTORE_DEFAULT_LABELS, E.5.12

SA_SESSION.SET_LABEL procedure, E.5.14

SA_SESSION.SET_ROW_LABEL procedure, E.5.18

SA_USER_ADMIN package, E.7

SA_USER_ADMIN.SET_USER_LABELS procedure, E.7.16

SA_UTL.CHECK_LABEL_CHANGE function, E.8.1

SA_UTL.GREATEST_LBOUND function, E.8.5

SA_UTL.LEAST_UBOUNDfunction, E.8.6

SA_UTL.SET_LABEL procedure, E.8.9

saving default session label, E.5.16

setting row label, E.5.18

syntax, 2.4, 5.3.8

valid, 2.4, 5.3.9, 6.1.2

with inverse groups, 13.3.3

LBAC_LABEL data type, 8.2.2

LBACSYS

export, 12.1.1

import, 12.1.1

login, 5.9.1

LBACSYS default user account

about, 4.2

best practice guideline, 4.2

enabling, 4.2

LBACSYS schema

and labeling functions, 8.2.2

creating additional databases, 12.5

data dictionary tables, 12.4.1

export restriction, F.2.3

LEAST_UBOUND function, 6.4.5

inverse groups, 13.8.13

levels

about, 5.3.2

altering levels, E.2.4

creating, E.2.7

definition, 2.3.2, 5.3.2

deleting, E.2.10

example, 2.3.2, 5.3.2

finding, F.1.2.6

SA_COMPONENTS.ALTER_LEVEL procedure, E.2.4

SA_COMPONENTS.CREATE_LEVEL procedure, E.2.7

SA_COMPONENTS.DROP_LEVEL procedure, E.2.10

SA_SESSION.MAX_LEVEL function, E.5.6

SA_SESSION.MIN_LEVEL function, E.5.9

SA_USER_ADMIN.SET_LEVELS procedure, E.7.13

setting authorizations, 3.3.1.1, 5.4.2

logging into Oracle Label Security

from Cloud Control, 4.3.1

from SQL*Plus, 4.3.2

login

Cloud Control, 5.9.1

LBACSYS, 5.9.1

M

materialized views, 11.6.1.1, 11.6.3.2

Max Read Groups, 13.3.3.2

Max Write Group, 13.3.3.2, 13.3.3.2

MERGE_LABEL function, 6.4.5, 6.4.5

multitenant container databases. See CDBs

N

NO_CONTROL option, 8.1.3, 8.1.4, 8.1.8

NOAUDIT procedure, E.1.6

NUMBER data type, 6.1.1

O

object privileges

and Oracle Label Security privileges, 3.5.4

and trusted stored program units, 3.5.6, 9.1.1

OCI interface, B.3

OCI_ATTR_APPCTX_LIST, B.3

OCI_ATTR_APPCTX_SIZE, B.3

OCIAttrSet, B.3, B.3

OCIParamGet, B.3

OLS_DOMINATED_BY function, B.1.3.5

OLS_DOMINATES function, B.1.3.2

OLS_GLBD function, 6.4.4.2

OLS_GREATEST_LBOUND function, 6.4.4.2

OLS_LABEL_DOMINATES function

about, B.1.3.3

in Data Redaction policies, B.1.3.3

in Database Vault policies, B.1.3.3

OLS_LEAST_UBOUND function, 6.4.4.1

OLS_LUBD function, 6.4.4.1

OLS_STRICTLY_DOMINATED_BY function, B.1.3.6

OLS_STRICTLY_DOMINATES function, B.1.3.4

OptionsA, C.2.1

Oracle Data Redaction

using OLS_LABEL_DOMINATES function with, B.1.3.3

Oracle Database Vault

using OLS_LABEL_DOMINATES function with, B.1.3.3

Oracle Enterprise Manager

administering labels, 2.6

Oracle Internet Directory

configuring OLS after switchover to standby database, 7.11.5

integration with OLS, 1.8.1

OID with Oracle Data Guard, 7.11.5

Oracle Label Security

about, 7.1

administrator duties in, 7.9

bootstrapping databases, 7.10

configuring, about, 7.2

configuring, permission for, 7.2.1

configuring, steps, 7.2.2

integrated capabilities of, 7.5

PL/SQL procedures for policy administrators, 7.14

policy attributes in, 7.6

profiles, about, 7.4

provisioning profiles, about, 7.11.2

provisioning profiles, changing database connection information, 7.11.4

provisioning profiles, managing, 7.11.3

removing OID-enabled OLS from database, 7.3

restrictions on new data label creation, 7.8

security roles and permitted actions, 7.12

subscribing policies in, 7.7

superseded PL/SQL statements, 7.13

synchronizing database with OID, 7.11.1

un-registering database, 7.2.3

Oracle Label Security

about, 1.1

benefits, 1.2

privileges required to use, 1.3

registering, 4.1.1

Oracle Label Security (OLS)

integration with Oracle Internet Directory, 1.8.1

Oracle Label Security data dictionary views

about, F.1.2

ALL_SA_AUDIT_OPTIONS, F.1.2.1

ALL_SA_COMPARTMENTS, F.1.2.2, F.1.2.16

ALL_SA_DATA_LABELS, F.1.2.3, F.1.2.17

ALL_SA_GROUPS, F.1.2.4, F.1.2.18

ALL_SA_LABELS, F.1.2.5, F.1.2.20

ALL_SA_LEVELS, F.1.2.6, F.1.2.21

ALL_SA_POLICIES, F.1.2.7

ALL_SA_PROG_PRIVS, F.1.2.8

ALL_SA_SCHEMA_POLICIES, F.1.2.9

ALL_SA_TABLE_POLICIES, F.1.2.10

ALL_SA_USER_LABELS, F.1.2.12

ALL_SA_USER_LEVELS, F.1.2.13

ALL_SA_USER_PRIVS, F.1.2.14

ALL_SA_USERS, F.1.2.11

DBA_OLS_STATUS, F.1.2.32

DBA_SA_AUDIT_OPTIONS, F.1.2.15

DBA_SA_GROUP_HIERARCHY, F.1.2.19

DBA_SA_POLICIES, F.1.2.22

DBA_SA_PROG_PRIVS, F.1.2.23

DBA_SA_SCHEMA_POLICIES, F.1.2.24

DBA_SA_TABLE_POLICIES, F.1.2.25

DBA_SA_USER_COMPARTMENTS, F.1.2.27

DBA_SA_USER_GROUPS, F.1.2.28

DBA_SA_USER_LABELS, F.1.2.29

DBA_SA_USER_LEVELS, F.1.2.30

DBA_SA_USER_PRIVS, F.1.2.31

DBA_SA_USERS, F.1.2.26

USER_SA_SESSION, F.1.2.33

Oracle Label Security profiles, 7.4

ORDER BY clause, 6.4.1, 6.4.2

P

packages

Oracle Label Security, 1.7.1

SA_AUDIT_ADMIN, E.1

SA_COMPONENTS, E.2

SA_LABEL_ADMIN, E.3

SA_POLICY_ADMIN, E.4

SA_SESSION, E.5

SA_SYSDBA, E.6

SA_USER_ADMIN, E.7

SA_UTL, E.8

trusted stored program units, 9.1

partitioning, 6.1.2.2, 12.4.4

PDBs

Oracle Label Security, 1.8.2

performance, Oracle Label Security

ANALYZE command, 12.4

indexes, 12.4.2

label tag strategy, 12.4.3

partitioning, 12.4.4

READ privilege, 3.5.2.1

PL/SQL

recreating labels for import, 12.2.2.2

SA_UTL package, 9.3, E.8

trusted stored program units, 9.1

pluggable databases. See PDBs

policies

enforcement guidelines, 8.1.9

enforcement options, 3.5.7, 6, 8.1.1, 8.1.2, 8.1.9

finding for current user, F.1.2.7

finding for entire database, F.1.2.22

finding information about schema policies, F.1.2.9

finding information about table policies, F.1.2.10

finding privileges for program units, F.1.2.8

multiple, 2.2, 6.1.2, F.2.2

OID subscription, E.4.8

OID unsubscription, E.4.9

privileges, 3.5.4, E.7.17

SA_POLICY_ADMIN package, E.4

SA_POLICY_ADMIN.POLICY_SUBSCRIBE procedure, E.4.8

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE procedure, E.4.9

SA_USER_ADMIN.SET_PROG_PRIVS procedure, E.7.14

setting program unit privileges, E.7.14

terminology, 5.6.1

policies, schema

altering, E.4.1

applying, E.4.2

deleting, E.4.10

disabling, E.4.4

enabling, E.4.6

SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY procedure, E.4.1

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY procedure, E.4.2

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY policy, E.4.6

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY procedure, E.4.10

policies, schema, disabling

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY procedure, E.4.4

policies, table

applying, E.4.3

deleting, E.4.11

disabling, E.4.5

enabling, E.4.7

SA_POLICY_ADMIN.APPLY_TABLE_POLICY procedure, E.4.3

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY procedure, E.4.5

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY procedure, E.4.7

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY procedure, E.4.11

policy label column

indexing, 12.4.2

inserting data when hidden, 6.5.4

introduction, 6.1.1, 6.1.1

retrieving, 6.3.2.1

retrieving hidden, 6.3.2.2

storing label tag, 2.4, 5.3.9

policy management

altering policies, E.6.1

creating policies, E.6.2

deleting policies, E.6.4

disabling policies, E.6.3

enabling policies, E.6.5

SA_SYSDBA package, E.6

SA_SYSDBA.ALTER_POLICY procedure, E.6.1

SA_SYSDBA.CREATE_POLICY procedure, E.6.2

SA_SYSDBA.DISABLE_POLICY procedure, E.6.3

SA_SYSDBA.DROP_POLICY policy, E.6.4

SA_SYSDBA.ENABLE_POLICY procedure, E.6.5

policy_DBA role, 2.2, E.3, E.7.17

about, 1.4

auditing policy_DBA role users, E.1.1

how to use, 1.4

required for Data Pump import operations, 12.2.2.1.2

required for label management, E.3

required for Oracle Label Security auditing, E.1

required for SA_USER_ADMIN.SET_PROG_PRIVS procedure, E.7.14

required for SA_USER_ADMIN.SET_USER_PRIVS procedure, E.7.17

predicates

access mediation, 3.5.7

errors, 8.6.1

label tag performance strategy, 12.4.3

multiple, 8.6.2

used with policy, 8.6.1

privileges

COMPACCESS, 3.5.1, 3.5.2.3, 5.5.1

FULL, 3.5.1, 3.5.2.2, 3.5.2.4, 5.5.1

Oracle Label Security, 1.3, 3.5.1

PROFILE_ACCESS, 3.5.1, 3.5.2.4, 5.5.1

program units, 3.5.6

READ, 3.5.1, 3.5.2.1, 5.5.1

row label, 3.5.3

SA_USER_ADMIN.SET_USER_PRIVS procedure, E.7.17

trusted stored program units, 9.2.5

WRITEACROSS, 3.5.1, 3.5.3, 3.5.3.3, 5.5.1

WRITEDOWN, 3.5.1, 3.5.3, 3.5.3.2, 3.5.6, 5.5.1

WRITEUP, 3.5.1, 3.5.3, 3.5.3.1, 5.5.1

PROFILE_ACCESS privilege, 3.5.1, 3.5.2.4, 5.5.1

program units

finding policy privileges for, F.1.2.8

policy privileges, E.7.14

propagated, D.1

R

RAC, D.1

read access

algorithm, 3.4.2, 3.5.2.2

introduction, 3.4.1.1

read label, 3.3.2

READ privilege, 3.5.1, 3.5.2.1, 5.5.1

READ_CONTROL option

algorithm, 3.4.2

and CHECK_CONTROL, 8.1.6.3

and child rows, 8.3.3

definition, 8.1.3, 8.1.4

referential integrity, 8.4.4

with other options, 8.1.9

with predicates, 8.6.1

reading down, 3.4.2

referential integrity, 8.3.3, 8.4.4, 8.5

registering Oracle Label Security, 4.1.1

releasability, 13.2

remote users, 11.2

REPADMIN account, 11.6.1.1, 11.6.3.1, 11.6.3.2

replication

materialized views (snapshots), 11.6.1.1, 11.6.3.2, 11.6.4

with Oracle Label Security, 11.6, 11.6.1.2

replication administrator, 11.6.3.1

restrictions, Oracle Label Security, F.2

row labels

default, 3.3.1.2, 3.3.1.3, 3.3.2, D.2, E.5, E.5.18, E.8.10

example, 3.2.3

finding current, E.8.8

in distributed environment, 11.3

inserting, 6.5.1

LABEL_DEFAULT option, 6.5, 8.1.6.1

privileges, 3.5.3

restoring, E.5.12

SA_USER_ADMIN.SET_ROW_LABEL procedure, E.7.15

SA_UTL.NUMERIC_ROW_LABEL function, E.8.8

SA_UTL.SET_ROW_LABEL procedure, E.8.10

saving defaults, E.5.16

setting, E.5.18, E.8.10

setting compartments, E.7.10

setting for current database session, E.8.10

setting for user’s initial use, E.7.15

setting groups, E.7.12

setting levels, E.7.13

understanding, 3.2.2

updating, 3.5.3

viewing, E.8.8

S

SA_AUDIT_ADMIN

procedures, listed, E.1

SA_AUDIT_ADMIN PL/SQL package

about, E.1

SA_AUDIT_ADMIN.AUDIT procedure, E.1.1

SA_AUDIT_ADMIN.AUDIT_LABEL procedure, E.1.2

SA_AUDIT_ADMIN.AUDIT_LABEL_ENABLED procedure, E.1.3

SA_AUDIT_ADMIN.CREATE_VIEW procedure, E.1.4

SA_AUDIT_ADMIN.DROP_VIEW procedure, E.1.5

SA_AUDIT_ADMIN.NOAUDIT procedure, E.1.6

SA_AUDIT_ADMIN.NOAUDIT_LABEL procedure, E.1.7

SA_COMPONENTS

procedures, listed, E.2

SA_COMPONENTS package, E.2

SA_COMPONENTS PL/SQL package

about, E.2

SA_COMPONENTS.ALTER_COMPARTMENT procedure, E.2.1

SA_COMPONENTS.ALTER_GROUP procedure, E.2.2

SA_COMPONENTS.ALTER_GROUP_PARENT procedure, E.2.3

SA_COMPONENTS.ALTER_LEVEL procedure, E.2.4

SA_COMPONENTS.CREATE_COMPARTMENT procedure, E.2.5

SA_COMPONENTS.CREATE_GROUP procedure, E.2.6

SA_COMPONENTS.CREATE_LEVEL procedure, E.2.7

SA_COMPONENTS.DROP_COMPARTMENT procedure, E.2.8

SA_COMPONENTS.DROP_GROUP procedure, E.2.9

SA_COMPONENTS.DROP_LEVEL procedure, E.2.10

SA_LABEL_ADMIN

procedures, listed, E.3

SA_LABEL_ADMIN PL/SQL package

about, E.3

SA_LABEL_ADMIN.ALTER_LABEL procedure, E.3.1

SA_LABEL_ADMIN.CREATE_LABEL procedure, E.3.2

SA_LABEL_ADMIN.DROP_LABEL procedure, E.3.3

SA_POLICY_ADMIN

procedures, listed, E.4

SA_POLICY_ADMIN PL/SQL package

about, E.4

SA_POLICY_ADMIN.ALTER_SCHEMA_POLICY procedure, E.4.1

SA_POLICY_ADMIN.APPLY_SCHEMA_POLICY procedure, E.4.2

SA_POLICY_ADMIN.APPLY_TABLE_POLICY procedure, E.4.3

SA_POLICY_ADMIN.DISABLE_SCHEMA_POLICY procedure, E.4.4

SA_POLICY_ADMIN.DISABLE_TABLE_POLICY procedure, E.4.5

SA_POLICY_ADMIN.ENABLE_SCHEMA_POLICY procedure, E.4.6

SA_POLICY_ADMIN.ENABLE_TABLE_POLICY procedure, E.4.7

SA_POLICY_ADMIN.POLICY_SUBSCRIBE procedure, E.4.8

SA_POLICY_ADMIN.POLICY_UNSUBSCRIBE procedure, E.4.9

SA_POLICY_ADMIN.REMOVE_SCHEMA_POLICY procedure, E.4.10

SA_POLICY_ADMIN.REMOVE_TABLE_POLICY procedure, E.4.11

SA_SESSION

procedures and functions, listed, E.5

SA_SESSION PL/SQL package

about, E.5

SA_SESSION.COMP_READ function, E.5.1

SA_SESSION.COMP_WRITE function, E.5.2

SA_SESSION.GROUP_READ function, E.5.3

SA_SESSION.GROUP_WRITE function, E.5.4

SA_SESSION.LABEL function, E.5.5

SA_SESSION.MAX_LEVEL function, E.5.6

SA_SESSION.MAX_READ_LABEL function, E.5.7

SA_SESSION.MAX_WRITE_LABEL function, E.5.8

SA_SESSION.MIN_LEVEL function, E.5.9

SA_SESSION.MIN_WRITE_LABEL function, E.5.10

SA_SESSION.PRIVS function, E.5.11

SA_SESSION.RESTORE_DEFAULT_LABELS procedure, E.5.12

SA_SESSION.ROW_LABEL function, E.5.13

SA_SESSION.SA_USER_NAME function, E.5.15, E.5.15

SA_SESSION.SAVE_DEFAULT_LABELS procedure, E.5.16

SA_SESSION.SET_ACCESS_PROFILE procedure, E.5.15, E.5.17

SA_SESSION.SET_LABEL procedure, E.5.14

and SA_SESSION.RESTORE_DEFAULT_LABELS, E.5.12

SA_SESSION.SET_ROW_LABEL procedure, E.5.18

SA_SYSDBA

procedures, listed, E.6

SA_SYSDBA PL/SQL package

about, E.6

SA_SYSDBA.ALTER_POLICY procedure, E.6.1

SA_SYSDBA.CREATE_POLICY procedure, E.6.2

SA_SYSDBA.DISABLE_POLICY procedure, E.6.3

SA_SYSDBA.DROP_POLICY procedure, E.6.4

SA_SYSDBA.ENABLE_POLICY procedure, E.6.5

SA_USER_ADMIN package

administering stored program units, E.7.14

overview, 2.2

procedures, listed, E.7

SA_USER_ADMIN PL/SQL package

about, E.7

SA_USER_ADMIN.ADD_COMPARTMENTS procedure, E.7.1

SA_USER_ADMIN.ADD_GROUPS procedure, E.7.2

SA_USER_ADMIN.ALTER_COMPARTMENTS procedure, E.7.3

SA_USER_ADMIN.ALTER_GROUPS procedure, E.7.4

SA_USER_ADMIN.DROP_ALL_COMPARTMENTS procedure, E.7.5

SA_USER_ADMIN.DROP_ALL_GROUPS procedure, E.7.6

SA_USER_ADMIN.DROP_COMPARTMENTS procedure, E.7.7

SA_USER_ADMIN.DROP_GROUPS procedure, E.7.8

SA_USER_ADMIN.DROP_USER_ACCESS procedure, E.7.9

SA_USER_ADMIN.SET_COMPARTMENTS procedure, E.7.10

SA_USER_ADMIN.SET_DEFAULT_LABEL procedure, E.7.11

SA_USER_ADMIN.SET_GROUPS procedure, E.7.12

SA_USER_ADMIN.SET_LEVELS procedure, E.7.13

SA_USER_ADMIN.SET_PROG_PRIVS procedure, E.7.14

SA_USER_ADMIN.SET_ROW_LABEL procedure, E.7.15

SA_USER_ADMIN.SET_USER_LABELS procedure, E.7.16

SA_USER_ADMIN.SET_USER_PRIVS procedure, E.7.17

SA_UTL package

dominance functions, B.1.3.7

overview, 9.3

procedures and functions, listed, E.8

SA_UTL PL/SQL package

about, E.8

SA_UTL.CHECK_LABEL_CHANGE function, E.8.1

SA_UTL.CHECK_READ function, E.8.2

SA_UTL.CHECK_WRITE function, E.8.3

SA_UTL.DATA_LABEL function, E.8.4, E.8.4

SA_UTL.GREATEST_LBOUND function, E.8.5

SA_UTL.LEAST_UBOUND function, E.8.6

SA_UTL.NUMERIC_LABEL function, E.8.7

SA_UTL.NUMERIC_ROW_LABEL function, E.8.8

SA_UTL.SET_LABEL procedure, E.8.9

SA_UTL.SET_ROW_LABEL procedure, E.8.10

schemas

applying policies to, 8.1.9, E.6.1

default policy options, E.6.2

restrictions on shared, F.2.5

session labels

changing, E.5.14

computed, 3.3.2

distributed database, 11.3

example, 3.2.3

finding, E.8.7

OCI interface, B.3

restoring to default, E.5.12

SA_UTL.SET_LABEL, E.8.9

saving defaults, E.5.16

setting compartments, E.7.10

setting groups, E.7.12

setting user initial, E.7.11

understanding, 3.2.1

sessions

compartments readable by user, E.5.1

compartments writeable by user, E.5.2

finding current OLS user, E.5.15

finding row label, E.5.13

finding security attributes for, F.1.2.33

finding session label number, E.8.7

finding session privileges, E.5.11

SA_SESSION package, E.5

SA_SESSION.COMP_READ function, E.5.1

SA_SESSION.COMP_WRITE function, E.5.2

SA_SESSION.GROUP_READ function, E.5.3

SA_SESSION.GROUP_WRITE function, E.5.4

SA_SESSION.LABEL function, E.5.5

SA_SESSION.MAX_LEVEL function, E.5.6

SA_SESSION.MAX_READ_LABEL function, E.5.7

SA_SESSION.MAX_WRITE_LABEL function, E.5.8

SA_SESSION.MIN_LEVEL function, E.5.9

SA_SESSION.MIN_WRITE_LABEL function, E.5.10

SA_SESSION.PRIVS, E.5.11

SA_SESSION.RESTORE_DEFAULT_LABELS procedure, E.5.12

SA_SESSION.ROW_LABEL function, E.5.13

SA_SESSION.SA_USER_NAME function, E.5.15

SA_SESSION.SAVE_DEFAULT_LABELS procedure, E.5.16

SA_SESSION.SET_ACCESS_PROFILE procedure, E.5.17

SA_SESSION.SET_LABEL procedure, E.5.14

SA_USER_ADMIN.SET_COMPARTMENTS procedure, E.7.10

SA_USER_ADMIN.SET_DEFAULT_LABEL procedure, E.7.11

SA_USER_ADMIN.SET_LEVELS procedure, E.7.13

SA_UTL.SET_LABEL procedure, E.8.9

SA_UTL.SET_ROW_LABEL procedure, E.8.10

saving default session label, E.5.16

setting label for, E.8.9

setting OLS privileges for user, E.5.17

setting row label for, E.8.10

SET_ACCESS_PROFILE procedure, F.2.5

SET_DEFAULT_LABEL procedure

inverse groups, 13.7.1, 13.8.7

SET_GROUPS procedure

inverse groups, 13.8.5

SET_LABEL procedure

definition, E.5

inverse groups, 13.7.2, 13.8.11

on remote database, 11.3

SET_PROG_PRIVS function, E.7.14

SET_ROW_LABEL procedure, 13.7.2.1, 13.7.2.2, E.5

inverse groups, 13.7.1, 13.7.2, 13.8.8, 13.8.12

SET_USER_LABELS procedure

inverse groups, 13.8.6

setting label for database session, E.8.9

shared schema restrictions, F.2.5

SQL*Loader, 12.3

STRICTLY_DOMINATED_BY function, B.1.3.10

STRICTLY_DOMINATES function, B.1.3.8

SYS account

policy enforcement, 8.1.10

SYS_CONTEXT

and labeling functions, 8.2.2

variables, B.3

SYSDBA privilege, 10.2

system privileges, 3.5.4, 3.5.5, 3.5.6

T

table rows

checking if user can read, E.8.2

checking if user can write to, E.8.3

SA_UTL.CHECK_READ function, E.8.2

SA_UTL.CHECK_WRITE function, E.8.3

TO_DATA_LABEL function, 6.5.5, E.3.2

TO_LBAC_DATA_LABEL function, 8.2.2

TO_LBAC_DATA_LABEL function, example of using, E.8.9

triggers, 8.2.2

trusted program units

about, 5.5.1

trusted stored program units

creating, 9.2.1

error handling, 9.2.5

example, 9.1.2

executing, 9.2.5

introduction, 9.1

privileges, 3.5.6, 9.2.5

re-compiling, 9.2.3

replacing, 9.2.4

U

unified audit trail, 10.4

UPDATE_CONTROL option, 8.1.3, 8.1.4, 8.4.2

updating labeled data, 8.4

user authorizations, E.7.7

adding for compartments, E.7.1

adding for groups, E.7.2

altering for compartments, E.7.3

altering for groups, E.7.4

compartments, 3.3.1.2, 5.4.4

dropping for all compartments, E.7.5

dropping for all groups, E.7.6

dropping for specified groups, E.7.8

groups, 3.3.1.3, 5.4.6

levels, 3.3.1.1, 5.4.2

removing all OLS privileges from user, E.7.9

SA_USER_ADMIN.SET_USER_PRIVS procedure, E.7.17

understanding, 3.3, 5.4.1

USER_SA_SESSION view, F.1.2.33

users

finding label-specific information of, F.1.2.12

finding level-specific information of, F.1.2.13

finding policy-specific privileges of, F.1.2.14

finding privileges of OLS users, F.1.2.11

LBACSYS default user account, 4.2

utilities

SA_UTL package, E.8

V

views

access mediation, 3.5.5

ALL_SA_AUDIT_OPTIONS, F.1.2.1

ALL_SA_COMPARTMENTS, F.1.2.2

ALL_SA_GROUPS, F.1.2.4

ALL_SA_LABELS, F.1.2.3, F.1.2.5

ALL_SA_LEVELS, F.1.2.6

ALL_SA_POLICIES, F.1.2.7

ALL_SA_PROG_PRIVS, F.1.2.8

ALL_SA_SCHEMA_POLICIES, F.1.2.9

ALL_SA_TABLE_POLICIES, F.1.2.10

ALL_SA_USER_LABELS, F.1.2.12

ALL_SA_USER_LEVELS, F.1.2.13

ALL_SA_USER_PRIVS, F.1.2.14

ALL_SA_USERS, F.1.2.11

DBA_OLS_STATUS, F.1.2.32

DBA_SA_AUDIT_OPTIONS, F.1.2.15

DBA_SA_COMPARTMENTS, F.1.2.16

DBA_SA_DATA_LABELS, F.1.2.17

DBA_SA_GROUP_HIERARCHY, F.1.2.19

DBA_SA_GROUPS, F.1.2.18

DBA_SA_LABELS, F.1.2.20

DBA_SA_LEVELS, F.1.2.21

DBA_SA_POLICIES, F.1.2.22

DBA_SA_PROG_PRIVS, F.1.2.23

DBA_SA_SCHEMA_POLICIES, 8.1.11, F.1.2.24

DBA_SA_TABLE_POLICIES, 8.1.11, F.1.2.25

DBA_SA_USER_COMPARTMENTS, F.1.2.27

DBA_SA_USER_GROUPS, F.1.2.28

DBA_SA_USER_LABELS, F.1.2.29

DBA_SA_USER_LEVELS, F.1.2.30

DBA_SA_USER_PRIVS, F.1.2.31

DBA_SA_USERS, F.1.2.26

W

write access

algorithm, 3.4.3, 3.5.2.2

introduction, 3.4.1

write label, 3.3.2

WRITE_CONTROL option

algorithm, 3.4.3

definition, 8.1.3, 8.1.4

introduction, 8.1.7.2

LABEL_UPDATE, 8.1.7.2

with INSERT, UPDATE, DELETE, 8.1.7.2

with other options, 8.1.9

WRITEACROSS privilege, 3.5.1, 3.5.3.3, 5.5.1, 8.1.3, 8.1.6.2, 8.4.2

WRITEDOWN privilege, 3.5.1, 3.5.3.2, 3.5.6, 5.5.1, 8.1.3, 8.1.6.2, 8.4.2

WRITEUP privilege, 3.5.1, 3.5.3, 3.5.3.1, 5.5.1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2015, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.