A pattern based approach for secure database design

Jenny Abramov, Arnon Sturm, Peretz Shoval

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

Security in general and database protection from unauthorized access in particular, are crucial for organizations. Although it has long been accepted that system requirements should be considered from the early stages of the development, non-functional requirements, such security, tend to be neglected or dealt-with only at the end of the development process. Various methods have been proposed, however, none of them provide a complete framework to guide, enforce and verify the correct implementation of security policies within a system design, and generate source code from it. In this paper, we present a novel approach that guides database designers, to design a database schema that complies with the organizational security policies related to authorization. First, organizational policies are defined in the form of security patterns. Then, during the application development, the patterns guide the implementation of the security requirements and the correct application of the patterns is verified. Finally, the secure database schema is automatically generated.

Original languageAmerican English
Title of host publicationAdvanced Information Systems Engineering Workshops - CAiSE 2011 International Workshops, Proceedings
PublisherSpringer Verlag
Pages637-651
Number of pages15
ISBN (Print)9783642220555
DOIs
StatePublished - 1 Jan 2011

Publication series

NameLecture Notes in Business Information Processing
Volume83 LNBIP

Keywords

  • Secure software engineering
  • authorization
  • database design

All Science Journal Classification (ASJC) codes

  • Management Information Systems
  • Control and Systems Engineering
  • Business and International Management
  • Information Systems
  • Modelling and Simulation
  • Information Systems and Management

Fingerprint

Dive into the research topics of 'A pattern based approach for secure database design'. Together they form a unique fingerprint.

Cite this