Designing secure databases for OLS

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 2736, Issue , 2003, Pages 886-895

  Fernández Medina, Eduardo ^a   Piattini, Mario ^a  

^a UNIVERSITY OF CASTILLA LA MANCHA   (Spain)

Author keywords

[No Author keywords available]

Indexed keywords

DATA HANDLING; DATABASE SYSTEMS; DESIGN;

DATA PROCESSING CENTERS; DESIGN AND IMPLEMENTS; MULTILEVEL DATABASE; REQUIREMENTS PHASE; SECURE DATABASE; SECURITY LEVEL; SENSITIVE INFORMATIONS;

CLASSIFICATION (OF INFORMATION);

EID: 35048812519     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/978-3-540-45227-0_86     Document Type: Article

References (21)

1. Dhillon, G. & Backhouse, J. (2000). Information system security management in the new millennium. Communications of the ACM,. 43, 7, 125-128.
2. Brinkley, D. & Schell, R. (1995). What is there to worry about? An introduction to the computer security problem. In Abrams, M., Jajodia, S. & Podell (Eds.), Information security, an integrated collection of essays (Chapter 1). California, IEEE Computer Society.
3. th, on personal data protection. BOE no. 298, 14/12/1999 (in Spanish).
4. Directive (95/467CE). Directive 95/46/CE of the European Parliament and Council, dated October 24th, about People protection regarding the personal data management and the free circulation of these data. DOCE no. L281, 23/11/1995, P.0031-0050.
5. nd International Conference on Software Engineering (pp. 227-239).
6. Ferrari, E. & Thuraisingham, B. (2000). Secure Database Systems. Advanced Databases: Technology Design. Eds.: Piattini, M. and Diaz, O. Artech House. London.
7. Hall, A. & Chapman, R. (2002). Correctness by construction developing a commercial secure system. IEEE Software, 19, 1, 18-25.
8. Chung, L., Nixon, B., Yu, E. & Mylopoulos, J. (2000). Non-functional requirements in software engineering. Boston/Dordrecht/London, Kluwer Academic Publishers.
9. Smith, G.W. (1991). Modeling security-relevant data semantics. In proceedings of the IEEE Trans. On Software Engineering, 17, 11, 1195-1203.
10. Marks, D., Sell, P. & Thuraisingham, B. (1996). MOMT: A multilevel object modeling technique for designing secure database applications. Journal of Object-Oriented Programming. 9, 4, 22-29.
11. Jürjens, J. (2002). UMLsec: Extending UML for secure systems development. In Jézéquel, J., Hussmann, H. & Cook, S. (Eds.), UML 2002 - The Unified Modeling Language, Model engineering, concepts and tools (pp. 412-425). Germany, Springer.
12. Castano, S., Fugini, M., Martella, G. & Samarati, P. (1994). Database Security. Addison-Wesley
13. Batini, C., Ceri, S. & Navathe, S. (1991). Conceptual database design. An entity-relationship approach. New York, Addison-Wesley.
14. Connolly, T. & Begg, C. (2002). Database systems. A practical approach to design, implementation, and management. Addison Wesley.
15. Levinger, J. (2002). Oracle label security. Administrator's guide. Release 2 (9.2). Retrieved July 1, 2002, from http://www.csis.gvsu.edu/GeneralInfo/Oracle/network.920/a96578.pdf.
16. Avison, D., Lau, F., Myers, M. & Nielsen, A. (1999). Action research. Communications of the ACM, 42(1), 94-97.
17. th International Conference on Integrated Design and Process Technology (IDPT'2002). June. Pasadena, California.
18. th Annual 2001 IEEE International Camahan Conference on Security Technology (ICCST 2001), pp. 163-171. October, 2001. London (UK).
19. Leavitt, N. (2000). Whatever happened to Object-Oriented Databases?. Industry Trends, IEEE Computer Society, August, 16-19.
20. Conrad, C. & Turowski, K. (2001). Temporal OCL: Meeting specification demands for business components. In Siau, K. & Halpin, T. (Eds.), Unified modeling language: Systems analysis, design and development issues (Chapter 10). Hersey, PA., Idea Group Publishing.
21. Toval, A., Olmos, A & Piattini, M. (2002). Legal Requirements Reuse: A Critical Success Factor for Requirements Quality and Personal Data Protection. IEEE Joint International Requirements Engineering Conference (RE'02). IEEE Computer Society, 95-103.