Data Management:Permission application

Prerequisites

You are a DMS administrator, a database administrator (DBA), or a security administrator.

Basic configuration items

On the Access apply tab, eight basic configuration items are provided:

• [Instance-permission application] default approval Template: By default, this approval template takes effect if you do not specify different approval processes for instance permission applications at different risk levels under the Validation for Instance Permission Application checkpoint. In the Change Configuration Item dialog box, you can click Switch Approval Template and change the approval process of the default approval template. For more information, see the "Modify the default approval template" section of the Data change topic.

• [DB-permission application] default approval Template: By default, this approval template takes effect if you do not specify different approval processes for database permission applications at different risk levels under the Database Permission Application Validation checkpoint.

• Table-permission request default approval Template: By default, this approval template takes effect if you do not specify different approval processes for table permission applications at different risk levels under the Table Permission Application Validation checkpoint.

• [Programmable object-permission application] default approval Template: By default, this approval template takes effect if you do not specify different approval processes for programmable object permission applications at different risk levels under the Programmable object verification checkpoint.

• [Field-permission application] default approval Template: By default, this approval template takes effect if you do not specify different approval processes for sensitive field permission applications at different risk levels under the Sensitive Field Application Validation checkpoint.

• Line-permission application default approval Template: By default, this approval template takes effect if you do not specify different approval processes for row permission applications at different risk levels under the Line permission application verification checkpoint.

• [Owner-application] default approval template (when the resource has no Owner): By default, this approval template takes effect if you do not specify different approval processes for data ownership applications at different risk levels under the Owner Application Validation checkpoint and the data involved in the application has no owner.

• [Owner-application] default approval template (when the resource has an Owner): By default, this approval template takes effect if you do not specify different approval processes for data ownership applications at different risk levels under the Owner Application Validation checkpoint and the data involved in the application has one or more owners.

Checkpoints

When you submit a ticket to apply for permissions, DMS checks whether the ticket conforms to rules that are specified under checkpoints. The ticket can be submitted only after DMS determines that the ticket conforms to all rules that are specified under checkpoints. On the Access apply tab, seven checkpoints are supported:

• Owner Application Validation: allows you to specify approval processes or constraints for Instances-OWNER, Table-OWNER, and Database-OWNER tickets.

• Validation for Instance Permission Application: allows you to specify approval processes or constraints for Instances-Performance and Instances-Login tickets.

• Database Permission Application Validation: allows you to specify approval processes or constraints for Database-Permission tickets.

• Table Permission Application Validation: allows you to specify approval processes or constraints for Table-Permission tickets.

• Programmable object verification: allows you to specify approval processes or constraints for Programmable Object tickets.

• Sensitive Field Application Validation: allows you to specify approval processes or constraints for Sensitive Column-Permission tickets.

• Line permission application verification: allows you to specify approval processes or constraints for Row-Permission tickets.

Factors and actions

• A factor is a predefined variable in DMS. You can use factors to obtain the context to be validated by security rules. The context includes SQL statement categories and database names. A factor name consists of the prefix @fac.and the display name of the variable. Each tab of the Security Rules tab provides different factors for different checkpoints. The following table describes the factors that are provided for the checkpoints on the Access apply tab.

  Factor	Description
  @fac.env_type	The type of the environment. The value is the display name of the environment type, such as DEV or PRODUCT. For more information, see Change the environment type of an instance.
  @fac.schema_name	The name of the database.
  @fac.perm_apply_duration	The period of time during which the requested permissions are valid. Unit: hours.
  @fac.column_security_level	The security level of the field. Valid values: sensitive confidential inner
  @fac.perm_type	The types of the requested permissions. A list of strings is returned, such as ['CORRECT','EXPORT']. Valid values: QUERY EXPORT CORRECT LOGIN PERF The @fac.perm_type factor can be used together with the @fun.listEqualIgnoreOrder function to evaluate the types of the requested permissions in a ticket. For example, the @fun.listEqualIgnoreOrder(@fac.perm_type, ['QUERY']) function is used to evaluate whether only the query permissions are requested.

• An action in a security rule is an operation that DMS performs when the IF condition in the rule is met. For example, DMS can forbid the submission of a ticket, select an approval process, approve a ticket, or reject a ticket. An action in a security rule shows the purpose of the security rule. An action name consists of the prefix @act.and the display name of the operation. Each tab of the Security Rules tab provides different actions for different checkpoints. The following table describes the actions that are provided for the checkpoints on the Access apply tab.

  Action	Description
  @act.forbid_submit_order	Forbids a ticket from being submitted.
  @act.do_not_approve	Specifies the ID of an approval template. For more information, see Configure approval processes.
  @act.choose_approve_template
  @act.choose_approve_template_with_reason

Security rule templates

DMS provides you with a large number of predefined security rule templates. You can use the templates or modify the templates based on your business requirements. The following table describes the security rule templates that are provided on the Access apply tab.

Create a security rule

1. Log on to the DMS console V5.0.

2. Move the pointer over the icon in the upper-left corner and choose All functions > Security and Specifications > Security Rules.

   Note

   If you use the DMS console in normal mode, choose Security and Specifications > Security Rules in the top navigation bar.

3. On the Security Rules tab, find the security rule set that you want to manage and click Edit in the Actions column.

4. On the Details page, click the Access apply tab in the left-side pane.

5. On the Access apply tab, click Create Rule next to Actions.

6. In the Create Rule - Access apply dialog box, set the parameters that are described in the following table.

   Parameter	Description
   Checkpoints	Required. The checkpoint for which you want to create the security rule. On the Access apply tab, seven checkpoints are provided: Owner Application Validation Validation for Instance Permission Application Database Permission Application Validation Table Permission Application Validation Programmable object verification Sensitive Field Application Validation Line permission application verification
   Template Database	Optional. The template that you want to use to create the security rule. DMS provides a large number of security rule templates. After you select a checkpoint, you can click Load from Template Database and select a template as required. For more information about the available templates, see Security rule templates.
   Rule Name	Required. The name of the custom security rule. If you load a security rule from a template, the rule name is automatically entered.
   Rule DSL	Required. The DSL statement that you want to use to configure the security rule. For more information, see DSL syntax for security rules. If you load a security rule from a template, the DSL statement is automatically entered.

7. Click Submit.

8. By default, the security rule that you create is in the Disabled state. Click Enable in the Actions column.

9. In the Prompt message, click OK.