Well the data is in memory - do you have a concern that another process on the same machine as the Ignite daemon can read it - there might be better ways then encryption to solve it. If you are concerned about swapping to disk then try to reduce the risk and/or encrypt the hard drive.
In the scenario you mentioned - how does the client fetching the data encrypt in memory (if at all). There are some research projects addressing this with additional hardware or complete new ways of accesses, but they are in some cases slow and also it is not always needed. Cf 1) spark research project with sgx (cf amplabs) 2) mit cryptdb (http://css.csail.mit.edu/cryptdb/) > On 13 Dec 2016, at 12:56, voli.sri <volivattam....@gmail.com> wrote: > > Hi, > > Does apache ignite provide for a way to support encryption of data at REST. > > I am looking for a way to transparently encrypt the stored data so as to > ensure the integrity of data. > > I believe such a solution should also have the option to decrypt and return > the data when required. > > I haven't found anything other using SSL/HTTPS in securing the network > connections between nodes in the cluster. > > Has anyone used something similar. Can you please help me on this. > > > Thanks, > Sridhar > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Encyrption-of-Data-at-REST-in-Apache-Ignite-tp9508.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com.
