Database Security
The strategies and techniques taught in this book that protect your architecture as a whole will logically also protect your database. However, there are also specific considerations to take into account when designing and building a database. For instance, you might have a situation where you are combining secret-level data with unclassified data. One approach is to use labels or tags to define the clearance and control access based on the user’s security level. However, maintaining such a system is complex, and there is a risk of unauthorized access if the system fails or is improperly configured. For instance, a user with lower-level access might accidentally gain visibility into sensitive or classified information. The best solution is to have separate databases so the classified and unclassified information is handled separately.
The complexity and sophistication of, and reliance upon, modern databases opens them up to various forms of attacks, such...
