19.06.2013 Views

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

DB2 UDB for z/OS Version 8 Performance Topics - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

up to eight uppercase alphanumeric or national characters and each SECLABEL profile<br />

specifies the particular combination of:<br />

► A SECLEVEL member<br />

► Zero or more members of the CATEGORY profile that apply to the security label<br />

For example:<br />

RDEFINE SECLABEL L1C12 SECLEVEL(L1) ADDCATEGORY(C1 C2) UACC(NONE)<br />

In addition, RACF has a number of built-in security labels.<br />

► SYSHIGH: Is equivalent to the highest security level defined and covers all categories<br />

defined.<br />

► SYSLOW: Is equivalent to the lowest security level defined and has no categories signed.<br />

It is dominated by all other security labels.<br />

► SYSNONE: Is treated as equivalent to any security label to which it is compared.<br />

SYSNONE, like SYSLOW, should be used <strong>for</strong> data that has no classified data content.<br />

► SYSMULTI: Is treated as equivalent to any defined security label. It is intended to be used<br />

by users <strong>for</strong> access to data that has multilevel data classified.<br />

Assigning security labels<br />

A subject (or user ID) can have more than one security label, but can only use one security<br />

label at a given time. To authorize a subject to use a security label, the security administrator<br />

permits that subject’s user ID to the profile in the RACF SECLABEL resource class <strong>for</strong> the<br />

security label. Do not <strong>for</strong>get to RACLIST REFRESH the SECLABEL class.<br />

PERMIT L1C12 CLASS(SECLABEL) ACCESS(READ) ID(USER01)<br />

The security label that a subject uses at a given time can be assigned in a number of ways.<br />

For example, a TSO/E user can specify a security label on the logon panel, and a batch user<br />

can specify a security label on the JOB statement. The default SECLABEL is defined in the<br />

user’s RACF profile.<br />

A resource can have only one security label. For most types of resources, the security<br />

administrator assigns a security label to each resource in the system that is to be protected by<br />

ensuring that the resource is protected by a profile, and by specifying the security label in the<br />

profile.<br />

For <strong>DB2</strong> row level security, <strong>DB2</strong> maintains the security label in a new column attribute within<br />

the table itself. To implement multilevel security, the DBA adds a column with the security<br />

label data type to an existing table. This is done by defining a column with the AS SECURITY<br />

LABEL attribute. Each row value has a specific SECLABEL. This new column is populated<br />

with security label in<strong>for</strong>mation when data is inserted into the table. Every row can have a<br />

different security label although this is not likely in practice. More likely, the number of distinct<br />

security labels is much smaller than the number of rows in a table.<br />

How Row Level Security works<br />

Briefly, access to tables is controlled by security labels which are assigned to users as well as<br />

to the data. If the security labels of a user and the data are an equivalent level, that user can<br />

access the data.<br />

Dominance<br />

One security label dominates another security label when both of the following conditions are<br />

true:<br />

Chapter 4. <strong>DB2</strong> subsystem per<strong>for</strong>mance 193

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!