Triple DES in Password2 fields

[Mira1992]

Hello community,
I just need to consult something.
Customer has received a SN Communication Record: Deprecation of Three-Key Triple DES in Password2 fields

I know Triple DES is Officially Being Retired and customer is asking about the impact to their instance.

According this SN Document it should not be a big deal but I am really not sure as I have no experience with this.
Steps on "How to deprecate 3DES" are quite clear but I just want to be sure.

Would any of you know if this is a big thing which requires big preparations or is it just a simple task?
Customer is on the Washingtond release.
Thanks a lot for any help.

[Mark Manders]

The steps are described. What did they show when you checked on the instance? 

[Dlam]

I was reading this communication record but wonder if any action is required in our Vancouver instance soon to be upgraded to Washington DC Patch 4 Hot Fix 1.

It says: "we are now requiring all customers to select complete deprecation." which refers to the checkboxes in All > System Security > Security Compliance > Password2 Triple DES Deprecation: 

• Tick Do you want to opt-in for 3DES deprecation for password2 fields?
• Untick Do you want to continue using 3DES in legacy password2 fields?

"If you do not take action, the complete deprecation option will be automatically enforced upon upgrade to the Now Platform® Yokohama release, planned for March 2025."

[Mark Manders]

The already extended this to the Zurich Release, so you don't have to do a thing at the moment. Just run the check and if it only returns OOB usage, you can ignore it. ServiceNow will change these on Yokohama and if you have any custom ones, you need to update them before Zurich, but that's a year away, so no impact on your current upgrade.

[Prabhu6]

Hi Mark and Dlam,

I got the same communication email. Now, we have upgraded to Xanadu. After complete depreciation, do they automatically add a new latest feature(KMF) or any action from our end?

Thank you

Prabhu