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.
Topics:
Oracle Data Pump enables high-speed movement of data and metadata from one database to another.
Topics:
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.
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.
Oracle Data Pump enables high-speed movement of data and metadata from one database to another.
Topics:
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.
You can use the impdp 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.
Before you can use the Import utility with Oracle Label Security, you must prepare the import database.
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:
"Duties of Oracle Label Security Administrators" for information about the policy_DBA role
DBA_SA_LABELSThe 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 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.
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.
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.
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, then you must first create the table in the import database.
HIDE option. This adds the policy label column to the table as a hidden column.IGNORE=Y. Setting the IGNORE parameter to Y ignores errors during import.HIDE option.SQL*Loader moves data from external files into tables in Oracle Database.
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
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.
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, you must 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 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 |
|---|---|
|
|
Hidden column loaded with tag value of data directly from data file |
|
|
Hidden column loaded with character value of data from data |
|
|
Same as in |
|
|
Hidden column not mapped to input |
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
You can 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 improves Oracle Label Security performance.
See Oracle Database SQL Language Reference for the ANALYZE syntax.
Running ANALYZE on application tables improves the application SQL performance.
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:
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 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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 |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
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.
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) );
You can create and configure additional databases after you install Oracle Label Security.
Topics:
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.
If you initially chose custom install, but did not install label security, you can install and configure label security using either process described in this section.
See Also:
For a complete discussion of Oracle database creation, see Oracle Database Administrator's Guide
You can configure Oracle Label Security if the database was installed with the label security schema is in the seed database.
You should be aware of how to manage Oracle Label Security upgrades and downgrades.
Topics:
Oracle provides a set of preprocess scripts that you can use to perform upgrade and downgrade operations.
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 provides a preprocess script that you must run before you perform an upgrade.
Topics:
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.
WARNING:
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.
You can run the Oracle Label Security preprocess script before upgrading.
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 provides a preprocess script that you must run before you downgrade.
Topics:
If you are downgrading from an Oracle Database 12c Release 1 (12.1) or later database that users Oracle Label Security (OLS) or Oracle Database Vault, then you must do the following: run the OLS preprocessing 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 processing 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 you can view them by directly accessing the SYSTEM.PREDWG_AUD$ table until the downgrade completes. Once the downgrade completes, the SYSTEM.PREDWG_AUD$ table is permanently deleted. At this point, all audit records are available for viewing in the DBA_AUDIT_TRAIL data dictionary view.