Abstract: An administrator distributes sensitive data to some trusted agents (third parties) and if one or more of them will leak that sensitive data and found in an unauthorized place (e.g. on the web or somebody’s laptop),then we can catch & prosecute them as per Law. The question may arise in mind, how to deal with such problem? There is a unique key embedded in each copy of the data by distributor before distributing that data to agents and this key remains within data. In some cases, we can also inject “realistic but fake” data records to further improve our chances of detecting leakage and identifying the guilty party. We are using List Significant bit (LSB) [1] steganography concept here to embed the key in the data. So when the distributor finds his secret data at unauthorized place, he will simply take that data and check for the unique key. If the key in that data matches with the key present in his database then the system will display the name of that guilty agent and then he can mark it as invalid user [2].

Keywords: Steganography, LSB [Least Significant Bit], FPS, Watermarks, Message key, Serialized