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.

4.8.3 Recommendations<br />

For both <strong>DB2</strong> encryption and the <strong>IBM</strong> Data Encryption Tool, we recommend you move to the<br />

current z990 or z890 hardware, where the hardware-assisted encryption instructions are<br />

available on all processors.<br />

The <strong>IBM</strong> Encryption Tool (row level) per<strong>for</strong>ms generally better than the <strong>DB2</strong> encryption and<br />

decryption (column level). The break<br />

even point varies depending on how many other columns are in the table and their size.<br />

However, per<strong>for</strong>mance is not the only reason to choose one encryption strategy over the<br />

other, as they also vary in function.<br />

Encryption is done be<strong>for</strong>e compression, so compression and encryption cannot be effectively<br />

combined. Encrypted data does not tend to compress very well because repeating<br />

unencrypted characters are no longer repeating after they are encrypted.<br />

Important: Be aware that if you plan to use DRDA encryption, you need the PCIXCC<br />

function on your z990, because the hardware requires it.<br />

4.9 Row level security<br />

<strong>DB2</strong> recognized the need <strong>for</strong> more granular security of <strong>DB2</strong> data and introduced support <strong>for</strong><br />

Row Level Security in V8. Multilevel security support in z/<strong>OS</strong> 1.5 and RACF Security Server<br />

1.5, in conjunction with <strong>DB2</strong> V8, simplify row level security implementation and management<br />

significantly.<br />

In this section we first introduce Row Level Security, then describe the per<strong>for</strong>mance impact of<br />

Row Level security on <strong>DB2</strong> workloads.<br />

Security is becoming increasingly important in the past few years. Row level access control is<br />

increasingly critical. Many customers need to extend the granularity from table level to row<br />

level, so that an individual user is restricted to a specific set of rows. Good examples are Web<br />

hosting companies that need to store data from multiple customers into a single subsystem,<br />

database or table.<br />

In the past, views have been used to hide data. They can subselect data to provide only<br />

certain columns or fields. By creating a view and granting privileges on it, you can give<br />

someone access to only a specific combination of data. However, the application tends to<br />

become much more complex when views are used in this way. Separating the data into<br />

different databases or base tables has also been used to provide more granular security.<br />

<strong>DB2</strong> recognizes this need and introduces support <strong>for</strong> Row Level Security in V8. Multilevel<br />

security (MLS) support in z/<strong>OS</strong> 1.5 and RACF Security Server 1.5, in conjunction with <strong>DB2</strong><br />

V8, simplify row level security implementation and management significantly.<br />

Multilevel security is a security policy that allows the classification of data and users based on<br />

a system of hierarchical security levels, combined with a system of non-hierarchical security<br />

categories. A multilevel-secure security policy prevents unauthorized individuals from<br />

accessing in<strong>for</strong>mation at a higher classification than their authorization (read-up), and<br />

prevents individuals from declassifying in<strong>for</strong>mation (write-down).<br />

You can use MLS <strong>for</strong> multiple purposes in <strong>DB2</strong>:<br />

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

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

Saved successfully!

Ooh no, something went wrong!