DMCA
Designing secure databases (2005)
| Venue: | INFORMATION & SOFTWARE TECHNOLOGY |
| Citations: | 9 - 2 self |
BibTeX
@ARTICLE{Fernández-medina05designingsecure,
author = {Eduardo Fernández-medina and Mario Piattini},
title = { Designing secure databases},
journal = {INFORMATION & SOFTWARE TECHNOLOGY},
year = {2005},
volume = {47},
pages = {463--477}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
Security is an important issue that must be considered as a fundamental requirement in information systems development, and particularly in database design. Therefore security, as a further quality property of software, must be tackled at all stages of the development. The most extended secure database model is the multilevel model, which permits the classification of information according to its confidentiality, and considers mandatory access control. Nevertheless, the problem is that no database design methodologies that consider security (and therefore secure database models) across the entire life cycle, particularly at the earliest stages currently exist. Therefore it is not possible to design secure databases appropriately. Our aim is to solve this problem by proposing a methodology for the design of secure databases. In addition to this methodology, we have defined some models that allow us to include security information in the database model, and a constraint language to define security constraints. As a result, we can specify a fine-grained classification of the information, defining with a high degree of accuracy which properties each user has to own in order to be able to access each piece of information. The methodology consists of four stages: requirements gathering; database analysis; multilevel relational logical design; and specific logical design. The first three stages define activities to analyze and design a secure database, thus producing a general secure database model. The last stage is made up of activities that adapt the general secure data model to one of the most popular secure database management systems: Oracle9i Label Security. This methodology has been used in a genuine case by the Data Processing Center of Provincial Government. In order to support the methodology, we have implemented an extension of Rational Rose, including and managing security information and constraints in the first
Keyphrases
secure database security information fine-grained classification extended secure database model therefore security rational rose data processing center quality property considers mandatory access control secure database model constraint language high degree database design oracle9i label security information system development relational logical design database model general secure database model last stage genuine case database analysis specific logical design security constraint provincial government fundamental requirement popular secure database management system database design methodology multilevel model important issue entire life cycle general secure data model
