Field encryption in Servicenow

[snowuser111]

Hello Experts,

Need your help again.

We are planning to encrypt certain fields which contains sensitive data so i have gone through many threads for this encryption, well in WIKI read that encryption.But still new to this area and need guidance how to proceed. Can someone help me how do i proceed :

Say example: in Incident table , we have a field credit card number...and this needs to be encrypted.

Can anyone please guide me the simple way how to proceed .

Thanks

[Chuck Tomasi · Accepted solution]

You have a couple options in this.

Use an encrypted text field

You might also want to look at Edge Encryption if you want to ensure the data is encrypted at rest as well.

Understanding Edge Encryption

[snowuser111]

Hi Chuck,

You got my concern thanks.

Yes exactly I was wondering that instead of field level can we use a common encrypted layer between servicenow and users as generic so that we don't have to maintain and monitor what upcoming sensitive fields are about to be come in ServiceNow each time down the line and prevent the operational activity and update each time new fields come in.

SO is the answer "Edge Encryption"     Chuck?.

Is edge encryption a layer which does this job and fulfills the encryption layer between users and servicenow instance....

If you can please guide me i will go through it more thoroughly...

Thanks

[snowuser111]

HI,

Can anyone suggest please, looking for a encrypted layer , is that possible or feasible, a complete layer between the users and data before inserting to servicenow?

Thanks

[Chuck Tomasi]

Hi,

Edge encryption simply encrypts the data at rest (in the database.) That means that only the customer can see the data when going through the Edge proxy. Not even ServiceNow support can see the encrypted data in a clear form.

As new fields are created, you still need to define whether that field is going to be encrypted or not. It's not a case of "encrypt all new fields from here on out." You wouldn't want that as it can have serious implications on things like reference fields or choice lists as the scripts running on the platform would not function with encrypted values. So you have to choose whether a field is encrypted or not.