While recording a script with the EveryStep Recorder, you may need to provide some sensitive information, such as passwords or credit card details.
The EveryStep Recorder automatically hides passwords and converts them to password context parameters in the scripts.
Also, you can mask any string data in the script editor by manually converting them into context parameters. However, context parameters can be converted back to a string form and viewed by other account users while editing the script. Therefore, it can be unsafe to store sensitive details in the EveryStep script body in clear form, especially when other users have access to the script in your Dotcom-Monitor account.
Dotcom-Monitor supports securing any type of sensitive information in EveryStep scripts. Configure a central Secure Vault and store sensitive data as encrypted variables in Crypt name-value collections. Once configured the Crypt Variables can be used in EveryStep scripts to protect sensitive information from being disclosed. For more details, see Working with Crypt Variables in EveryStep Recorder.
You may also want to temporarily pause session recording when it comes to sensitive web content instead. You can do this by using the Video Recording function of the desktop version of EveryStep Scripting Tool. Alternatively, you can hide specific regions on the recorded video. The masked region will stay hidden on the captured video of web app transactions for all users of your Dotcom-Monitor account. To find more about using these advanced features of the EveryStep Scripting Tool, see Managing Video Recording in EveryStep Recorder to Protect PII.