Introduction
About this Guide
System Requirements
Minimum Required Permissions
Required Ports
Performance Calculations
Deploying Classification in Identity Manager
Classification Overview
Required Components
Component Workflow
Activating Classification
Configuring Classification: Taxonomies, Categories, and Rules
Install the Classification Components
Enable Classification in the Designer
Identify the Classification Service Account
Deploy the Classification Server
Deploy Classification Workers
Enable and Disable Automatic Classification on Specific Managed Hosts
Enabling Categorization on Folders (Security Index Roots)
Managing the File Types to be Classified
Starting Initial Classification
Upgrade an Agent for Classification
Re-classify Data
Classification Application Roles
Troubleshooting the Classification Deployment
An Overview of Classification Configuration
Steps Required to Implement Classification
Creating Taxonomies
Appendix A: PowerShell Commands
Working with Taxonomies
Implementing Rules for Automated Categorization
Creating a Taxonomy
Importing and Replacing Taxonomies
Editing a Taxonomy
Deleting a Taxonomy
Exporting Taxonomies
Working with Categories
How Rules Affect Categorization
Managing Rules in the Classification System
Classifying Resources
When Do Categorization and Classification Occur?
Managing the Life Cycle of Taxonomies and Categories
Creating a Rule
Editing a Rule
Associating Rules to Categories and Applying Rule Weights
Deleting a Rule
Advanced Rule Applications
Working with Text Extractors
Identifying Text Extractors used within the System
Creating Text Extractors
Validating the Text Extractor
Editing Text Extractors
Removing Text Extractors
Working with Regular Expression Text Extractors
Working with Dictionary Text Extractors
Managing Public Dictionary Text Extractors
Managing Protected Dictionary Text Extractors
Managing Dictionary Text Extractors with PowerShell
Working with Advanced Text Extractors
Testing and Reviewing Automated Classification
Testing a Rule against a Resource
Testing all Rules Against a Resource
Viewing the Text from a Resource
Determining Why Categorizations Were Applied to a Resource
Viewing Categorized Resources
Making a Category Available to the Classification System
Adding the PowerShell Snap-ins
Finding a Taxonomy, Category, or Extractor ID using PowerShell
Deploying the Classification Server and the Classification Worker
Troubleshooting Deployment
Managing Taxonomies
Appendix B: Oracle Configuration
Appendix C: Classifying Data with Data Governance Templates
Available Templates
Appendix D: Creating a Taxonomy to Classify Data
Introduction
Contents
About this Guide
This document has been prepared to assist you in becoming familiar with Quest One Identity Manager Data Governance Edition — Classification Module. This document is for network administrators, consultants, analysts, IT professionals responsible for deploying Data Governance in their organization, and Web Portal users. It provides typical use cases and step-by-step instructions to help you understand how to use Data Governance to secure the unstructured data in your organization.
This guide is supplemented with the Data Governance Edition Deployment Guide, User Guide, and Quick Start Guide, which provides more detailed information about the Data Governance features, and includes instructions to help administrators perform day-to-day administrative activities.
System Requirements
Review the following section to ensure that your system meets the following minimum requirements for the Classification Module.
 |
For complete Quest One Identity Manager system requirements (including those required for the client and the Web Portal), see the Quest One Identity Manager Release Notes. |
Database Server Requirements
- Microsoft SQL Server Standard Edition 2008 Service Pack 3
- Microsoft SQL Server Standard Edition 2008 R2 Service Pack 1
- Microsoft SQL Server 2012 Standard Edition, Service Pack 1 (Compatibility level for databases: SQL Server 2008 (100))
- Oracle database 11g r2 Enterprise Edition version 11.2 (patch level will vary with operating system platform)
- Microsoft Windows Operating Systems: Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2 (32 bit or non-Itanium 64 bit), Windows Server 2012, Windows Server 2012 R2
- 32 GB RAM minimum (128 GB minimum if classification is enabled)
- In addition to Q1IM Database Server requirements, an additional 30GB per million resources
Classification Server Requirements
- Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
- 500 MB of space required for installation, 200 MB space for logs, plus an additional 2 GB per 1 million resources for data processing
- 8 GB RAM
- Quad core CPU
- .NET 3.5 or .NET 4.0
Worker Server Requirements
- Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
- 300 MB of space required for installation, plus an additional 300 MB for logs
- 8 GB RAM
- Quad Core CPU
- .NET 3.5 or .NET 4.0
Classification Agent Host Requirements
- Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2
- 4GB RAM (if hosting multiple agents, 16GB RAM) 100 MB free disk space for every million resources scanned 2 GHz or faster x86 or x64 bit processor (if hosting multiple agents, quad core CPU) .NET 3.5 or .NET 4.0
- Classification enabled local agents are not supported on Windows Server 2003 or Windows Server 2003 R2 operating systems.
- Agents hosts installed on Windows Server 2003 or Windows Server 2003 R2 operating systems are not supported if they are scanning a classification-enabled managed host.
Minimum Required Permissions
The following table lists the required minimum permissions:
| Account | Permissions |
| Classification Identity | All classification services run under this account. - Local Administrator on the Classification Server and Classification Workers - Local Administrator on any agent host - Log On as Service on the Classification Server and Classification Workers - Member of Quest QCS Users local group on the Classification Server and Classification Workers. Note: The group is created and the user is placed in this group automatically during installation. (You should ensure that an existing policy does not change this group.)When Windows Authentication is selected for database connection during the Classification Server installation: - db_owner for ContentService and TopicService databases - dbcreator role for the installation (this role is needed even if databases are pre-created) |
| SQL account for database connection for Classification server | When SQL Authentication selected for database connection during the Classification Server installation:- db_owner for ContentService and TopicService databases - dbcreator role for the installation (this role is needed even if databases are pre-created) |