Considering Database Security
IDEA already provides some safeguards for data that you work with. For example, you can't modify the original data in a database. It's possible to add new fields of your own data, extract the data to a new location, and perform other manipulations, but the original data is pretty much inaccessible except for reading. That means that someone with ill intent can't contaminate the original data—at least, not without a whole lot of effort that's well outside the programming capabilities of most people. That's the good news, and what good news it is! Just knowing you can always go back to the original data should provide some reassurance to you immediately.
However, there are all kinds of other ways in which people can cause problems for you. In many cases, these issues aren't even caused purposely, but are the result of simple human error. Whether application security is purposely breached or benignly bungled, the issue is that somehow application integrity or data is compromised or damaged. Security actually covers quite a bit of ground, but this chapter focuses on some simple ways of making your application significantly more secure without a lot of work on your part or the use of exotic techniques.
Some people will try to tell you that it's possible to provide complete protection of your software and data. The fact is that if someone ...