---
sourceDocument: Brazil Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-security

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Cloning and Secrets Management

# Cloning and Secrets Management {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Learn how to reconfigure secrets groups and client secrets groups after a clone.
After you clone an instance, your secrets groups and client secrets groups may require reconfiguration to operate as expected.
{#cloning-and-secrets-mgmt__table_qz1_l2f_w1c__entry__2}

| Secrets group origin | Behavior after a clone |
|-|-|
| Original instance secrets groups from the target instance | Works as expected after manually importing the missing cryptographic module. See [Exporting and importing data via XML](https://www.servicenow.com/docs/access?context=c_ExportAndImportXMLFiles&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). |
| Original client secrets groups from target instance | Works as expected after manually importing the missing cryptographic module. See [Exporting and importing data via XML](https://www.servicenow.com/docs/access?context=c_ExportAndImportXMLFiles&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US). |
| Cloned instance secrets groups from source instance | Doesn't work unless manually set up |
| Cloned client secrets groups from source instance | Work if manually config sg/identity group/alias/mid |
[ ]

{#cloning-and-secrets-mgmt__table_qz1_l2f_w1c}