We have a requirement from the customer that if anyone gets access to the database, then all data that contains personal information, It should be encrypted when they select the call, they will not see anything in the clear text. Now there is no problem for these strings, but what about the bitters? (Which can potentially be quite large (many 100 MB))
When you make a selected call, then you become strong anyway, do any hackers read the bytes in any way and It is possible to get sensitive information, how is the structure of the object mapped without any?
Because if this is the case then I think we should encrypt those bytes, even if they might be too big. (I'm guessing adding encryption to make them big)
First of all, the encryption is not normally Increase the size except the next multicolve of the block size (e.g., 128 bit limit) of the encryption algorithm.
Second, yes, if the data is left clear, then an attacker could possibly understand at least a few times it very fast.
Third, this is a big problem with all (with the most cryptology) key storage and distribution. At some point you have to decrypt the data, and (often) the easiest way to attack is to find a way to recover that key. For two of your main options, the user needs to enter a key, or some type of protected storage (such as smart cards) to enter the key, or to use smart card readers on the client computer.
Depending on the database you are using, it may be able to do much for you in a reasonable number to help in complying with privacy requirements (eg Sarbens-Oxley in the US) There are some types of line-level or even column-level encryption.
Comments
Post a Comment