How to configure to use FIPS compliant cryptographic algorithm while using CyberArk.TPC.exe on CPM v10.9?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

How to configure to use FIPS compliant cryptographic algorithm while using CyberArk.TPC.exe on CPM v10.9?

L2 Linker

On CPM v10.9 (Windows 2012 R2), FIPS is enforced thru GPO.

 

For Unix accounts we would like to use CyberArk.TPC.exe as CPM plugin, but is giving following errors while verifying the passwords:

 

On CPM#1 (in Sandbox env):

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

  at System.Security.Cryptography.SHA256Managed..ctor()

 

On CPM#2(in DEV env):

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

  at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()

 

Note: The difference between both errors is invocation of "MD5CryptoServiceProvider" vs "SHA256Managed" on two different CPM servers.

 

We need to find out whether TPC is using internal configuration to invoke\use crypto providers? OR is it using default OS .NET framework configuration settings?

 

If it is using OS security providers configuration settings, then how we can configure so TPC will use FIPS compliant algorithm.

 

We have already tested that PMTerminal.exe is working fine with FIPS enabled.

 

Thanks,

-Dinesh

5 REPLIES 5

L6 Presenter

@Dinesh Jadhav​ 

 

Are the targets already FIPS compatible?

 

See: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/security_guide/sect-se...

 

Check sshd_config:

Protocol 2

Ciphers aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc

Macs hmac-sha1,hmac-sha2-256,hmac-sha2-512

 

The above basically switches off weak ciphers and algorithms that are not FIPS compliant.

I'm checking internally what needs to be done on the CPM.

L2 Linker

Hello Che,

 

Currently the target linux servers are not FIPS compatible. But it is possible that thru STIGs we will enable FIPS on those servers.

 

The CPM server(s) in both environments are having FIPS enabled thru GPO.

 

We will appreciate if you can advise the configuration on CPM servers to use FIPS compliant algorithms for TPC.

 

Thanks in advance.

 

Regards,

-Dinesh

L4 Transporter

Hi @Che-Wing Cheung​ ,

 

Did you manage to get any update internally for CPM?

Other than disabling the FIPS completely?

L3 Networker

See article knowledge article 7619 to disable FIPS just for TPC plugin.

L3 Networker

See article knowledge article 7619 to disable FIPS just for TPC plugin.

  • 1095 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!