立即与支持人员聊天
与支持团队交流

Classification Module 6.1.1 - User Guide

Introduction Deploying Classification in Identity Manager Configuring Classification: Taxonomies, Categories, and Rules
An Overview of Classification Configuration Steps Required to Implement Classification Creating Taxonomies Setting Up Manual Categorization Implementing Rules for Automated Categorization Classifying Resources When Do Categorization and Classification Occur? Importing and Exporting Taxonomies Working with a Taxonomy XML File Managing the Life Cycle of Taxonomies and Categories Advanced Rule Applications
Working with Categorized Resources Appendix A: PowerShell cmdlets Appendix B: Oracle Configuration Appendix C: Classifying Data with Data Governance Templates Glossary

Editing a Taxonomy

You can change the name and description of a taxonomy. If you plan to apply the top node of a taxonomy as a category, you may want to change the category parameters. For more information, see Editing a Category.

To edit the name and description of a taxonomy using the Web Portal

  1. Select Governed Data | Taxonomy Manager |Categorizations.
  2. Locate the row containing the taxonomy, and click Edit.
  3. Select the top node of the tree, and click Edit.
  4. Modify the name and description.
  5. Click Apply Changes.
    You can change any of the category parameters as well. For details, see Working with Categories.

To edit the name and description of a taxonomy using PowerShell

  1. If you do not know the required taxonomy ID, run the Get-QTaxonomies cmdlet, using the following mandatory parameter:
    1. ServerAddress
      Provide the name of the computer hosting the Data Governance server, and the port. Enter in the form computername:port number. The default port is 8723.
    2. Locate your desired taxonomy, and note or copy the taxonomy ID.
  2. Run the Set-QTaxonomy cmdlet, with the following parameters:
    1. ServerAddress (mandatory)
      Provide the name of the computer hosting the Data Governance server, and the port. Enter in the form computername:port number. The default port is 8723.
    2. TaxonomyID (mandatory)
      The ID of the taxonomy you want to change.
    3. Name (optional)
      The new name of the taxonomy.
    4. Description (optional)
      The updated description of the taxonomy.
      You can change any of the category parameters as well. For details, see Working with Categories.

Deleting a Taxonomy

If a taxonomy has been in use, you should use extreme care deleting it. When you delete a taxonomy:

  • All categories in the taxonomy will be deleted.
  • If resources were categorized using any category in the taxonomy, the association will be removed.
  • Any policy that included a category from the taxonomy may no longer have the expected results.
  • Attestations involving any category from the taxonomy may no longer work.
  • Reports will no longer include data about any category in this taxonomy.

If you choose to delete a taxonomy, you should ensure that the proper administrators are notified so that policies, attestations and reports can be modified as needed. A safer approach may be to delete categories individually. For more information, see Deleting a Category.

To delete a taxonomy using the Web Portal

  1. Select Governed Data | Taxonomy Manager | Categorizations.
  2. Locate the row containing the taxonomy, and click Delete.
  3. In the confirmation dialog box, select the I still want to delete this taxonomy check box.
  4. Click Delete Taxonomy.

To delete a taxonomy using PowerShell

  1. Make sure you know the ID of the taxonomy. For more information, see Finding a Taxonomy or Category ID using PowerShell.
  2. Run the Remove-QTaxonomy cmdlet with the following mandatory parameters:
    1. ServerAddress (mandatory)
      Provide the name of the computer hosting the Data Governance server, and the port. Enter in the form computername:port number. The default port is 8723.
    2. TaxonomyID (mandatory)
      The ID of the taxonomy you want to delete.
  3. Press enter to confirm the deletion.

Working with Categories

The proper configuration of a category is integral to a properly working system. Categories should be created and refined in test mode, and published when they are ready to be used in your production environment. Deployments of categories should be properly managed. See Managing the Life Cycle of Taxonomies and Categories for more information.

You can work with categories using the following methods:

Each category has a number of settings, which have an impact on the category’s behavior. In the table below, the parameter in brackets is the PowerShell and XML equivalent of the setting in the Web Portal.

