Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Data encryption for activity variables

Log in to subscribe to topics and get notified when content changes.

Data encryption for activity variables

You can protect sensitive data passed from Orchestration activities by encrypting input and output variables.

The system never stores encrypted variables as clear text. If the MID Server is used to fulfill the activity, the corresponding ECC Queue's input payload is encrypted if an encrypted output variable is defined in the template. Output variables passed to a downstream activity as input variables maintain their encryption throughout processing.

Inputs that require data encryption come from one of these sources:
  • Workflows: These inputs are provided through the Workflow Editor and must be in the password2 format for two-way encryption.
  • Service catalog requests: These input values are provided to an activity as encrypted variables from a service catalog item.
  • GlideRecord: These are variables attached to any ServiceNow table. The source column in the table must be a password2 type variable.
  • Activity outputs: These are variables passed as outputs from one activity to a downstream activity as inputs, through the data bus.
  • Empty string: The system allows you to define encrypted input variables but never pass a value into the variable.