The General Data Protection Regulations (GDPR) is the new European Union (EU) data protection regulations which go into effect May 25th, 2018. Under the GDPR individuals have certain rights to their personal data. They can make requests to exercise those rights to the data controller, and the controller must respond within 1 month. It is expected that the controller will verify the identity of the requestor.
There are four primary types of GDPR requests:
- Export – Request for a copy of all personal data about an individual held by this controller and any related processors. Must be in a commonly accepted portable data format.
- Update – Request to rectify inaccurate personal data.
- Delete – Request to remove all personal data about an individual from our systems. Can be initiated by an individual or by a revocation of consent process. Includes burden of proof. (Ideally follow a delete with an export to show no remaining data)
- Hold – Request to halt processing of personal data but not delete that data.
When Directory Sync Pro for Active Directory is installed, the data associated with the application is hosted locally within the client’s environment. The client has full control over this data. By default, the user and configuration data is stored in the SQL database called, “DirectorySyncPro_<date>”. It is assumed the operator has the proper administrative SQL Permissions to execute the following methods outlined.
SQL Tables containing User data:
[DirectorySyncPro_<Date>].[dbo].[BT_Person]
Unique Key Look-up Columns:
[SAMAccountName]
[TargetSAMAccountName]
[TargetUserPrincipalName]
[OriginalSAMAccountName]
[OriginalUserPrincipalName]
[UserPrincipalName]
If user data is used for matching (e.g. SAMAccountName, UserPrincipalName, etc.) then those values will also appear in one of the following columns:
[MatchValue1]
[MatchValue2]
[MatchValue3]
[MatchValue4]
[DirectorySyncPro_<Date>].[dbo].[BT_Groups]
Unique Key Look-up Columns:
[MatchValue1]
[MatchValue2]
[MatchValue3]
[MatchValue4]
Be aware that data can be mapped to different Internal Fields (table columns) depending on customer specific configuration, so just about any SQL column could theoretically contain user data if so configured. For example, if SAMAccountName has been mapped to Custom001 or to any other Internal Field selectable in the mappings. Therefore this process should be undertaken by someone knowledgeable about the schema and attribute mappings in use. It may also be helpful to work with Support when completing these requests if you are not comfortable with the database.
All user data within Directory Sync Pro for Active Directory is derived from the source Active Directory Forest configured in the product. Therefore, the authoritative source of any user related data stored in Directory Sync Pro for Active Directory is Active Directory. Any remediation required from a GDPR request should first be remediated in Active Directory or the source feeding Active Directory. Once that user data is updated in the source directory, running a new discovery within the product will update those values as well.
The following sections will provide guidance on fulfilling the 4 primary GDPR request types.
1. Exports – Request for a copy of all personal data about an individual held by this controller and any related processors. Must be in a commonly accepted portable data format.
For the purposes of this document, using PowerShell with the SQLPS Module is the recommended method to refine the results of the output. One may export any SQL Query result to a CSV file. Below is an example script to do so. Replace the variables to conform to your environment.
Import-Module sqlps
$SQLquery='SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]'
$result=invoke-sqlcmd -query $SQLquery -serverinstance <servername> -database <dbname>
$result |export-csv c:\temp\ExportQueryResults.csv -notypeinformation
2. Updates – Request to rectify inaccurate personal data.
As previously stated, all user data within Directory Sync Pro for Active Directory is derived from the source Active Directory Forest configured in the product. Therefore, the authoritative source of user data is Active Directory. Any remediation required from a GDPR request should first be remediated in Active Directory or the source feeding Active Directory.
If editing the user data within SQL is still required, using any SQL editor such as SQL Server Management Studio, run an update command against one or more columns for one or more records. Below are examples to accomplish this. Note however, that any new discovery will update the values based on the source Active Directory.
Update multiple columns for a single record:
UPDATE [DirectorySyncPro_<Date>].[dbo].[BT_Person]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE userPrincipalName='<Unique ID>'
UPDATE [DirectorySyncPro_<Date>].[dbo].[BT_Person]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE userPrincipalName='<Unique ID>'
Update multiple columns for multiple records:
UPDATE [DirectorySyncPro_<Date>].[dbo].[CMTEUP_Person]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE DistinguishedName='<Unique ID>' OR DistinguishedName='<Unique ID>'
UPDATE [DirectorySyncPro_<Date>].[dbo].[CMTEUP_PersonADData]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE userPrincipalName='<Unique ID>' OR userPrincipalName='<Unique ID>'
Update multiple columns for multiple records using a list:
UPDATE [DirectorySyncPro_<Date>].[dbo].[BT_Person]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE DistinguishedName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
UPDATE [DirectorySyncPro_<Date>].[dbo].[BT_Person]
SET <Column1 Name> = <New Value1>, <Column2 Name> = <New Value2>
WHERE userPrincipalName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
3. Deletes – Request to remove all personal data about an individual from our systems. Can be initiated by an individual or by a revocation of consent process. Includes burden of proof. (Ideally follow a delete with an export to show no remaining data.)
Using any SQL editor such as SQL Server Management Studio, run a Delete command against one or more records. Below are examples to accomplish this. However, as previously stated, if the user is not deleted in the source Active Directory during any subsequent new discovery the user will be re-populated into SQL. The only way to truly remove the data is to delete the source user or delete the entire SQL database when it is no longer required.
Delete a single record then verify:
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName='<Unique ID1>'
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName='<Unique ID1>'
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName='<Unique ID1>'
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName='<Unique ID1>'
Delete multiple records then verify:
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName='<Unique ID1>' OR SAMAccountName='<Unique ID2>'
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName='<Unique ID1>' OR SAMAccountName='<Unique ID2>'
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName='<Unique ID1>' OR userPrincipalName='<Unique ID2>'
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName='<Unique ID1>' OR userPrincipalName='<Unique ID2>'
Delete multiple records then verify:
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE SAMAccountName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
DELETE FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
SELECT * FROM [DirectorySyncPro_<Date>].[dbo].[BT_Person]
WHERE userPrincipalName IN ('<Unique ID1>', '<Unique ID2>', '<Unique ID3>')
4. Holds – Request to halt processing of personal data but not delete that data.
This can also be accomplished using the product interface. Halting a user from processing can be achieved using the Blacklist feature.
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center
