As an Administrator, I want to avoid a JVM dump or define in memory encryption of data

Use case is for security reasons, avoid dumping the JVM memory etc.

Ideas:

• We may think of a new storage type, delete temporarily unencrypted objects after their usage, eventually involve GC.
• Or even think of a pluggable data policy on the row level. (e.g. custom plug-in checks at first time of object creation if this field (e.g. defined by the field name or other criteria defined by the custom plug-in) is defined as sensitive data and need to be encrypted).