Category Parameters (PowerShell/XML equivalent in brackets)
Setting
Category Risk
(Risk)
Indicates the relative risk of the category. This is then used to determine how a resource is classified. For more information, see Classifying Resources.
Publish this category
(IsPublished)
Makes a category available for manual categorization. You must also enable this for automation to work. Publish a category only when you are ready for business owners to have access to it.
A subcategory must have a published parent category. If you publish a subcategory, and the parent is unpublished, the action is ignored.
Allow this category to be used by the automated system
(IsAutomaticClassificationEnabled)
You can make a category available to the automated system. Automated categorization is based on the rules associated with the category, so you should associate rules and test the category before automating it.
Automation will not take place until the category is published as well.
Govern using this category
(CausesGovernance)
When a category that causes governance is applied to a resource, that resource is placed under governance and can be managed using the Web Portal. Resources under governance can be subject to polices and attestations.
Mutually Exclusive
(IsMutuallyExclusive)
The mutually exclusive setting applies to the children of a category. If a category has been defined as mutually exclusive, only a single subcategory can be applied to a resource. For example, consider a category in your taxonomy called PHI, which has three subcategories: Level 1, Level 2, Level 3. If PHI is set to mutually exclusive, you can only apply one of the subcategories. To create an entire taxonomy that is mutually exclusive, so that only one category can be assigned from the taxonomy, all parent categories must be set to mutually exclusive. When more than one category could be applied to resource based on the associated rules and category threshold, the category with the highest combined rule score is applied.
Strictly Ordered
(IsStrictlyOrdered)
Strictly ordered is a special kind of mutual exclusivity, in which the order of the subcategories has meaning. When more than one category could be applied to a resource based on the associated rules and category threshold, the category closest to the parent category will be applied. For example, if your categories are Level 1 and Level 2, in that order, and either category could be applied, in this case Level 1 will be applied.
If you are planning on creating a strictly ordered category, ensure you enter the subcategories in the correct order. There is no way to change the order of subcategories once they are created. You must delete and recreate the categories, including assigning the rules.
Threshold The threshold value determines whether a category is applied. Combined with the weights given to a rule when you associate it, and the match strength of the rule, the threshold gives you control over what causes a resource to have a category applied. For a full explanation, see How Rules Affect Categorization. The default threshold is one. Note: The threshold can only be modified through PowerShell commands.

Creating a Category

The first step is to create the category, giving it a name and description. A category requires a parent, which can either be the top level taxonomy node or any category in the taxonomy. By default, new categories:

  • are created in test mode, and are not available for manual or automated categorization.
  • do not cause governance.
  • have a threshold value of one.
  • are not mutually exclusive.
WARNING! You should not change these values without fully understanding the implications for your classification system. For more information, see Working with Categories.

Each category can only belong to a single taxonomy. If you have created a category in one taxonomy and want to move it to another, see Moving a Category.

To create a category using the Web Portal

  1. Select Governed Data | Taxonomy Manager | Categorizations.
  2. Locate the row containing the taxonomy, and click Edit.

    -OR-

    Create a taxonomy as outlined in Creating a Taxonomy, and click Save.
  3. Select the parent category of the new category.
    To create a first level category, select the top level taxonomy node, otherwise select the category under which you want the new category to appear.
  4. Click Add.
  5. Provide a name and optional description for the category.
  6. Set the risk value.
  7. If you are ready to allow business owners to use this category to manually categorize their resources, select the Publish this category check box.
    You should not make a new category available for use by the automated system, as this requires the association of rules to the category. For more information, see Associating Rules to Categories.
  8. If you want all resources categorized with this category to be governed, select the Govern using this category check box.
  9. If you plan to allow only one subcategory of this category to be applied to a resource, select the Mutually Exclusive check box.
  10. If you want the order of the categories to influence categorization, select the Strictly Ordered check box.
  11. Click Save.
    Your new category appears nested under its parent category.

To create a category using PowerShell

  1. Make sure you know the ID of the parent category. For more information, see Finding a Taxonomy or Category ID using PowerShell.
    To create a first level category, provide the ID of the taxonomy root.
  2. Run the Add-QCategory cmdlet with the following mandatory parameters:
    1. ServerAddress
      Provide the name of the computer hosting the Data Governance server, and the port. Enter in the form computername:port number. The default port is 8723.
    2. ParentCategoryID
      To create a first level category, use the ID of the parent taxonomy, otherwise use the ID of the category under which you want the new category to appear.
    3. Name
  3. Additionally, you can use the following optional parameters:
    1. Description
    2. Risk
    3. CausesGovernance
      By default, this is set to $false.
    4. IsPublished
      You should only set this to $true if you are ready for business owners to use this category for manual categorization.
      You should not set IsAutomatedClassificationEnabled to $true, as automated categorization requires the association of rules to the category. For more information, see Associating Rules to Categories.
    5. IsMutuallyExclusive
      Set this to $true if you plan to allow only one subcategory of this category to be applied to a resource.
    6. IsStrictlyOrdered
      Set this to $true if you plan to allow only one subcategory of this category to be applied to a resource, and you want this based on the order of the categories.
    7. Threshold
      The default value is one. You should not change this unless you have already determined the rules you plan to associate and the weights for these rules. For more information, see How Rules Affect Categorization.
      Note: The threshold can only be modified through PowerShell commands.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级