Post-clone Clean Up Script Execution in Multi-Node Environment (Scrambling Sensitive Data Process)

[Community Alums]

We have sensitive data that we're trying to scramble after the clone is performed, and we're planning to use Post-Clone Cleanup Script to do that. However I wanted to know how and when the post-clone script executes in a multi-node environment. I know that this script runs after the cloning process completes, but does the script run before the cloned node is made available to the users, or it executes after it's already been made available to the end-user?

What we're trying to determine is whether there is a period of time that somebody accessing the environment can access the sensitive data before it's scrambled. For example if the post-clone script takes 2 hours to complete, will users of the instance be able to access the sensitive data until the script finishes?

[Allen Andreas · Accepted solution]

Hi,

The post-clone script process executes as soon as the clone has completed. This would mean the node is "back online" and could be eligible for individuals to connect.

More info just to throw it out there: https://docs.servicenow.com/bundle/rome-platform-administration/page/administer/managing-data/concep...

You may want to submit a ticket to ServiceNow HI/Support for the time between clone completion and beginning of the post-clone script process and then your follow-on question about access availability as I don't think we'd know that on the forums as far as a timing window is concerned.

What I do know, is that I've seen some people add script to their post-clone scripts to disable SSO (for example, the system property for it) and then at the conclusion of the post-clone scripting, reenable SSO). This would prevent your non-local account users from logging in until you were truly ready.

Please mark reply as Helpful/Correct, if applicable. Thanks!