Comprehensive data protection for all workloads
Post Reply
flavor4real
Expert
Posts: 205
Liked: 5 times
Joined: Nov 22, 2010 7:57 pm
Full Name: DS
Contact:

FIPS compliant algorithms

Post by flavor4real »

Hello,
does Veeam 6.0 utilize FIPS compliant algorithms?

thanks,
foggy
Veeam Software
Posts: 21070
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: FIPS compliant algorithms

Post by foggy »

If you are talking about web UI (Enterprise Manager), then yes, it became FIPS compliant starting right from v6. And we haven't received any FIPS-related issues reports after its release.
Gostev
Chief Product Officer
Posts: 31521
Liked: 6699 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: FIPS compliant algorithms

Post by Gostev »

All encryption algorithms we are using throughout all components of our product are FIPS compliant.
brupnick
Expert
Posts: 196
Liked: 13 times
Joined: Feb 05, 2011 5:09 pm
Full Name: Brian Rupnick
Location: New York, USA
Contact:

Re: FIPS compliant algorithms

Post by brupnick »

Gostev, is this new as of 6.5? I know that there were FIPS issues with 6.1.
Gostev
Chief Product Officer
Posts: 31521
Liked: 6699 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: FIPS compliant algorithms

Post by Gostev »

I have not heard of any FIPS-related issues since we addressed the last one in 6.0
brupnick
Expert
Posts: 196
Liked: 13 times
Joined: Feb 05, 2011 5:09 pm
Full Name: Brian Rupnick
Location: New York, USA
Contact:

Re: FIPS compliant algorithms

Post by brupnick »

I only ask because I ran into some FIPS issues with VBR 6.1. See Veeam legacy ticket 5219644.
Gostev
Chief Product Officer
Posts: 31521
Liked: 6699 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: FIPS compliant algorithms

Post by Gostev »

From the support case, I see that you were getting the following error:

Code: Select all

This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
The fact that implementation of something is not a part of Windows Platform does not automatically render it non-compliant ;) lots of pieces of our product (everything that has to deal with Linux) are not a part of Windows Platform... however, all encryption algorithms we are using are still FIPS-compliant. We had to do research this a couple of years ago and look at every encryption algorithm we are using from this standpoint.
brupnick
Expert
Posts: 196
Liked: 13 times
Joined: Feb 05, 2011 5:09 pm
Full Name: Brian Rupnick
Location: New York, USA
Contact:

Re: FIPS compliant algorithms

Post by brupnick »

This might just be an issue of semantics, but seeing as how VBR is required to run on Windows, if the solution is to set "System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing" to disabled, then I interpret this as VBR not being FIPS compliant (otherwise, why would I have to disable this?).
Gostev
Chief Product Officer
Posts: 31521
Liked: 6699 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: FIPS compliant algorithms

Post by Gostev » 1 person likes this post

You make a valid point too. But, you will only get this error when using Multi-OS FLR wizard, due to its reliance on Linux appliance - that's the point I was trying to make. All product's functionality that runs on Windows solely will not throw this message. Outside Windows, we do use encryption algorithms which are not "Windows Platform FIPS validated", but are still FIPS-compliant.
brupnick
Expert
Posts: 196
Liked: 13 times
Joined: Feb 05, 2011 5:09 pm
Full Name: Brian Rupnick
Location: New York, USA
Contact:

Re: FIPS compliant algorithms

Post by brupnick »

That makes complete sense. Thank you, as always, for the clarification.
Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 65 guests