Arctera Insight Information Governance User's Guide
- Section I. Introduction
- Section II. Information Governance Workspace
- Navigating the Workspace tab
- Analyzing data using the Workspace views
- Viewing access information for files and folders
- Viewing user activity on files or folders
- About visualizing collaboration on a share
- Viewing access information for users and user groups
- Section III. Information Governance reports
- Using Information Governance reports
- About Information Governance security reports
- Activity Details report
- Permissions reports
- Inactive Users
- Path Permissions
- Permissions Search report
- Creating a Permissions Query Template
- Permissions Query Template actions
- Entitlement Review
- User/Group Permissions
- Group Change Impact Analysis
- Ownership Reports
- About Information Governance storage reports
- About Information Governance custom reports
- Managing reports
- Viewing reports
- Using Information Governance reports
- Section IV. Remediation
- Configuring remediation workflows
- Managing workflow templates
- Creating a workflow using a template
- Managing workflows
- Using the Self-Service Portal
- About the Self-Service Portal
- Managing data
- About managing data using Arctera Enterprise Vault and custom scripts
- Managing permissions
- Configuring remediation workflows
- Appendix A. Command Line Reference
About migrated domains
During the course of operations, a directory service domain can be migrated to another domain. When a directory service domain migrates, the directory service assigns a new SID (Security Identifier) to each user and group from that domain. The original SID of each migrating user or group is added to an attribute called sIDHistory. Thus, sIDHistory attribute keeps track of all the previous SIDs of an object as it migrates from one domain to another.
When Information Governance scans a directory service domain, it fetches the sIDHistory attribute of all the users and groups. If Information Governance finds a user, say A, whose SID is present in the history of another user, say B, it knows that user A has migrated to user B. If user B is itself not contained in the sIDHistory of any other object in the directory service, Information Governance marks B as the latest user that user A has migrated into. Consequently, user A's LatestSID custom attribute points to user B on the Information Governance console. The LatestSID custom attribute links a user or group to its newest migrated version.
While Information Governance scans configured domains, it automatically adds a domain called MigratedSIDs. This domain is used to collect SIDs that are present in sIDHistory of some user or group, but do not belong directly to any object in Information Governance.
For example, if a user test_user in domain test_domain has the SID S-X-X-X-X in the sIDHistory, and there is no user in any directory service domain scanned by Information Governance with that SID, then Information Governance adds a new user test_user#1 in the MigratedSIDs domain with SID S-X-X-X-X and it sets the user's LatestSID custom attribute to test_user@test_domain. When Information Governance adds multiple SIDs from sIDHistory of a user or group to MigratedSIDs domain, it suffixes the display name of the object with #1, #2, #3.
Information Governance considers a user's SID and SID history to compute the effective permissions and to display user activity information. When Information Governance calculates effective permissions of a user, it considers that user's SID and sIDHistory along with the SID and sIDHistory of all the groups that the user is a member of. This emulates the way Windows determines effective permissions.