The security administrator uses a security policy to define criteria that determine who has write access and who has read access to individual rows and individual columns of tables. Use options in the Security Policy editor to create a security policy and identify security label components for the security policy.
To define a DB2 LUW security policy
The DB2 LUW Security Policy Editor opens.
Note: Click New on the toolbar to create a security policy. Use the Enter filter text text box to filter a large list of names to locate the one you want to work with.
Specifies the name of the security policy.
Generates DDL for this object during Forward Engineering.
Specifies the action that is taken when a user is not authorized to write the specified security label that is provided in the INSERT or UPDATE statement issued against a table that is protected with this security policy. Valid values are: Override and Restrict.
Specifies to use group authorizations in the security policy. Select from the drop-down list; valid values are True and False.
Specifies to use role authorizations in the security policy. Select from the drop-down list; valid values are True and False.
The Security Policy Editor closes.
Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |