---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Configure data anonymization clone request

# Configure data anonymization clone request {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Data privacy clone integration is configured using a PostClone script to create and
execute data privacy jobs for configured policies on the target. After running the script,
users will see de-identified data and will not have access to the original data.

## Vorbereitungen

The data privacy PostClone script is installed with the activation of the data privacy plugin (sn_dp_store_app). See [Activate data privacy](https://servicenow-prod.fluidtopics.net/F6K~Vtd8PnzHs7A8FAhr5Q "Data Privacy includes data classification and anonymization and is installed from the ServiceNow Store.") for details.

Role required: data_privacy_clone_processor, data_privacy_admin, and admin

## Prozedur

1. Activate the data privacy plugin (sn_dp_store_app) on the source instance.  
   The data privacy PostClone script is installed.
2. Elevate to the data_privacy_admin role.  
   For details on role elevation, see [Elevate to a privileged
   role](https://servicenow-prod.fluidtopics.net/QSMW4UNBg6bevZDKAPGT2Q "The base system admin can elevate to a privileged role to have access to the features of High Security Settings.").
3. Navigate to System SecurityData PrivacyAnonymization.
4. Select Create new policy.  
   See [Create anonymization policies](https://servicenow-prod.fluidtopics.net/cjeA6Iv3iokuLqFccEWtvw "Configure an anonymization policy to specify which techniques are used when anonymizing your data.") for details.
5. Select Data tables or columns.
6. Select Create.
7. Enter a name and select a data class.
8. Select to Activate the policy during cloning.
9. Select the policy order to run if there are multiple clone policies.  
   A data privacy job for Postclone configuration with a higher Application Order might start before another job of lower order, if the job with the higher order does not involve any table related to other lower order job.
10. Select Continue.
11. Complete the policy configuration and publish the policy.
12. Back up data privacy configurations.
13. Schedule the anonymization job.  
    See [Create anonymization job](https://servicenow-prod.fluidtopics.net/_0xIHi5JElrnN_jshtgZyA "Configure a data privacy job on your production instance to use anonymized data on your non-production instance for user and data class jobs.")for details.
14. As the data privacy admin, submit a clone request.
{#dps-configure-data-anonymization-clone__steps_kf1_44k_dwb}

## Ergebnisse

The data privacy PostClone script executes on the target Instance and The PostClone
script creates a data privacy federated job record on the target instance. The
federated job creates and executes a data privacy job for each post-clone policy, in
Application Order, on the target instance.​The backup source is cloned to the target
Instance. Data privacy PostClone script creates and executes data privacy jobs for
configured policies on the target instance.

The elevated data privacy clone processor can log on to the target instance and
monitor the post-clone federated job state on the dp_federated_job.list and
dp_job.list​.