Return to Answer

CipherCloud's website now clearly states, here, that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

Update:

Ciphercloud's FAQ indicates that it does word-by-word encryption to support search. From the FAQ:

• How is encrypted data still searchable >

 

CipherCloud provides granular control over the level of encryption and search-ability for specific pieces of information. Data can be encrypted on a per-field or per-word basis with industry standard AES 256-bit encryption.

CipherCloud's website by September 21^th, 2013 clearly states that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

Ciphercloud's FAQ by October 17^th, 2013 indicates that it does word-by-word encryption to support search:

• How is encrypted data still searchable >

CipherCloud provides granular control over the level of encryption and search-ability for specific pieces of information. Data can be encrypted on a per-field or per-word basis with industry standard AES 256-bit encryption.

CipherCloud's website now clearly states, here, that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

Update from ciphercloud.com indicates that Ciphercloud does word-by-word encryption to support search. As noted by others above, this approach is vulnerable to statistical attacks and makes the "encryption" meaningless.

How is encrypted data still searchable > (FAQ Tab)
CipherCloud provides granular control over the level of encryption and search-ability for specific pieces of information. Data can be encrypted on a per-field or per-word basis with industry standard AES 256-bit encryption.

CipherCloud's website now clearly states, here, that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

Update:

Ciphercloud's FAQ indicates that it does word-by-word encryption to support search. From the FAQ:

• How is encrypted data still searchable >

CipherCloud provides granular control over the level of encryption and search-ability for specific pieces of information. Data can be encrypted on a per-field or per-word basis with industry standard AES 256-bit encryption.

CipherCloud's website now clearly states, here, that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

CipherCloud's website now clearly states, here, that CipherCloud DOES NOT use homomorphic encryption.

This also states that CipherCloud DOES NOT implement 1:1 mapping or ECB mode in any customer deployment. Other statements are next to acknowledging that CipherCloud's early demos did that, citing the will to illustrate the functionality, features that where not yet implemented, and necessity to avoid disclosure of technology not yet patented.

I'm also seeing that CipherCloud now "wholeheartedly apologize" for some of the chilling effect of the DMCA takedown notice brought by its legal team.

I'm eager to see a description of the feature more precise than "recognized standard for cloud information protection"; and in particular, for the (reverse-)proxy setup in front of a database application, what kind of restriction (if any) there is on searchability of terms enciphered without 1:1 mapping.

Update from ciphercloud.com indicates that Ciphercloud does word-by-word encryption to support search. As noted by others above, this approach is vulnerable to statistical attacks and makes the "encryption" meaningless.

How is encrypted data still searchable > (FAQ Tab)
CipherCloud provides granular control over the level of encryption and search-ability for specific pieces of information. Data can be encrypted on a per-field or per-word basis with industry standard AES 256-bit encryption.