cryptographic module

[Jose Garcia2]

Hi everyone,

I just upgraded to Utah and crypto module is showing up below the application scope.

We did not have this activated on the previous version.

If there is anyone who may have some knowledge on this and can point me in the right direction

-Is crypto automatically activated in the Utah upgrade

-is this module a requirement? How can I deactivate it?

Please let me know. Thanks... jgarcia

[goeln]

Hi, We are having the same issue after upgrade, do you have any resolution for this ?

[Rajat singh2]

Root Cause: 

When the instance was upgraded to Utah, the Crypto Modules were created because the Security Incident Response plugin was installed and those Crypto Modules get created automatically. -See screenshot

Solution:

If you do not want this module, the best way is to disable the Module Access Policies for the above roles:

https://yourinstance.service-now.com/sys_kmf_crypto_caller_policy_list.do?sysparm_query=crypto_modul...

Hope This Helps

[Supritha Jose]

Hi @Rajat singh2  -

I'm not able to see any screenshot, but I am facing the same issue and I want the Crypto module removed from application picker. 

When trying to access the Module Access Policies, no records are visible, I found only a report view ACL for this module which requires two roles,  both of which are not available, so I'm not sure how to get rid of this.

[Aidarus]

Hi Supritha, 

I'm having the same issue. Did you get any solutions for this issue yet?

I tried to access the Module Access Policies and it is an empty table. 

Please share with us if you found any solution.