IEEE Transactions on Software Engineering - Special issue on computer security and privacy
ACM SIGMOD Record - Directions for future database research & development
Database security
Executing SQL over encrypted data in the database-service-provider model
Proceedings of the 2002 ACM SIGMOD international conference on Management of data
Automating physical database design in a parallel database
Proceedings of the 2002 ACM SIGMOD international conference on Management of data
Incremental Implementation Model for Relational Databases with Transaction Time
IEEE Transactions on Knowledge and Data Engineering
The Vision of Autonomic Computing
Computer
Automated Selection of Materialized Views and Indexes in SQL Databases
VLDB '00 Proceedings of the 26th International Conference on Very Large Data Bases
DB2 Advisor: An Optimizer Smart Enough to Recommend its own Indexes
ICDE '00 Proceedings of the 16th International Conference on Data Engineering
Providing Database as a Service
ICDE '02 Proceedings of the 18th International Conference on Data Engineering
Balancing confidentiality and efficiency in untrusted relational DBMSs
Proceedings of the 10th ACM conference on Computer and communications security
The dawning of the autonomic computing era
IBM Systems Journal
VLDB '02 Proceedings of the 28th international conference on Very Large Data Bases
SMART: making DB2 (more) autonomic
VLDB '02 Proceedings of the 28th international conference on Very Large Data Bases
| Hi-index | 0.00 |
The system management complexity is exponentially increasing for the computing systems by even threatening their viability. Researchers and practitioners are scrambling to significantly simplify the all aspects of system management complexity. One of the most notable efforts towards this direction is the autonomic computing initiative, which is inspired by how the human body works to manage itself. In this paper, we focus on the database security management. We approach the security management issues from the autonomic computing perspective. We consider situations where the database is damaged by successful malicious attacks. Our goal is to design the system in such a way that the database system should be able to isolate the damaged parts of the system and to keep the other parts of the system functioning as the damage is being repaired.